Skip to content
Workspace
Contact
Status
Owner
Tags
Related
🚨Incident response🏗️Architecture overview

Production deploys pause on Fridays after 3pm unless the change fixes an active incident.

Before you deploy

  • CI is green on main
  • Migrations reviewed by a second engineer
  • Risky changes are behind a feature flag
  • Changelog entry added

Deploy to staging

terminalbash
1# Build and push the image
2pnpm build
3docker build -t registry.acme.dev/app:$(git rev-parse --short HEAD) .
4docker push registry.acme.dev/app:$(git rev-parse --short HEAD)
5
6# Roll out to staging
7./scripts/deploy.sh staging

Promote to production

  1. Run the smoke suite against staging: pnpm test:smoke --env staging.
  2. Post the release notes in the team channel and tag the on-call engineer.
  3. Run ./scripts/deploy.sh production and watch the error rate for 15 minutes.

Rollback

Run ./scripts/rollback.sh production to return to the previous image, then open an incident doc so the follow-up is tracked.

Pages inside

Linked mentions3

Comments

V