Tagged: rollback
Pages with this tag
4 · Track and restore
1Keep a MOD-NNN tracking log and a _CUSTOMIZATIONS file documenting every vendor patch, and run restore-vendor-customizations.php to re-apply your overlay automatically after composer install or a vendor update overwrites vendor/.
Emergency Hotfix
2Production is broken — the fast, safe path to patch a live CodeCanyon Laravel app and roll back if needed.
2 · Roll back
3Restore the last good release via the deployer symlink or a known-good tag — when to roll back versus fix forward, the database-migration caveat, and post-incident steps.
6 · Rollback + monitor
4Prove a one-command rollback restores a previous release, run the immediate post-deploy sweeps, and open the standing 24–48h observation follow-up without leaving Phase 5 falsely partial.
4 · Post-deploy monitoring & day-2 (P9)
5Watch closely through the first 24–48h — smoke tests, integration checks, performance/security spot-checks, log triage, and baselines — with rollback always one command away, then the abbreviated subsequent-deploy cycle.
Implement Vendor Updates
6Apply a new CodeCanyon vendor release without losing your customizations or breaking the database — compare the schema, apply the update on a branch, then restore your overlay.
2 · Apply the update
7Tag a backup, branch the frozen author baseline to author/vY.Y.Y, drop in the new vendor files, then merge to develop and run migrations safely — every step reversible until the update is proven.
3 · Restore customizations
8Re-apply your vendor-customizations overlay with the restore script after the clean vendor/ rebuild, re-scan for backdoor signatures, confirm every ZajModule, zajm_ table, and _zaj column survived untouched, verify the patches behaviourally, then deploy staging-first.
Code → test → ship
9Terse deploy loop — local verify, pick Pattern A/B/C, run dep deploy or staging→production, post-deploy checks. Peeled from MWF1; teaching lives in the Ship playbook step.
Version management
10Two version lines that never get confused — SemVer for your own fork versus the vendor's author-vX.X.X snapshots — plus CHANGELOG discipline that keeps upgrades calm.
Deploy commands
11Ship, server-sync, and rollback command sequences at a glance — develop → staging → production behind the Atlas pre-deploy gate (STOP on DS102/DS103), plus the three rollback options.