ecarjat takes Mike off the cloud and onto his own hardware
A self-hosted build of Mike, packaged for private servers and toughened so it stops falling over.
ecarjat has wired up a private build-and-release pipeline that packages Mike's front and back end into production-ready images and runs them on hardware he controls, reachable at his own domains rather than someone else's cloud. For anyone who wants Mike running on infrastructure they own, this is about as close to a working blueprint as the forks get.
Folded into the same work is a round of hardening. The backend used to crash on certain errors; now it catches them and returns a clean response instead of going down, and authentication hiccups come back as a proper "try again" rather than a hard failure. He also fixed a genuine bug where documents shared with a colleague weren't reliably matching - meaning shared access could quietly fail to work.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?