Menu

Flisk BYO Runs Any Language. Goose Uses That Door.
📰

Flisk BYO Runs Any Language. Goose Uses That Door.

DEV Community: docker·flisk·about 4 hours ago
#d5pBltRs
#devtodocker#devto#dev#flisk#language
Reading 0:00
15s threshold

Part 1 of Any language on Flisk.

docs/byo.md does not list allowed languages. The heading is "Bringing a framework app (Node, Go, Rust, ...)" and the next sentence is the rule: any app that fits the contract can run as a bring-your-own resource. Fastify is the worked example only because it needs nothing beyond the framework. The provider guide sends Java, Ruby, and a legacy service through the same door. Goose goes through it too.

--type backend --language is a different door. That one scaffolds Bun, or Python, Go, Rust, and Node if you ask. It is a generator. BYO is not a generator. Flisk does not write your application. You bring the image. The language inside the image is yours.

Same command, any language

flisk resource <name> --type bring-your-own --stack <stack> \ --dockerfile ./Dockerfile --health-path /health \ --path services/<stack>/<name> --yes

Enter fullscreen mode

Exit fullscreen mode

byo is the same type as bring-your-own .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.