I’ve been thinking about moving this blog over to Windows Azure for a while, but I’ve finally got around to it, and it has to be said the experience was pretty simple. Previously I’d experimented with Windows Azure Cloud Services, specifically packaging it up as a web role. However, this blog is powered by WordPress, which is PHP and MySql based, so this wasn’t the simplest process in the world, and left quite a lot to be desired when it came to enabling and using all the WordPress features, like being able to use plugins without having to repackage the web role. But then Windows Azure Web Sites comes along, and migrating was simple.
In case anyone else is looking to do the same, here’s the steps I followed:
Well, when I say all done, I mean that WordPress, with all my content and options, is running in Windows Azure. However, I also had to move all the DNS for phazed.com over too, and that’s where I tripped over a little. You can certainly do this with Windows Azure Web Sites, you just need to use a reserved instance, add a CNAME in your domain for the Windows Azure Web Site hostname, and then add a custom domain to your Windows Azure Web Site. This is all explained quite well here:
There’s a caveat however. At the moment you can only add custom domains using CNAMEs, which is practice means I can add www.phazed.com for phazed.azurewebsites.net, but not phazed.com (without the www). Apparently it’s coming, but this was a problem for this blog as all the permalinks used phazed.com, not www.phazed.com. I won’t bore you with the details of how, but I got around it by adding some redirection at my DNS hoster for phazed.com to www.phazed.com, and bulk editing the contents of the database export before importing back into the new MySql database.
Anyway, it’s all done, and I’m quite pleased that’s the blog is finally on Windows Azure. It’s even a little faster I think!
Original post by Rupert Benbrook on July 12th 2012.