I’ve moved my blog to a new blogging engine. I’ve migrated all of the old posts. I won’t be setting up any handlers for the old URLs, so the old permalinks will probably 404 on you.
The long form
As you may have noticed, this blog looks and feel different. I’ve moved the blog through a series of blog engines to get to this point. The blog started out on Blogger and was there for years.
After moving to Microsoft I decided it was time to use the tools and platforms that we make. I also decided that it was time to get back into writing code at least part of each day. To that end I decided to grab Mads Kristensen’s MiniBlog blogging engine source code and deploy it into an Azure Platform-as-a-Service (PaaS) web site. This worked out well for a while but I found that I was spending more time tweaking the code and the site than thinking about and writing blog posts. As you can see from my blog history, I posted zero times while on MiniBlog. This should not be taken as a negative against MiniBlog. It is a great blogging engine. Rather I just found writing code more fun than writing the blog.
Since I really want to get back to blogging, I decided to give up MiniBlog for WordPress since I don’t know a damn thing about PHP and MYSQL. I started out by launching the Azure Portal and creating a new Web App and selected WordPress from the Azure Gallery.
Unfortunately, MySQL in Azure is managed by ClearDB and billed separately. I was hoping that I would be able to select Azure SQL as the backend for WordPress but that was never an option. So what’s a guy to do. I could either continue using MySQL as the database or I could ask my colleagues in the Premier Support for Developers team what they us and if any of them have experience with WordPress. It just so happens that one of my colleagues uses WordPress on Azure SQL through Project Nami.
In their own words
And that moment, when we realized that SQL Azure now had proper replacements for all required functions, is when we decided to fork WordPress. In a matter of weeks, Project Nami (Not Another MySQL Interpreter) was born.
Project Nami has a single initial goal — to teach WordPress to natively speak MSSQL while maintaining full compatibility with properly written plugins and themes. This is an important item to note. Any plugin, theme, or function written to access the database via the WordPress API will operate normally. – Project Nami Team
Installation is EXTREMELY easy if you already have an Azure subscription. Just go to the Project Nami download page and click the blue button that says “Deploy to Azure”.
About five minutes later I was up and running. That’s all it took.
If you are looking for a blogging engine running on Azure Paas with a SQL Azure database there are a couple of options, but this WordPress / Project Nami site was easy to deploy and configure. I have to give it high marks so far.