Flisk · interactive

Two small files. `flisk up`. A whole stack.

Each part of the app is one short service.json. Press flisk up and watch Flisk write the rest, start a local gateway and Postgres, route requests, and rebuild only the part you save. Edit the ports below first if you like.

services/shop/orders-api/service.json backend

{
  "appName": "orders-api",
  "appType": "backend",
  "stack": "shop",
  "port": 4000,
  "healthCheckPath": "/health"
}

services/shop/shop-web/service.json frontend

{
  "appName": "shop-web",
  "appType": "frontend",
  "stack": "shop",
  "port": 3000
}

stack: shop stopped

0files written

0Traefik labels

0/4containers healthy

0rebuilds (only what changed)

Start the stack, then send a request through the gateway.

terminal ~/my-shop

# press ▶ flisk up shop

A simulation for illustration: timings are sped up and no containers run in your browser. The file counts, gateway, routing rule and health check mirror what the real flisk up writes for this two-service shop (see What Flisk writes for you). Try it for real: npm install -g @flisk-sh/flisk · flisk.sh