juanjo cuts Mike's cord to Supabase
The frontend now talks to its own backend through a cookie, not a hosted auth service - and the whole stack boots from a single command.
juanjo has finished pulling Supabase out of Mike entirely. Supabase was doing double duty as the hosted database and the login system; both now run locally. The browser side has been rewired to authenticate through a cookie issued by Auth.js (an open-source login library for Next.js apps) and to talk to the backend over same-origin URLs, instead of carrying a bearer token to a hosted service.
The practical result: a fresh contributor can clone the repo, run one Docker command, and have a working stack - Postgres for data, MinIO standing in for cloud object storage, login working end-to-end - without signing up for anything. The team also added a profile-update endpoint so user records flow through the backend rather than a third-party SDK.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?