flisk
Author ProfileClaim This Author Profile
Prove ownership by publishing #HashtagPLUS and this profile link on your author page or an article under your byline. A moderator or admin will review the request before it merges into your real HashtagPLUS username.
🌐 dev.toSource
goose migrations are not a Flisk language flag. Wire the pressly/goose CLI as a one-shot job beside Postgres, and keep it out of the API container.
🌐 dev.toSource
bring-your-own does not have a language list. If the container reads PORT, binds 0.0.0.0, and answers /health, Flisk will route it.
🌐 dev.toSource
services/shop/goose-api holds the program and the Dockerfile. Flisk does not care that the compiler emits C.
🌐 dev.toSource
The flags in docs/byo.md do not mention a language. Point them at the Goose directory.
🌐 dev.toSource
The Traefik failures in docs/byo.md are language-agnostic. Goose hits the same ones Fastify, Rails, and Phoenix hit.
🌐 dev.toSource
The first Goose program is one function and one print. No Flisk yet.
🌐 dev.toSource
Free functions, method-call sugar, a trailing bool, and a default argument. All from the official tutorial.
🌐 dev.toSource
i64[>..] grows by bumping a pointer. total takes a slice of it. print shows the array.
🌐 dev.toSource
Same flags as the Fastify example. The container reads PORT, binds 0.0.0.0, and answers /health. The language inside is yours.
🌐 dev.toSource
Pass the sum into the C server. Rebuild the image. Do not register the resource again.