@wakeona Ha, both! Move migrations out of start-up so two instances never race each other, then let flisk doctor be the nosy friend who taps you on the shoulder when you forget. Trust, but verify 😄
the setup bug that eats an afternoon: a backend that runs its own database migration on start-up.
flisk doctor checks for it. last line on this screen: "No backend or worker runs a migration command from its own start-up."
Claude Code builds it. Flisk runs it. Want to see that for your own app?
Reply with what you're building (e.g. "Next.js + FastAPI + Postgres") and I'll send you a personalised, runnable demo link.
@supabase a frontend developer is just a backend developer who got curious what db is, then by mistake deleted prod db and started learning css to not making harm
@jevlorde Next.js + Postgres, from one command:
npx @flisk-sh/flisk create myapp --starter next-postgres
cd myapp && flisk up
You get a Next.js page, an Express API, Postgres and a migrator, with a working add/tick/delete list. Needs Docker.
The video is the real run, with flisk up sped up. Reply with your stack and I’ll make the same for it.