Personal Flisk demo

@ada_test2's Flisk stack

Upvoting lifts this stack toward the top of the list on the home page. One vote per browser. You can also pop a stack's bubble there to vote for it.

Progress

00:02

elapsed

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

✓
Plan ready
Scaffolding with flisk
✓
Repo pushed
○
Starting flisk up on a GitHub runner
○
Live

✓ clone restaurant
✓ flisk resource ×2
✓ flisk up --dry-run

Open the repo on GitHub

popped 0Waiting? Pop some bubbles.

While yours builds, see other stacks

@BonoDJblackweb · api · api-migrator▲ 1ready
@example_devweb · api · api-migrator · chain · indexer▲ 1ready
@brookserversweb · api · api-migrator▲ 1starting
@botweb · api · api-migrator · assistant▲ 1ready
@theoweb · api · api-migrator▲ 1starting
@testweb · api · api-migrator▲ 1ready

Why this stack

db · postgres
jobs · worker, email
agent · ai
mcp

Stack diagram

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

Run it

Fork Star Flisk

Fork puts this stack in your own GitHub account, ready to change. On the fork page, untick "Copy the main branch only", then open the branch demo/ada_test2-agents-efcf2c. Then flisk doctor and flisk up run it on your machine.

Or use the commands

npm install -g @flisk-sh/flisk
git clone -b demo/ada_test2-agents-efcf2c https://github.com/flisk-sh/demos.git agents-demo
cd agents-demo
flisk doctor
flisk up

Or scaffold it yourself

npm install -g @flisk-sh/flisk
flisk doctor
flisk project --yes
flisk resource web --type frontend --stack agents --framework react --yes
flisk resource api --type backend --stack agents --feature prisma --yes
flisk resource jobs --type worker --stack agents --feature nats --yes
flisk resource tools --type mcp --stack agents --yes
flisk resource assistant --type agent --stack agents --yes
flisk up agents
flisk status

Open after `flisk up`

Live links appear here while a live run is up. Until then, run the stack on your machine.

Local addresses (only on your machine, after flisk up)

reservation-apphttp://app.flisk-restaurant-example.localhost/reservation-app
floor-apphttp://app.flisk-restaurant-example.localhost/floor-app
assistanthttp://api.flisk-restaurant-example.localhost/api/assistant/health
toolshttp://api.flisk-restaurant-example.localhost/api/tools/health
reservation-apihttp://api.flisk-restaurant-example.localhost/api/reservation/health
kitchen-apihttp://api.flisk-restaurant-example.localhost/api/kitchen/health
menu-apihttp://api.flisk-restaurant-example.localhost/api/menu/health

If port 80 is busy, Flisk picks 8080–8180; flisk status shows the exact address.

Your service.json files

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

webfrontendreact app

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

apibackendbun + hono API

// services/agents/api/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "api",
  "appType": "backend",
  "stack": "agents",
  "port": 4000,
  "healthCheckPath": "/health",
  "params": {
    "ASSISTANT_URL": "http://assistant:4300"
  },
  "dependsOn": [
    "api-migrator"
  ],
  "featuresEnabled": [
    "prisma"
  ]
}

api-migratormigratorruns Prisma migrations against the shared Postgres before the api starts

// services/agents/api-migrator/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "api-migrator",
  "appType": "migrator",
  "stack": "agents"
}

jobsworkerbackground work: worker, email

// services/agents/jobs/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "jobs",
  "appType": "worker",
  "stack": "agents",
  "port": 4100,
  "dependsOn": [
    "api-migrator"
  ],
  "featuresEnabled": [
    "nats"
  ]
}

toolsmcpMCP server over Streamable HTTP at /mcp

// services/agents/tools/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "tools",
  "appType": "mcp",
  "stack": "agents",
  "port": 4200
}

assistantagent/health, /ready, x-session-id routing, checkpoints survive restarts

// services/agents/assistant/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "assistant",
  "appType": "agent",
  "stack": "agents",
  "port": 4300,
  "dependsOn": [
    "tools"
  ]
}

Make it yours

This stack is a plain git branch. Copy it, change any service.json or the code, and run it on your machine. Send your version back and we can show it here.

1. Copy the branch: the clone command is in Run it above.

2. Put it in your own repository (needs the GitHub CLI)

cd agents-demo && rm -rf .git && git init -q -b main && git add -A && git commit -qm "my agents" && gh repo create my-agents-demo --source . --push --private

Open the branch on GitHub Share your change on X

Add a badge to your README

Show that this stack is a Flisk bubble. The badge links back here and shows the upvotes.

Copy the markdown

[![Flisk bubble](https://demo.flisk.sh/badge/ada_test2-agents-efcf2c.svg)](https://demo.flisk.sh/d/ada_test2-agents-efcf2c)

Share it

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

Post it on X

Want one for a friend?

Ask @grok on X with their handle and what they build.

Make one for a friend How it works

Get this stack for yourself Ask Grok for a friend