Release readiness

Prepare rollback
before you need rollback.

A release is safer when verification, protected-route evidence and recovery are prepared before the website overlay changes.

Deployment guide Diagnostics guide Release operations

Package verificationRun checksums, validation and local doctor checks before files move.CHECKRoute preflightConfirm the website-owned namespace does not collide with application routes.CHECKProtected-route baselineSnapshot the real application routes that must not change.CHECKRollback identifiedKnow the exact previous overlay backup and command before release.CHECKNginx syntaxValidate Nginx configuration before reload.CHECKOverlay smoke testsTest homepage, key explore pages, assets, health and lead behavior.CHECKProtected routes comparedCompare API/webhook/callback behavior after the overlay switch.CHECKEvidence capturedKeep release output/reference IDs so later debugging starts with facts.CHECK

LOCAL CHECKLIST

Release state

0/8 checks marked

bin/thonem-site release-readiness
bin/thonem-cloudpanel doctor
bin/thonem-cloudpanel backup

No persistence

The checkboxes are a browser aid only. Server commands and the real target environment remain authoritative.

Prepare rollbackbefore you need rollback.

Prepare rollback
before you need rollback.