In this tutorial, we will cover application settings in Microsoft Azure.
Before jumping to application settings menu item, i am assuming you have successfully created app service and its running.
Microsoft supports different programming languages with different version numbers. php and java version is not setup to be configured by default so if we intend to do we need to manually turn it on or if don’t need (for instance) php version we can turn it off as one of the tactics to ensure we don’t get hacked.
We can also choose platform either 32 bit or 64 bit. For 64 bit your application need to be in basic or standard mode.
We can also turn on web sockets if our application is using one like node.js or firebase or Signal R.
We can set the application on always on it avoids when sometime application times out.
Managed pipeline version:-
For IIS pipeline versioning it needs to be integrated by default unless we have legacy app that requires an older version of IIS.
The concept of affinity means that when a visitor visits for the first time they get tagged with a cookie and every subsequent time that they come in the same session they directed back to same exact web instance so instead of having 10 running version, that user always goes to same instance every time.
What auto swap means is when we do a deployment from staging slot to production slot and ones deployment is complete and application has started Microsoft Azure automatically do a swap between staging environment and production environment .
So if developers want to determine why application is not working as expected we can turn the remote debugging on so that we can connect to visual studio and debug the code line by line.
Microsoft azure automatically turn it off after some time if so we don’t leave it on accidentally.
Application Settings and connection String:-
We can set up our azure specific app settings and this will override whatever in web.config file.
Now for instance if we have key =a and value =2 in app settings and key =a and value =1 in web.config file then when we deploy application Microsoft azure will replace the key ‘a’ value to 2. We can also check slot settings if we don’t want to override key from staging to production slot.
Connection string is pretty much similar to app settings except we need to choose SQL database. Slot settings is same as app settings if we don’t want to override connection string from staging to production slot.
If we have a particular file extension that we want a particular program to manage for us we can put them here. So if we want php engine to interpret any file that ends in .Html then we can put a mapping to php engine for instance e:\wwwroot.so can configure it within the portal.
Virtual Application and directories:-
Like in IIS, Virtual Application and directories are used to define sub directories that are actually mapped into other physical directories.For Example …/contactus lies in another physical path within website so whenever this URL hits it will mapped to physical directory provided .
When we set up web app for first time Microsoft automatically assigned a domain name by default like http://example.azurewebsites.com which you can see on overview section of Webapp. But almost all time we need to have a custom domain name or sub domain of our main domain when this URL is not sufficient. For that we need to go to custom domain section and purchase a domain through azure. So we can select buy domain button and go through the process of selecting available domain name, purchasing it and it will show up within custom domain name tab of application so Azure is basically functioning as a registrar.
In SSL certificates, we can install certificate so that our application can run over a secure channel. For that we need to generate a certificate and upload it in order for Microsoft azure to associate it with Web app. You go through Microsoft’s this link which will give you complete guide for importing and installing certificate
That’s all for this post.See you in next tutorial