Skip to main content

R3. Safer deploys

What this page helps you do​

Lower the chance that a normal update becomes an outage.

Why it matters​

Launch is not one deploy. It is the start of repeated deploys.

You should already have​

  • a working deploy path

Skip this page if​

  • you are still trying to get the first version online

What to do​

  • keep deploys repeatable
  • add a simple smoke test
  • avoid manual production-only edits
  • know how to roll back

Use small deploys and keep a working previous version available if your stack allows it.

Common mistakes​

  • changing too many things in one deploy
  • making emergency server edits with no record
  • skipping a post-deploy check

Next step​

Go to R4. Rollback.

Advanced notes​

TODO for contributors: add example smoke-test questions for simple sites, SaaS apps, and APIs.