amal66 makes Mike something you can run on your own servers

A new one-command setup lets anyone stand up Mike's full web-and-API stack locally instead of wiring it together by hand.

infrastructure

amal66's fork bundles everything needed to spin up a working copy of Mike on your own machine or infrastructure - the web front end, the API behind it, and, in later additions, file storage and a caching layer. The idea is that a contributor or an IT team can go from zero to a running system in a single step, rather than chasing down environment settings and dependencies one at a time.

This is plumbing, not a new feature - it doesn't change what Mike does, only how easily you can get a copy running. But it's the kind of plumbing that decides whether a tool stays a demo or becomes something a firm can actually evaluate in-house. The work mirrors a recurring push across Mike's wider fork family toward being genuinely self-hostable.

So what Worth a look for any legal-ops or IT lead who wants to trial Mike on their own setup before betting on it.

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 amal66/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
5719dd1d feat(chapter-27): add Docker Compose for local self-hosting Amal 2026-05-24 ↗ GitHub
commit body
Chapter: 27 - Self-hosting path.

Plain-English map:
Add Dockerfiles and Docker Compose configuration so contributors can run a
local web/API setup with less manual environment work.

Why it matters:
If local setup is fragile, forks drift because everyone solves deployment
differently. A supported path keeps more work shareable upstream.

Principle:
Self-hosting should be boring and documented.

Precedent borrowed:
Upstream PRs #44, #63, and #149 plus the fork report's large local/self-hosted
stack cluster.

Upstream base: willchen96/mike@d39f580.
Original local commit: b2ae01c.

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

⬇ Download capture-thread-594.md