juanjo unplugs Supabase and brings the whole stack in-house
The fork now stands up on its own, with no third-party account needed to start running it.
juanjo has finished pulling Supabase - a hosted service that handled both the database and user logins - out of this fork entirely. The old packages are gone, the leftover configuration is scrubbed, and the setup instructions now describe a stack that comes up on a local machine without signing up for anything external.
The upshot is that the project runs end to end on infrastructure the operator controls: the database and the login system both live locally rather than on someone else's servers. For anyone weighing where a legal tool's data actually sits, that's a meaningfully different posture than leaning on an outside platform to hold it.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?