kevmurr lets you pin where Mike's files actually live

A small config change opens the door to controlling the geographic region of stored data.

infrastructurecompliance

Storage for a Mike deployment runs on Cloudflare R2, an object-storage service for files and documents. Until now the region was effectively fixed, leaving operators to edit source code if they needed something specific. kevmurr's change makes the storage region a setting an operator can choose at deployment time, while leaving the existing default untouched for anyone who doesn't care.

The reason this matters isn't technical housekeeping. Some storage configurations - particularly buckets tied to a specific jurisdiction - only work when you can name the region explicitly. This change makes that possible without forking the code, so a firm that needs its documents to sit in a particular place can say so.

So what Worth a look for anyone weighing Mike against data-residency or sovereignty requirements, where "which country holds the files" is a real question.

View this fork on GitHub →

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

Commits in this thread

1 commit from kevmurr/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
19a3fea5 update region kevmurr 2026-05-19 ↗ GitHub

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-509.md from inside the repo you want the changes in.

⬇ Download capture-thread-509.md