So I decided to start a blog. I’ve always looked at blogging with a certain amount of apprehension. “Will I become one of those guys that just does stuff cause the crave attention?”. Well I decided to set all misgiving aside and do it anyways … the world needs to be enlightened.
As I will be blogging about Microsoft Cloud technology I set down some base requirements for myself:
- It needs to run in the cloud, either as SaaS or PaaS. While my firm belief is that SaaS is the future, I decided to go with a PaaS solution just because my fingers we burning to do some stuff on Azure.
- It needs to make use of the Microsoft stack. I was actually quite conflicted here, “should I use SharePoint?”, “or maybe built something myself using .net?”. While my preference would have gone to something from Microsoft, WordPress is just so damn simple, elegant and just works. I am typically not a big fan of going with “point solutions” but in stead tend to look at the overall architecture and try to find the best way to create an elegant, harmonious whole in any environment. This is why I tend up making use of 99% Microsoft based solutions and why I love their products. Having said this, WordPress is so simple. I don’t have much time to invest here and WordPress is in the Azure marketplace, makes use of all-PaaS services on Azure so it was kind of a no-brainier.
- It should be free. As I have a Visual Studio with MSDN subscription I get free monthly credit on Azure. I mostly end up using only a small portion of that credit every month meaning these is plenty left for me to host WordPress on Azure without it costing me anything. So even though hosting it on Azure is not free, I don’t have to pay 🙂 More on that later.
- It should be properly managed, secured, backed up and always available. I’ll treat this just like I would an (smaller-) customer solution.
To get WordPress up and running and Azure I needed a couple of things sorted:
- I need an Azure subscription.
- I need to install and configure WordPress.
- I need to properly size Azure resources. This affects performance but also cost.
- I want to add my own domain name.
- I want it backed up, monitored and want to be alerted if there is a problem.
I have quickly sketched these components in Visio:
This is the first post in a 6 part series on running WordPress on Azure (PaaS services). Through the course of the next 5 posts I will detail how I configured all of these elements to produce this working WordPress blog you are using right now.
Follow the links below to read each of the articles in this 6 part series:
- PART1: Introduction (this post): Hello world! So this is WordPress … on Azure 🙂
- PART2: Creating and using your Azure subscription.
- Coming soon: PART3: Installing WordPress.
- Coming soon: PART4: Sizing, performance and cost.
- Coming soon: PART5: Adding a custom domain name.
- Coming soon: PART6: Backup, monitoring and alerting.
EDIT 8-10-2018: I noticed I’ll have to pay MUCH more attention to my spelling and typo’s if I want to blog 🙂 I’ve corrected most typing mistakes. If you find any more and they really bug you, please let me know!