WordPress Account Containment

For nearly every one of my music projects, I have been the guy with enough experience in web development to take a stab at making a webpage for the band.

The result is that, over the years, I’ve attached a handful of add-on domains to my web-hosting account. As my account has slowly grown, this has led to a combination of issues ranging from increased exposure to malware, privacy concerns, and sloppy .htaccess files.

After a recent talk with my web-host, I’ve transitioned my web-hosting package to a reseller account, and have finally completed the process of migrating the add-on domains to independent, contained accounts. The result for each site will (hopefully) be reduced exposure to malware, improved privacy, cleaner .htaccess files, and — more generally — easier maintenance.

While it would have been best for my hosting package to have been a reseller account from day one, this transition has taught me how to port web-mail accounts, email forwarders, and MySQL databases between servers. (Although my accounts are on the same server, the process is the same). More generally, the migration process has taught me about the challenges one can encounter while porting WordPress.

From my early days of static websites, PHP and MySQL, and much later – WordPress, child themes, automated back-ups, and now a reseller account – it has been a long but illuminating road as a hobbyist web programmer. The lesson seems to always be “do it right the first time”, but often it takes making mistakes to learn that there is a right way of doing things.

This post is part of the thread: Ralford.net – an ongoing story on this site. View the thread timeline for more context on this post.