Diabolarius rips out Supabase for a self-hosted stack

In one large AI-assisted commit, Diabolarius pulls Supabase - the hosted Postgres-plus-auth service Mike normally leans on - and replaces it with plain Postgres running in a Docker container, password hashing and token-based login written from scratch, and a docker-compose file that ties the pieces together. New signup, login, and account-deletion endpoints land alongside a fresh users table. The motivation reads as data sovereignty: keep everything inside your own infrastructure rather than a third-party cloud.

The clever trick is a translation layer that lets the rest of the codebase keep talking to the database as if Supabase were still there, so the route handlers didn't need a rewrite. Clever, but bespoke - and now permanently the fork's problem to maintain. There's also no migration path for anyone already running on Supabase, a dev-only secret sitting in the config, and a server-side auth check quietly disabled along the way.