Skip to main content

R4. Rollback

What this page helps you do​

Plan how to return to the last good version quickly.

Why it matters​

Rollback plans feel optional right until a deploy breaks sign-in, payments, or data flows.

You should already have​

  • a deploy path

Skip this page if​

  • you are still before the first deployment

What to do​

  • decide what rollback means in your setup
  • document the steps
  • know what happens to database changes

Have a written rollback note, even if the first version is simple.

Common mistakes​

  • assuming redeploying the old commit is always enough
  • forgetting database changes
  • not testing the rollback path once

Next step​

Go to R5. Uptime monitoring.

Advanced notes​

TODO for contributors: add rollback examples for managed hosting, VPS deploys, and hosted databases.