Learn to define and configure framework versions, app settings, connection strings, and handlers in an Azure app to achieve optimal performance.
- [Instructor] Now that we have a couple of apps created, let's go ahead and look at the settings that we can configure for each of these apps. Let's focus in on Prodwebapp, I'm going to go ahead and select it. And we'll find application settings under settings. This is quite an extensive list, so we'll step through it in detail. Under general settings, basically we can specify our framework version here. We will select the supported versions of the development frameworks that may be applicable to our application.
In the case of Java and Python, off means it is disabled, and if you enable it you will disable .NET, PHP and the Python options, as we can see as I turned on Java 7, I'm going to go ahead and turn that off. We can choose between either 32 or 64-bit to run our web app. Keep in mind the basic, standard and premium run in 64-bit.
Free and shared only run in 32-bit. Next is our web sockets. These can be turned off or on. Our next item is Always On. Enabling Always On ensures our app is already loaded. And the reason we have this is because if our web app is idle for a period of time it will be unloaded. You would turn this on, for example, if your app runs continuous web jobs.
And finally, under our general settings, we have Managed Pipeline. You would only turn on Classic, if you were running with a legacy app. Otherwise, leave it as the default of Integrated. As we scroll down a little bit, we come into ARR Affinity, otherwise known as Sticky Sessions. You would turn this on to ensure that the client is always directed to the same instance for the duration of that session. But feel free to turn this off if an instance becomes too overwhelmed with requests.
Next we have the Auto Swap feature. In the previous chapter, we saw how we could swap our deployment slots manually. Here we can set it to Auto Swap. If we turn this on when a new update is pushed to the staging slot, the app will automatically be swapped into the production slot. You will notice that I cannot turn this on, because I'm actually looking at the web app, that happens to be sitting in the production slot right now.
In order to turn this on, I'd have to configure this setting from the app that sits in the staging deployment slot. Next we have debugging. If we need to enable remote debugging this is where we'd turn it on. Once this is turned on, then we can use Visual Studio to connect directly to the web app, keeping in mind that when you turn this on, it's only on for 48 hours.
When turned on, you would pick your corresponding Visual Studio version. Next we have our app settings. On startup, our app will load the name value pairs that are listed. If you're like me, and not a developer, you'll need to reach out to your dev team and they can help you with entering the correct values as required, and our connection strings are used to connect to linked resources, such as a sequel database. Next we have our default documents.
This specifies the documents that are displayed to your users when they open up the web app. This list is processed from the top down. Therefore, you will want your home page at the top of this list. Next we have handler mappings, that are used to add custom script processors to configure specific extensions, such as PHP, RESP. We need to enter the extension, processor path and any additional arguments that are required.
Again, you may have to work with your dev team for this. And finally we have virtual apps and directories. If your app requires a virtual app or directory, you would provide the details here. Again, if you're like me, and dev is a little bit of a foreign area for you, you will need to work closely with your dev team, in order to configure these app settings.
- Deploying Web Apps
- Creating App Service plans
- Deploying and moving apps
- Configuring app settings
- Managing Web Apps using PowerShell and CLI
- Configuring alerts
- Enabling diagnostic logs
- Retrieving and streaming logs
- Configuring Web Apps for scale and resilience