There are a lot of awesome static site generators out there. It’s not always easy to figure out how to setup continuous deployment for them though.
This post will describe how to deploy a statically generated site using yeoman angular to Azure Web Apps, but these steps can be applied to deploy any statically generated site to Azure Web Apps.
Deploying the initial site
What’s going on here?
Using Kudu for debugging
Luckily all Azure Web Apps come with a handy Kudu site that gives you command line access to your site. You can get to it at
I navigated to the site’s
D:\home\site\wwwroot folder and saw all the content was there. And that’s when I face-palmed and realized that statically generated site is saved to the
dist folder, and that’s not even part of the deployment!!!
Luckily, that’s easy enough to fix.
Check the static site into the source code
First issue was to include the
dist folder in the source code. You just need to exclude the
/dist line from the .gitignore file for that. Easy enough.
Now when you deploy your site to Azure Web Apps your site exists in the new
yo angular you have to run
grunt once first before you check in your code to actually generate the
But your site still doesn’t work…because Azure Web Apps is expecting the site’s content to be in
Custom deployment settings to the rescue!
.deployment file to the root folder of your code and paste the below inside:
[config] project = dist
This will tell Azure Web Sits that the root folder for your site is the
dist folder. Now your sites will be hosted from the
D:\home\site\wwwroot\dist folder. If your static site generator puts your site in some other folder, set project to that folder’s name.
Check in the file, deploy it to Azure Web Apps, and see the magic happen.
You can find a full copy of the sample code here on Github, with check-ins corresponding to each step of this tutorial: https://github.com/ZainRizvi/YoAngularOnAzureWebApps
You can see the final working site here: http://yoangularonazurewebapps.azurewebsites.net