Getting your hands dirty in a geeky way

I spent most of the day migrating my WordPress-powered blogs from my current web host to a new one.

Migrating from one web host to another is not something new to me. I’ve been with so many different web hosts I’ve developed my own routine of doing it in about an hour or two with the least amount of stress for me and downtime for my blog.

Backup the blog’s files and database. Setup the new server, install WordPress on it, restore the files then the databases and last would be pointing my domain to it.

The whole exercise has been made a lot easier because until now, the servers I’ve used ran on cPanel and its nifty automated tools – Fantastico, cPanel to cPanel copying of files and whole directories, and the DNS records editor.

For this move however, I had none of those goodies as I have opted to use Virtulamin – a free and open source control panel to manage my VPS instead of the usual cPanel. It may have saved me a lot of in terms of costs but it has taxed me quite well in terms of time and labor.

Don’t get me wrong, it’s not that Virtualmin is not user-friendly or a terrible piece of software, far from it. It’s just that this is the first time I’ve used Virtualmin, I had to take a much steeper learning curve just to do the things I need to complete the migration.

Since Fantastico is not around, I had to scour the web for an install script that would automatically install WordPress for Virtualmin. I had to manually install phpMyAdmin and configure the mySQL databases.

After going through the steps, I wasn’t really surprised that when I hit the home page, it gave me the infamous WordPress “white screen of death” so a quick dive into the Apache error logs and fire up the FTP connections again to figure out what caused the error. After all, the routine I followed was developed with cPanel in mind.

Overall, my day started with the Terminal and would end with it as well. This exercise has really taught me a lot and it gave my command line skills a brush up that it so badly needs.

The fact that you’re able to read this post means that I got most of it right. I just need to give this blog another thorough sweep so in the meantime, expect to see a few missing pages, the 401 error page popping up now and then, and even some of your comments just disappearing.

More updates to come soon.

2 Replies to “Getting your hands dirty in a geeky way”

    1. True that! I actually got to brush up on my command line skills because of the move. I switched to dotblock hosting because their VPS packages offered more RAM than most other providers which was what I really needed more than the huge disk space.

Leave a Reply