@yourhandle's Flisk stack

Progress

6% · Scaffolding with flisk 00:02
typically about 1 min, a typical estimate.

1. ✓
   Plan ready
2. Scaffolding with flisk
3. ○
   Repo pushed
4. ○
   Starting flisk up on a GitHub runner
5. ○
   Live

While yours builds, see other stacks

• @MY_HANDLEweb · api · api-migrator · chain · indexer● live now
• @yourhandleweb · api · api-migrator · jobs● live now
• @pausecheck2web · api · api-migrator● live now
• @fixcheckweb · api · api-migrator● live now
• @Hollywood90120web · api · api-migrator● live now
• @0xHxxeweb · api · api-migrator · chain · indexer● live now

Why this stack

• cache · redis

Stack diagram

Browser → web → api → Postgres. Workers and migrators share the same database. Traefik routes every service on *.localhost.

Run it

npm install -g @flisk-sh/flisk
flisk doctor
flisk project --yes
flisk resource web --type frontend --stack app --framework react --yes
flisk resource api --type backend --stack app --language python --feature redis --yes
flisk up app
flisk status

Your service.json files

One service.json each. Postgres comes from "prisma" and Traefik routing is built in, so neither needs its own file.

// services/app/web/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "web",
  "appType": "frontend",
  "stack": "app",
  "port": 3000,
  "framework": "react",
  "dependsOn": [
    "api"
  ]
}

// services/app/api/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "api",
  "appType": "backend",
  "stack": "app",
  "port": 4000,
  "language": "python",
  "healthCheckPath": "/health",
  "featuresEnabled": [
    "redis"
  ]
}

Share it

Opens a ready-made post on X. You read it and send it yourself; nothing is posted for you.