Intranoggin

Blither, Blather, Web Content Management.
Blog » Kentico on Azure: Creating the App Service

Kentico on Azure: Creating the App Service

Now that we have our database created, our next step will be to create the Kentico Web App or App Service.

1. Click New>Web+Mobile>Web App

Create New Web App

2. Enter an App Name, select your subscription, Select the existing resource group that you created above.

3. Click on the App Service plan/Location and click Create New. For Service Plan details, enter a new service plan name, select the location that matches your Resource Group (should be selected by default), and choose the S1 pricing tier.

Why S1?: You may be able to get the site running on a lower tier (Basic, or even a ‘D’ Shared tier), however the Standard ‘S’ tiers give us the Web Slots I want to use along with 50GB storage, backups, free SSL, custom domain support, and room to scale when we need it.

Select Pricing Tier

4. Turn on Application Insights (why wouldn’t you?) and click Create.

Configure your new Web App Settings

1. Navigate to the App Services tab and open the web app you created above.

Navigate

2. Click into the Application Settings tab.

3. Turn off PHP

Settings

4. Scroll down to the App setting section, and add an entry for CMSDisplayApplicationErrorMessages = false. Mark this as a Slot Setting.

Slot Settings

5. In the Connection strings section, add an entry for CMSConnectionString

a. Value= Data Source=tcp:<ServerName>.database.windows.net,1433;Initial Catalog=<DatabaseName>;User Id=<AdminAccount>@<ServerName>.database.windows.net;Password=<AdminPassword>;

b. Replace <ServerName>, <DatabaseName>, <AdminAccount>, & <AdminPassword> with the information you used in the first database you created above.

c. Mark this one as a slot setting as well.

Connection String

6. Click Save

Create the Deployment slot

1. In the web app you created above, click on the Deployment Slots tab.

2. Click the Add Slot button.

3. Enter a Slot Name, and choose your production app as the Configuration source. Click OK

Tip: If you name your deployment slots identical to the production site, but insert a character code to indicate their purpose it makes it easier to understand what’s what and will make jumping back and forth between your sites easier later on.

Example: my production site is IntranogginKenticoApp, so my development slot is IntranogginKenticoDevApp.

Slot Name

Configure Deployment Slot Settings

1. Click into the newly created deployment slot. You’ll notice we have almost all the settings from the primary application available at the slot level as well.

Open Dev Slot

2. Click into the Application settings tab for this slot

3. PHP should already be set to off. Turn Remote debugging on and set Remote Visual Studio Version to the proper version (for me this is 2015)

Dev Slot Settings

4. In the App settings section, adjust the CMSDisplayApplicationErrorMessages value to true and ensure it is set to be a Slot specific setting.

Dev Slot Settings

5. In the Connection strings section, adjust the Database Name in the Initial Catalog value to be the name of your development database created above. In my example, this is IntranogginKenticoDevDB. Ensure this is also a slot specific setting.

a. As long as you’ve used the same server for both your prod and dev databases, only the Initial Catalog needs to be changed.

Dev Slot Connection String

6. Click Save


Posted: 1/11/2017 5:50:00 AM by Ryan Miller | with 0 comments