juanjo rips Supabase out of Mike, root and branch
A plan-driven excision of the hosted backend in favour of a self-contained local stack - and the planning docs are the real artifact.
juanjo's fork sets out to make Mike runnable end-to-end with nothing but a single Docker command - no external accounts, no hosted services. The target is a clean break from Supabase, the hosted Postgres-and-auth provider Mike was built on, replaced with a local Postgres database, Auth.js for login, and Drizzle as the single source of truth for the schema. Object storage moves the same direction: MinIO, a local stand-in for Amazon's S3, takes the place of the cloud bucket for first-run development.
What sets this fork apart is the paper trail. Three planning documents lay out the spec, the foundation work, and the mechanical sweep through every remaining call site - sequenced as foundation, then a single working slice, then the cleanup. It reads less like a refactor and more like a migration playbook anyone else could pick up and follow.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?