kushbavaria draws Mike a cloud home, then shuts the door a minute later

A full production deployment path plus an organization-locked login - proposed, verified in part, and closed almost as fast as it opened.

kushbavaria put together a way to run this Mike fork as a real hosted product rather than something that only works on one laptop, and bundled a login policy to control who gets in. Three pieces stand out:

A cloud deployment path: the frontend and backend are packaged into separate containers and run on Google Cloud Run, Google's managed service for hosting web apps without babysitting servers.
Secrets-aware setup: credentials are meant to be pulled from a managed vault at runtime rather than pasted into the code, keeping a live deployment production-safe.
A front-door access policy: sign-in and sign-up are limited to anyone with an @ornn.com company email, plus a short invite list of named outside advisors.

The author sanity-checked the scripts and got both halves to build, but noted a real launch still needs live database, storage, and model credentials. The change closed about a minute after it opened and never reached the main project, so it stands as a blueprint, not a running system.