easterbrooka opens a path to AWS

The fork can now be deployed on Amazon's cloud, not just Cloudflare's.

infrastructure

easterbrooka has rewired the backend so it can run on AWS - specifically on Fargate, Amazon's managed container service, sitting behind a standard load balancer. The storage layer, which previously assumed Cloudflare R2 (Cloudflare's S3-compatible object store), has been generalised so the same code can talk to either R2 or Amazon S3. Credentials no longer need to be supplied up front either; the backend can pick up its identity from the AWS task it runs inside, which is how enterprise AWS deployments are expected to work.

A second piece of plumbing bundles LibreOffice into the container so the backend can convert Word documents to PDF on the fly, without depending on an outside service.

So what Legal teams whose IT departments standardise on AWS - most large firms and many in-house groups - now have a clean deployment story for this fork.

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