juanjo is cutting Mike's cord to the cloud
A careful, fully-planned rebuild so Mike runs end-to-end on your own hardware, with no outside accounts required.
Most forks bolt on features. juanjo went the other way and pulled out a dependency: Supabase, the hosted service Mike leaned on for both its database and its user logins. In its place, everything now runs locally - the database, the sign-in system, and the document storage all spin up on a developer's own machine in one step, no third-party cloud sign-ups needed to get started.
What stands out is the discipline. Before touching the code, juanjo wrote out the whole plan in detail: what changes, what stays, what's deliberately left for later, and an honest note about which parts are broken mid-switch. One route was migrated end-to-end first as a test before the other sixty-odd were touched. The result is a Mike a firm could, in principle, run entirely on infrastructure it controls.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?