Diabolarius/mike

Single-commit Supabase extraction -- Postgres, JWT, and Docker Compose replacing the entire cloud dependency

One-commit fork. No ongoing development visible beyond the initial Supabase extraction. Appears to be a compliance- or data-sovereignty-motivated one-shot effort rather than active fork maintenance.

View on GitHub →

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

Direction

infrastructuresecurity

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

Threads of work (detailed view)

2 threads have been distilled into posts.

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.