amaingot moves Mike's whole stack onto AWS
The fork has quietly re-platformed off Cloudflare and Supabase onto Amazon's cloud, and a routine housekeeping pull request accidentally put the whole rebuild on display.
amaingot's fork no longer runs on the hosting and database services Mike ships with by default. The frontend, backend, and storage layer have all been rebuilt to run on AWS, Amazon's mainstream cloud - the same infrastructure most large firms and vendors already trust and know how to procure.
The rebuild surfaced by accident. amaingot opened a pull request to the main Mike project that was described as a small change - adding automated quality checks so bad code gets caught before it lands. But because the change came from this already-re-platformed fork, the request dragged the entire AWS rebuild along with it. It was closed within about a minute without being merged, so none of it reached the main project. The re-platform and the new checks both stay in amaingot's fork.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?