This is part of my series of try some alternative hosting options. I decided not to stop with S3 and instead to carry on with a few more options I found. One of these was Microsoft Azure.
I was thinking, like Google and Amazon, I would use their storage platform, using a Blob on Azure Storage. The problem was getting my domain pointed at it and the lack of support for default documents (so you have to specify index.html on the end of URLs).
They do offer some free tiers for their Web Apps though, which is their names for hosting websites, whether they be static HTML, PHP, Python, NodeJS or .Net. You can build and host up to 10 apps for free. So I decided to give that a whirl.
To start you need to sign up for a Web App. That will ask you to create an account using Microsoft Online, Google or Facebook logins. You’ll also need to pick a type, based on the language you want to use. I opted for an ‘Empty site.’
When it’s created you’ll get a random subdomain of azurewebsites.net. For some reason I had a countdown suggesting the app was only available for an hour. There was also a link to click to extend it to 24 hours. There was also the option to sign up for a free 30-day trial, which allows the 10 apps. So it’s all very misleading.
So next I had to figure out how to sign up for the free trial, which seemed to send my round in circles. Then I went through a sign up process on a page that took forever to load and re-load. I had to verify myself by text (or phone), I thought they weren’t going to request my card details, but they did. Eventually it created my account (which can take up to four minutes apparently). What a rigmarole.
Once you’re over that hurdle you’ll find your test site is now pointless and you’ll have to create an app all over again. Now you get to pick your type of plan and have to find the free one as it’s tucked away. You also have to create a resource group, something to with sharing permissions. Then you get to wait until the app is deployed. Finally you have a site!
There’s a bunch of options to load your files, from git to Visual Studio. One option is good old FTP (yay). I found the FTP/Deployment User was set to ‘No FTP/deployment user set’ and no obvious way to change it. It took me a web search to find I had to go to ‘Deployment credentials’ and enter some details. Finally I could upload my files to the wwwroot folder.