easterbrooka teaches Mike to live on AWS

The fork now runs cleanly on Amazon's infrastructure without giving up its original Cloudflare home.

easterbrooka reworked Mike's storage layer so the backend can talk to either Cloudflare R2 (the original object-storage backend, similar to Amazon's S3) or AWS S3 itself, picking up credentials automatically when running inside Amazon's container service. Neither side has to be torn out - a team that started on Cloudflare can keep going, and a team that wants to stand Mike up entirely inside AWS now can.

Alongside the storage work, the fork ships a production-shaped container image: slim Node runtime, LibreOffice bundled in so Word documents can be converted to PDF, a non-root user, and the plumbing needed to behave well under Amazon's orchestrator. A separate handoff document covers the deployment architecture and the AWS-side rollout that follows.