Week 68: Production Deployment — Feb 7 – 13, 2026
TL;DR: Exoserva deploys to Google Cloud Platform. Cloud Run services, Artifact Registry, Workload Identity Federation, and a full CI/CD pipeline are live. Version 1.4.0 through 1.4.7 shipped.
Highlights This Week
- Deployed to GCP Cloud Run with Docker containers
- Configured Artifact Registry for container image storage
- Set up Workload Identity Federation for GitHub Actions
- Shipped versions 1.4.0 through 1.4.7 with iterative CI fixes
Cloud Production
Exoserva is officially in production on Google Cloud Platform. The deployment architecture: Docker containers (API on port 8080, Web via nginx on port 8080), Artifact Registry for images, Cloud Run for serverless scaling, and GitHub Actions for CI/CD with Workload Identity Federation (no service account keys).
The Iterative Path
Getting production right took 8 versions in rapid succession. Each version fixed a deployment issue: v1.4.0 (initial deploy), v1.4.1 (test spelling fix), v1.4.2 (Artifact Registry auth), v1.4.3 (id-token permissions), v1.4.4 (env secrets), v1.4.5 (port config), v1.4.6 (smoke tests), v1.4.7 (health check URL). This is the reality of cloud deployments — iteration until everything clicks.
What’s Next
Discourse community integration with OAuth2 provider.