• Introduction
• Prerequisites
• Installing Azure Publisher
• Configuring Azure Publisher

Prerequisites

Make sure you have these prerequisites in place:

• A blob storage on Microsoft Azure
• A source C1 CMS website

Azure blob storage

You should have an Azure blob storage (classic) where you will upload your “source” website or changes on it.

^{Figure 2: A blob storage on Microsoft Azure}

If you do not have a storage on Microsoft Azure, create one:

1. Log in to your Microsoft Azure Portal.
2. Select New / Storage / Storage account.

   
   

   ^{Figure 3: Creating a new storage account on Microsoft Azure}

3. Select Classic for the deployment model.
4. Enter a name for your storage account and select other options where necessary: Type, Subscription, Resource Group, Location.
5. Click Create.

^{Figure 4: Filling out configuration parameters of a blob storage}

Blob connection information

Next, copy or make a note of, the storage account's name and access key (key1):

• All Resources / [your storage account] / Access Keys

^{Figure 5: Getting the blob storage name and access key}

When configuring Azure Publisher you will need to specify the storage account name and primary access key for the blob connection.

It is a “recipient” endpoint (target). Here, you will upload the “source”.

Source website

This is a C1 CMS XML-based website. (The SQL-based website is not covered in this guide.)

We recommend using C1 CMS version 5.0or later.

You can deploy it wherever it is convenient for you. It might be a local website running on WebMatrix, or an online instance on Microsoft Azure or your ISP.

It is a “sender” endpoint (source). Changes made here will be pushed to a blob storage by Azure Publisher.

The source website can be considered as a “staging” website while the website on a target server - a “production” or live website (especially in a single-deployment scenario).

This website can also be occasionally called “local”, which might be a little misleading, since you are not limited to where you host this website: on your local or some remote machine.