ecarjat wires Mike up to KairosVista's own hardware
A self-hosted production deploy path lands, with some quiet reliability fixes bolted on along the way.
ecarjat has stood up a deployment pipeline that builds Mike's backend and frontend as proper production containers and ships them to KairosVista's in-house servers, behind a public gateway. It's a clear signal of a fork being run for real users on infrastructure the team controls, rather than a hosted cloud setup.
Bundled in are a handful of stability fixes that are arguably more interesting than the plumbing: the server no longer crashes when an authentication check hiccups (it politely returns a temporary error instead), background failures in request handling get caught rather than swallowed, and a sharing-permissions query that wasn't matching the right records has been corrected. Several of these have since been addressed upstream too - so anyone running their own fork should check what they still need.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?