cphlabspace writes down how to actually launch Mike

A pull request that adds no features and changes no product behaviour - but turns the fork from "builds on my laptop" into something a stranger can host.

infrastructureworkflow

The fork already ran locally. What was missing was everything between a working dev environment and a live website: container recipes for the backend and frontend, the Cloudflare config that the existing deploy command silently depended on, a one-command local stack, and a continuous-integration check so a broken build gets caught before merge.

Alongside the plumbing, @cphlabspace has written a full deployment walkthrough - Supabase (the hosted database), object storage, model-provider keys, and concrete steps for half a dozen hosting options from Cloudflare to plain Docker. The Cloudflare path in particular was quietly broken before this; the new config makes the advertised deploy command actually work. None of the application code is touched.

So what For anyone evaluating Mike as a base for a real product, this is the difference between a demo and something a small team can stand up over a weekend.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?