Resources
Rollback
Overview
Roll back the application to a previously verified immutable image and matching frontend assets. Preserve database volumes and forward-only migration history.
Setup & requirements
Do not drop tables, reset databases or rewrite Git history. Recheck Auth redirects, API health and send kill switches after rollback.
Usage & verification
Retain the prior image, main SHA and compatible database backup. Roll back only MailRaft services and recheck health, login and tenant denials. Do not automatically reverse an applied migration or overwrite live data; assess schema compatibility and data loss first. Keep external sending disabled during recovery.