Deploying a static website to Azure Storage from AppVeyor

This week the Azure storage team finally announced that Azure Storage now support hosting static websites. This has been a long-standing request from users of Azure (for nearly 4 years), so it's great to see something now available for use, even if at the time of writing it's currently only in public preview.

I've been hosting this blog in AWS for almost a year now, so I thought I'd give the public preview a try and automate deployment with AppVeyor as well at the same time.

Part of the primary reason this blog is hosted in AWS is because it wasn't possible to host the static site in Azure, which is my preferred cloud hosting provider for most of my infrastructure. But as that wasn't possible I went with S3 for content and AWS Lambda@Edge to handle IIS-style folders and custom HTTP response headers. You can read more about that in this blog post: https://blog.martincostello.com/migrating-from-iis-to-s3/

I've used AppVeyor to deploy content to Azure storage before as it's used to host my CDN where I store images and other content that this blog and some of my other sites use to reduce duplication, so I thought I'd use that as a starting point for the implementation.

All-in it actually only took about 45 minutes to setup and configure, so it's surprisingly easy to start using. I just followed the Getting Started instructions in the announcement blog post and then opened a Pull Request on my blog repo in GitHub to test it out.

The approximate steps to enable Azure static website hosting for this blog were:

There's plenty of extra stuff I'd need to do to migrate back from AWS to Azure once this comes out of public preview if I choose to move, but it's nice to see that the mechanics of uploading content are easy to get moving with. These extras include:

Deleting content from the storage container no longer present in source.

Configuring a custom DNS hostname.

Fronting it with Azure CDN to support custom TLS certificates.

Configuring appropriate caching headers.

Configuring HTTP response headers for things like having a Content Security Policy to get an A+ rating in tools such as securityheaders.io.

Relatively painless and quick to turn around, this looks like a feature that will be useful for those with a strong preference for Windows Azure to keep their different types of infrastructure co-located (and leverage their Azure MSDN credits too).