Visit djangoplay.org ↗
djangoplay-web / Runbooks / Runbook — Application Rollback
DocsDjangoPlay WebRunbooksRunbook — Application Rollback

Runbook — Application Rollback

Use rollback when a release introduces a confirmed application regression.

1 min readApplies to v1.2.2
On this page ▾
  1. Trigger
  2. Steps
  3. Database Warning

Trigger

Steps

  1. Identify the last known-good release.
  2. Check whether the new release introduced schema changes.
  3. If schema changes are backward compatible, check out the previous application release.
  4. Reinstall the matching dependencies if necessary.
  5. Restart Gunicorn and Celery.
  6. Verify health.
  7. Disable or correct the problematic frontend asset version if the failure is CDN-related.

Database Warning

Do not automatically run:

bash
python manage.py migrate <previous_migration>

A rollback of application code is not equivalent to a rollback of database schema.

Use a database restore only when a controlled database recovery is actually required.