The Settings blade: App Service plan
This is
the App Service Plan section of the Settings blade (Figure 2-28).
Figure
2-28 App Service Plan section on the web app’s Settings blade.
These are
the App Service plan settings you can configure on this blade.
App Service Plan This shows which App Service plan is used by the web
app. This will show the settings for that App Service plan, which are the same
values you see if you choose your App Service plan from All Resources on the
main menu of the Azure portal.
Scale
Up (App Service Plan) This lets you change the pricing tier for the plan.
Each pricing tier provides different values for the
Scale Out (App Service Plan) This is where you can set up autoscaling
for your App Service plan and all of its app services. For example, you can ask
it to increase the number of VMs if your CPU percentage reaches 90 percent and
stays there for X number of minutes. We’ll take a closer look at this in the
“Scaling Web Apps” section later in this chapter.
Change
App Service Plan This enables you to select a different App Service plan or
create a new one.
The
Settings blade: Publishing
Figure
2-29 shows the Publishing section of the Settings blade for a web app.
Figure
2-29 Publishing section on the web app’s Settings blade.
Here is
what each of the Publishing settings is for:
Deployment Source This is where you can choose a source
such as Git, GitHub, OneDrive, Bitbucket, Dropbox, or Visual Studio Team
Services to be used for continuous deployment.
Deployment Slots This lets you publish multiple versions
of your web app to different URLs. For example, you can set one up and call it staging,
then publish interim changes to it. After you’ve tested the new version
thoroughly, you can put the new version in production by swapping the
deployment slot called staging with production.
Deployment
Credentials This lets you set the user name and password for use with Git
and FTP deployment.
There are additional sections for Mobile
Apps, WebJobs, and Routing, and a section that enables you to set up a custom
domain and SSL bindings.