Diabolarius/mike
Single-commit Supabase extraction -- Postgres, JWT, and Docker Compose replacing the entire cloud dependency
Diabolarius/mike has one recorded topic: a wholesale replacement of Supabase with a self-hosted stack. The fork ships Postgres 16 in Docker, a pg-backed query-builder shim that preserves the Supabase-shaped route API, jsonwebtoken + bcrypt auth, and a docker-compose.yml that brings up all three services together. The approach is a big-bang AI-assisted rewrite done in a single commit.
Notable issues include a gutted SSR auth function, a deleted frontend/package-lock.json, no data migration path from existing Supabase deployments, and a hardcoded JWT secret in docker-compose.yml. The query-builder shim in db.ts is the most transferable piece for evaluators.
What's in it
- Self-hostable backend Swaps the managed backend dependency for a database you run yourself, so the application can live entirely inside your own environment.
- Bundled deployment Frontend, backend, and database are wired together to come up as a single stack, making it realistic to stand up on a server without a long setup ritual.
- Conventional auth User accounts and sessions are handled with widely-used token and password-hashing primitives rather than a third-party identity service.
Direction
infrastructuresecurity
Activity
Threads of work (detailed view)
Diabolarius tears out the managed backend and rolls his own
One sweeping, AI-assisted rewrite swaps Mike's hosted backend-and-login service for a self-hosted stack Diabolarius now owns end to end.
Supabase ripped out, replaced with Postgres + JWT + Docker in one commit
Diabolarius swapped the entire Supabase dependency for a self-hosted stack -- Postgres 16, `jsonwebtoken`, `bcrypt`, Docker Compose -- in a single 41-file commit. The most interesting part is a 533-line PostgREST-style query-builder shim that keeps existing route handlers working without rewriting them all.