Last updated on June 6, 2026
The full migration from two separate WordPress installations (dev and www) to a single Debian 12–based VPS is now complete. The new setup runs NGINX with 1 GB RAM and 1 vCPU, sitting cleanly behind Cloudflare. Performance has noticeably improved, even before full caching optimization.
A detailed breakdown of the entire migration process — including NGINX setup, PHP‑FPM tuning, database imports, and theme integrity checks — is now published as a standalone article.
📄 Read: [How I Rebuilt My WordPress Sites from Scratch on NGINX]
Post‑migration cleanup in progress
A series of fine‑tuning and security cleanup tasks followed the main server switch.
Git access reconfigured:
Existing SSH keys were recovered from the old server. Global identity set; safe directory warnings resolved without changing ownership of production directories.
Permissions realigned:
User added to the www-data group. Theme and plugin directories updated with group write access (775/664). Group sticky bit applied to maintain future permission integrity.
WordPress config & database users audited:
All active wp-config.php files reviewed for correct database references. Redundant MariaDB users identified and marked for removal. .disabled migration folder isolated and will be deleted after final review.
Smarter RAM usage observed:
Server appears to be using more memory, which is expected under Debian 12’s smarter caching. Site feels faster even without Cloudflare — likely due to clean config and modern system libraries. No swap usage or out‑of‑memory errors reported.
Status
✅ Status: Migration stable, configuration hardened, and cleanup nearly complete.
Next up: Cloudflare optimization testing, redundant user cleanup, and full theme asset audit.