As a few of you knows already, I REALLY love static sites.
So when I read the news that Azure Blob Storage enabled Static Site in Public Preview back in June, how would you classify my reaction?
Right away, I wanted to automate this deployment. Then began my search into Azure Resource Management (ARM) templates. I search left and right and could not find an answer.
Where was this mysterious setting hiding?
If the switch wasn’t in the ARM template, it must be somewhere else.
Since I tend to rush myself into coding, it’s the perfect moment to breathe and read. Let’s read the announcement once again:
This feature set is supported by the most recent releases of the Azure Portal, .Net Client Library (version 9.3.0), Java Client Library (version 8.0.0), Python Client Library (version 1.3.0), Node.js Client Library (version 2.10.0), Visual Studio Code Extension (version 0.4.0), and CLI 2.0 (extension version 0.1.3).
So, it’s possible to do it in code. On top of that, there are at least 6 versions of this code in multiple languages that set that property. Wow. Way to rush too fast into code Maxime (imagine slow claps here).
By going into the .NET Client Library’s GitHub, and searching for
static website led me to those results.
The results may not look like much, but it mentions
Service Properties. This is definitely not an ARM concept. Let’s do a quick search for
azure storage service properties.
Where does it lead us? Just like every good Google search should lead. To the docs.
Wow. So I don’t even need to do a REST API or sacrifice a few gummy bears to get it?
Just like that, the service is now enabled and able to serve HTTP request on a URL looking like this.
Next post? Custom domain? Yay or nay?
If you want to read more about how it works, I would recommend the following resources: