ecarjat makes Mike run on a laptop with no cloud account

A new local setup lets you stand up the whole of Mike on your own machine, end to end, without signing up for anything.

infrastructure

ecarjat folded in a contributor's setup that packages Mike's front end, back end, and database into containers - self-contained bundles of software you can run locally with Docker - so the entire system boots on a single laptop. No hosted accounts, no cloud bill, nothing to provision before you can poke at it.

This is a build for tinkering, not for production: it reloads as you change the code and is aimed squarely at developers evaluating Mike rather than running it for real clients. A production-grade version lands later in the fork. A couple of manual setup steps still trip up first-timers, but the headline is the lowered barrier - clone, run, and you're looking at a working copy.

So what If you're a founder or technical lead weighing whether Mike is worth a serious look, you can now try it before committing to any infrastructure.

View this fork on GitHub →

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

Commits in this thread

2 commits from ecarjat/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

b671622e Add Docker Compose dev stack and local Supabase setup Nader 2026-05-08 ↗ GitHub

SHA	Subject	Author	Date
`b671622e`	Add Docker Compose dev stack and local Supabase setup	Nader	2026-05-08	↗ GitHub
commit body Two services in docker-compose.yml (frontend on :4000, backend on :4001) with bind-mounted source for hot reload. Container command runs `npm install` on start to work around a Docker Desktop named-volume init quirk where node_modules from the image gets a partial copy when overlapped by a bind mount. `supabase init` scaffolding with the existing one-shot schema copied into supabase/migrations/ so `supabase start` brings up Postgres + Auth + Storage + Realtime locally and applies the schema automatically. README: new "Run locally with Docker" section covering ports, env wiring (host.docker.internal for server-side, localhost for browser), and the storage bucket bootstrap.
`319d4bc1`	Merge remote-tracking branch '0xNadr_fork/local-docker-setup' into merge-0xNadr merge local docker	Emmanuel Carjat	2026-05-09	↗ GitHub

commit body

Two services in docker-compose.yml (frontend on :4000, backend on :4001)
with bind-mounted source for hot reload. Container command runs `npm install`
on start to work around a Docker Desktop named-volume init quirk where
node_modules from the image gets a partial copy when overlapped by a bind
mount.

`supabase init` scaffolding with the existing one-shot schema copied into
supabase/migrations/ so `supabase start` brings up Postgres + Auth +
Storage + Realtime locally and applies the schema automatically.

README: new "Run locally with Docker" section covering ports, env wiring
(host.docker.internal for server-side, localhost for browser), and the
storage bucket bootstrap.

319d4bc1 Merge remote-tracking branch '0xNadr_fork/local-docker-setup' into merge-0xNadr merge local docker Emmanuel Carjat 2026-05-09 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-395.md from inside the repo you want the changes in.

⬇ Download capture-thread-395.md