mosha101 ↗ analysis ↗ GitHub rainylabs/mike
Infrastructure migration fork: swapping Supabase and Cloudflare for Auth0, Heroku Postgres, and S3
rainylabs/mike has one active line of work: consolidating the platform onto an Auth0 + Heroku + AWS stack to match mosha101's existing infrastructure. The functional application layer is unchanged - the migration strategy is a shim-first approach that keeps the Supabase client surface in place while swapping the backend implementation.
The PR introduces a pg-backed Supabase adapter, Auth0 JWT verification via JWKS, bridge endpoints to feed the frontend auth shim, and Docker/Heroku container deployment. Manual provisioning steps (Heroku add-ons, Auth0 registration, key seeding) are called out as preconditions.
What's in it
- Auth0-based identity Plans to consolidate authentication on an existing Auth0 tenant the team already runs.
- Heroku-hosted backend Intent to run Mike's backend as a container on Heroku rather than its original serverless footing.
- AWS storage Storage moves to S3 as part of the same platform swap.
Direction
infrastructure
Activity
Threads of work (detailed view)
Platform swap: Auth0 + Heroku Postgres + S3 in place of Supabase and Cloudflare
mosha101 is migrating the rainylabs fork off Supabase and onto an existing Auth0 tenant, Heroku-managed Postgres, and S3. The notable decision is what stays unchanged: the entire route layer.
Pull requests (detailed view)
🟢 Open (1)
mosha101 · opened 2mo ago