Flisk vs Docker Compose and Tilt

Flisk generates a Compose file and a Tiltfile and runs them for you.

Task Flisk Local dev stack Docker Compose Local containers Tilt Live-update loop
Scaffold a service
flisk resource api --type backend
Different job, closest command.
docker init

Writes Dockerfile and compose.yaml for a project, not one service.

No equivalent

Define resources in the Tiltfile by hand.

Start everything
Live reload on change
flisk up

Generated Tilt live_update

docker compose up --watch

Needs develop.watch rules in compose.yaml.

tilt up

live_update in the Tiltfile syncs files without a rebuild.

Start one service or stack
docker compose up api

Also starts linked services.

tilt up api

Also starts its resource_deps.

Wait until healthy
flisk up

dependsOn waits for /health

docker compose up --wait

Implies detached mode.

tilt wait --for=condition=Ready "uiresource/api"

Experimental. Blocks until the resource is Ready.

See what is running
Read one service's logs
Restart one service
docker compose restart api

Does not apply compose file changes.

tilt trigger api

Triggers an update; may rebuild the resource.

Run a command in a service
Different job, closest command.
tilt alpha shell api

Alpha. Opens a shell only, in a Kubernetes pod.

Show service URLs
Different job, closest command.
docker compose port api 80

Prints the public port for one mapping, not a URL.

No equivalent

Links are set in the Tiltfile and shown in the UI.

Check the config
Different job, closest command.
tilt alpha tiltfile-result

Alpha. Runs the Tiltfile and prints the result as JSON.

Stop