easterbrooka cuts Mike loose from Cloudflare and onto AWS

A small, tightly-linked set of changes lets the fork run on Amazon's cloud without rewiring the backend.

infrastructuresecurity

The original Mike backend assumes Cloudflare's storage and refuses to start until you hand it a specific set of access keys. easterbrooka loosened that. When the app runs inside Amazon Web Services, it now picks up its own permissions from the surrounding environment automatically, so there are no static keys to copy, paste, or accidentally leak.

The container it ships in also bakes in document conversion, turning Word files into PDFs on the fly. Together these add up to a clean, self-contained way to host Mike on AWS for any team already living there, without adopting a different architecture or changing how the app stores files.

So what If your firm or legal product already runs on AWS, this is the route to keeping Mike's data inside your own estate rather than a separate vendor's.

View this fork on GitHub →

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

Commits in this thread

3 commits from easterbrooka/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`ddc07e1e`	Support AWS S3 alongside Cloudflare R2 in storage layer	Claude	2026-05-04	↗ GitHub
commit body Make endpoint and explicit credentials optional so the SDK falls back to AWS default endpoints and the default credential provider chain (which picks up the ECS task role automatically). Add R2_REGION env var that falls back to AWS_REGION (auto-set inside ECS) and finally to "auto" for R2 compatibility. Needed because we're deploying on AWS App Runner's successor (ECS Fargate + ALB) rather than Cloudflare.
`754529de`	Add backend Dockerfile for ECS Fargate deploy	Claude	2026-05-04	↗ GitHub
commit body Multi-stage build on node:22-bookworm-slim. Runtime layer installs the minimal LibreOffice (core + writer) needed for DOCX -> PDF conversion, plus tini for proper signal handling around the soffice subprocess. Runs as the non-root `node` user with a writable home so LibreOffice can create its profile. .dockerignore keeps the build context to source + lock files only.
`cc5ebc97`	Merge pull request #1 from easterbrooka/claude/setup-supabase-integration-aCV7X	Andrew	2026-05-05	↗ GitHub
Add AWS S3 support and backend Docker image for ECS deployment

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-55.md from inside the repo you want the changes in.

⬇ Download capture-thread-55.md