Software Engineering / ENGINEERING CASE STUDY
Live Site Migration, Backups & CVE Triage
Moved a live WordPress site between hosts without touching its email records, verified backups with archive tests and checksums, and triaged trending PHP and Node.js CVEs by where each runtime actually runs.
THE PROBLEM
Change infrastructure without losing anything
The challenge
Host moves, backups, and security patches tend to fail quietly: email stops arriving, a backup turns out to be corrupt, or effort goes to a runtime that isn't exposed.
My role
Operations work alongside the engineering.
What I did
- Migrated a live WordPress site between hosts, keeping the email records untouched.
- Verified backups with unzip -t and checksums instead of assuming the file is good.
- Triaged trending PHP and Node.js CVEs by first mapping where each runtime actually runs.
THE RESULT
The site moved without touching email, backups are checked rather than assumed, and CVE work goes to the runtimes actually in use.
WordPress · DNS · PHP · Node.js · Bash
HAVE A SIMILAR CHALLENGE?