Getting changes live.
WHAT THE STEPS USUALLY ARE
Back up Deploy the code or artefact Install dependencies Apply database changes Rebuild caches Restart processes Verify
WHY THAT ORDER
Each depends on the previous one.
WHAT TO AUTOMATE
All of it, ideally as one command.
WHAT TO PREFER FOR DELIVERY
Pulling from version control, or deploying a built artefact.
WHY
Repeatable and traceable, and it avoids uploading the wrong files.
WHAT NOT TO DO
Edit files directly on the server.
WHY
Changes are lost at the next deployment and exist nowhere else.
WHAT TO KEEP
The previous version, so reverting is possible.
WHAT TO VERIFY AFTERWARDS
The site loads Key paths work The log is clean Scheduled tasks still run Assets load with current versions
WHAT TO MONITOR
Error rates, for the following hour.
WHY
Problems appear under real traffic, not during verification.
