Welcome to Shaun Luttin's public notebook. It contains rough, practical notes. The guiding idea is that, despite what marketing tells us, there are no experts at anything. Sharing our half-baked ideas helps everyone. We're all just muddling thru. Find out more about our work at bigfont.ca.

Two Git Deployments to Azure: One for Static Files, Another for Full Builds

Tags: kudu, azure, azure-websites, git

The goal is to have two deployments types.

  • One for static files only.
  • The other for a full build.

Both will use KuduSync to copy files. A wonderful thing about KuduSync is that (if we use it as intended,) it will never delete a file that is not under version control.

The full build deployment is what comes out of the box when we run this:

azure site deploymentscript --aspWAP Orchard.proj -s src\Orchard.sln

For the static files only deployment, we can take that default script and change this:

To this:

And beside the deploy.cmd file, add a new csproj like this: