icon Azure Publisher - Single
Created by Orckestra

Azure Publisher User Guide

Downloading Websites with Azure Publisher

Apart from pushing changes to a blob storage, Azure Publisher allows you to download the website from the blob storage and run it on a host of your choice. In this way you can set up a "staging" copy of a website from the blob storage, for example, locally on WebMatrix or IIS, or remotely on your ISP hosting or even Microsoft Azure.

And with its publishing features, you can synchronize your “local” changes back to the Azure blob storage and then further on to the live website(s) on target servers.

Please note that the download feature is only available to those publishing profile that are set as “downloadable”. And at least one publishing profile should be set as downloadable to make the feature available.

To download a website with Azure Publisher, first prepare a staging website:

  1. Install a new "blank" website selecting "Bare Bones" in the setup wizard on a server of your choice, for example, locally on WebMatrix.
  2. Install and configure the AzurePublisher add-on on your staging website.
  3. Make sure to set at least one publishing profile as downloadable. (It make sense to use the profile that copies all the files of the website.)

(For information about installing and configuring Azure Publisher, please see the “Azure Publisher Setup Guide”.)

Now download the website:

  1. In the Content perspective, select the Azure Publisher node.
  2. Click Open Publisher on the toolbar to open the Azure Publisher view.
  3. In the Azure Publisher view, click the down arrow button on the Download button to select the profile to use to download the website data.

Figure 5: Advanced Publisher with the Download feature

It might take some time to download and locally set up the website. Once the website has been downloaded and ready, the CMS Console will reload and you will have the copy of the website from the Azure storage.

If it is not reloaded automatically, you might need to reload the CMS Console manually.

Back to top