Deploy to GCP
OGRRE production deployments use three pieces of Google Cloud infrastructure:
| Layer | Source | Purpose |
|---|---|---|
| Terraform | orphaned-wells-ui-server/deployment/terraform | Creates and manages backend cloud infrastructure, including GKE Autopilot, upload buckets, static IPs, and DNS records. |
| Kubernetes on GKE | orphaned-wells-ui-server/deployment/kubernetes | Runs one backend workload per collaborator in the shared GKE cluster. |
| App Engine | orphaned-wells-ui/deployment/app-engine | Serves one frontend App Engine service per public collaborator deployment. |
The backend deployment path is GKE Autopilot. Legacy Compute Engine VM modules and definitions have been retired from Terraform; the old VM runtime assets are available only through Git history.
Standard deployment order
- Confirm the Google Cloud service accounts, MongoDB, and GitHub secrets prerequisites.
- Open a fork PR for Terraform infrastructure changes and pass credential-free checks and normal review. After merge to upstream
main, enabled CI plans the sharedogrreworkspace; plans with changes require approval, while no-change plans finish automatically. - Updated backend workflows read
kubernetes_deploy_targetslive after successful reconciliation. While automation is disabled for rollout, apply locally and refresh the fallbackK8S_DEPLOY_TARGETSsecret. - Deploy or update the backend on GKE.
- Deploy or update the frontend on App Engine.
- Configure DNS, App Engine custom domains, and OAuth entries for the frontend host.
- Verify the backend health endpoint, Kubernetes rollout, frontend App Engine service, and OAuth sign-in flow.
Common tasks
- Add a new collaborator deployment: Add Collaborator Deployment
- Manage infrastructure: Terraform Infrastructure
- Deploy backend services: Backend on GKE
- Deploy frontend services: Frontend on App Engine
- Configure repository credentials: GitHub Secrets and Variables
- Reference the old VM path: Legacy Backend VM Deployment