25 comments

[ 0.19 ms ] story [ 60.1 ms ] thread
npx @flisk-sh/flisk demo

Flisk Cloning template: demo

The demo stack: restaurant ops with reservations, kitchen and floor control

Source: https://github.com/flisk-sh/flisk-restaurant-example.git Destination: /Users/myusr/.flisk/flisk-demo

Cloning into '/Users/myusr/.flisk/flisk-demo'... remote: Enumerating objects: 644, done.

remote: Counting objects: 100% (16/16), done.

remote: Compressing objects: 100% (15/15), done.

remote: Total 644 (delta 0), reused 2 (delta 0), pack-reused 628 (from 1)

Receiving objects: 100% (644/644), 221.44 KiB | 1.56 MiB/s, done.

Resolving deltas: 100% (353/353), done.

Cloned "demo" into /Users/myusr/.flisk/flisk-demo/

Next steps: 1. cd /Users/myusr/.flisk/flisk-demo 2. flisk doctor # check Docker/Tilt are ready 3. flisk up # start the stack

Runtime readiness: Docker and Tilt are only needed to start the stack: start them, then run `flisk doctor` (readiness) and `flisk up`.

Starting the stack in /Users/myusr/.flisk/flisk-demo...

Added VERDACCIO_URL_DOCKER, VERDACCIO_URL, TILT_ENV, DATABASE_URL, DB_PASSWORD, JWT_SECRET to .env (generated; existing values unchanged)

No generated Tiltfile yet; generating .flisk/.flisk-out/ ...

Generated: .flisk/.flisk-out/TILT_TECH_STACK.star

Generated: .flisk/.flisk-out/TILT_RESOURCE_DEFAULTS.star Generated: .flisk/.flisk-out/spec.master Generated: .flisk/.flisk-out/Tiltfile

Generated: .flisk/.flisk-out/.tiltignore Generated: services/platform/database-management/docker-compose.yml Copied: shared-platform-engineering/docker-templates → project root

Vendored Flisk extension → .flisk/.flisk-out/flisk-cli-ext/

To start Tilt: flisk up

Starting 6 services from all stacks (3 stacks, 6 services)... - reservation-api - reservation-app - kitchen-api - kitchen-worker - floor-app - menu-api

Frontend URLs: - reservation-app: http://app.flisk-restaurant-example.localhost:8081/reservati... - floor-app: http://app.flisk-restaurant-example.localhost:8081/floor-app...

Backend API URLs: - reservation-api: http://api.flisk-restaurant-example.localhost:8081/api/reser...

Opening the first frontend of flisk-restaurant-example - reservation-app: http://app.flisk-restaurant-example.localhost:8081/reservati... - floor-app: http://app.flisk-restaurant-example.localhost:8081/floor-app - kitchen-api: http://api.flisk-restaurant-example.localhost:8081/api/kitch... - menu-api: http://api.flisk-restaurant-example.localhost:8081/api/menu/...

Host ports: HTTP 8081, HTTPS 443, Postgres 15432 HTTP: wanted 80, using 8081 (selected from fallback range 8080-8180). To force 80: HTTP_PORT=80 flisk up

Postgres: wanted 5432, using 15432 (selected from fallback range 15432-15532). To force 5...

how do you run your stack? I bet you not have just one command:)
npx @flisk-sh/flisk demo thats it!
I build magic tool. Its fascinating. Why? Because I decoupled it from real enterprise application. Have for you though about running one command that spins whole Tech stack?

Define each app once, then run flisk up

do you have goose lang integration?
free premium code for 90 days tdk-5a374e its a tool for removing docker
Flisk: your whole stack, running locally with one command

Ask your AI agent for an app, or type four commands yourself. Flisk sets up the containers, database, routing, and secrets, wires them together, and keeps them in sync as you change things.

fix(up): add Health checks section with /health URLs for test infrastructure; fix windows-binary script - #2481 #2481