rainylabs is moving Mike onto a brand-new stack without touching the app

A proposed migration would relocate this fork's login, database, and document storage to different vendors - while leaving the actual product code essentially untouched.

infrastructuresecurity

Contributor @mosha101 has opened a plan to lift the rainylabs fork off its original foundations - Supabase (a hosted database and login service) and Cloudflare - and set it down on a new combination: Auth0 for sign-in, Heroku for running the backend, and Amazon's S3 for storing documents, with files landing in a US East data centre. Access keys are locked down and kept in a managed secrets vault rather than scattered through the code.

The clever part is restraint. Instead of rewriting the large body of application logic that assumed the old setup, the team built thin translation layers that make the new services answer to the old commands. The migration lands as plumbing work, and the legal features riding on top keep working unchanged. It's still an open proposal on the fork's own branch, with several manual setup steps flagged honestly as not-yet-done.

So what Worth a look for anyone weighing where a Mike-based product actually runs and stores client documents - this is a clean blueprint for swapping the whole foundation without a risky rewrite.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?