Skip to content

Deployment

CI/CD pipelines, deployment guides, and release management.

Document Description
Deployment Guide Branch model, what deploys where, rollback
Build Pipeline Cloud Build triggers, images, and deploys
Releasing Per-app release timelines and workflows
Coolify Decommission What the GCP path replaced
  • Development: local β€” docker-compose up -d postgres redis temporal, apps run natively
  • Staging: merge to staging β†’ gcp-deploy.yml β†’ Cloud Build β†’ *-staging services
  • Production: manually dispatch auto-deploy-main.yml β€” it fast-forwards main to staging β†’ same pipeline β†’ *-prod services

Cloudflare Workers and the docs site deploy from their own per-app workflows, not through Cloud Build.

Terminal window
# Record a change for release
pnpm changeset
# Deploy staging: merge your PR into staging (never push to it directly)
gh pr merge --squash
# Promote staging to production (a human dispatching this IS the approval)
gh workflow run auto-deploy-main.yml --ref staging
# Force a full rebuild + redeploy of every GCP service
gh workflow run gcp-deploy.yml -f force_all=true