Cloudbeaver’s Post

Transcript

Mou. Configure Web app settings. In this module you will be learning about the settings that are related to the deployment slots, the options on configuring the transport layer certificate for your app. How do you deal with diagnostic logins for monitoring and debugging? And what does a virtual app to the directory mapping? Let us see that. Now in the app servers there is something called App settings to make it more easy. When you create an application, say for example Java or a Python or a PHP or a NET application you build. The environmental variables so-called app configurations would be kept by you in the code. For example in a net app settings dot JSON or web app config files you store your variables of environment in it. And why do we do that? This is something we can leverage as a benefit so that tomorrow you deploy your application to dev environment, you can just change the configurations in that app dot config file to connect to the dev database. You can do the same for testing or staging or production. And same goes with here. A developer doesn't have to each time go and modify the code. Rather in the environmental variables he will provide the configurations. Now, tomorrow, whenever you come across the situation where you want to replace the code with the connection string of a dev database or a testing or QA stage of base, you can pass those app configuration names with the same names in the app settings but with the respective values pointing to dev or testing or. New environment. On doing so, you now ensure that without modifying your code each time, when the app is deployed to each stage, it will connect to the right. Area of connection it has that could be APIs or databases or services it talk to using the connection strings. So in Windows if you talk about it's a very easy thing. You have app config even for Linux as well. But The thing is in the Linux platform based app environment you also pass on these facilities which is an advantage. Similarly in containerized platform of the Linux you have environment flag that can be used which is called container variables. How do I do this in your Azure app service when they go to? The app servers and the left side you have configuration. In the configuration is where you can find out your facility and that's going to be your app settings. So in the app settings you can click on new app settings and you can start adding a key under value where the value is going to be the connection string of the database or API or whatever you want to connect to a dev or testing or staging. So for example there is a dev server then in your dev server you are going to add these respective value. If it is a testing server then. Investing app servers you'll go and you'll do the same. If it is a staging or production you repeat that which means in each environment you do the same. The thing is the key name was going to be common which is in the code, but the value will change based on each environment. Sometimes it's not like you can add every environmental variable by clicking on new. So in such cases you can pass on a JavaScript object notation. You can copy paste a lengthy content at once in an easier. So this is the best strategy that we will use in the upcoming demo. We will be leveraging this as a benefit. So this is an example of the bulk headed where you can give the name of your configuration a value, which is basically the value of it. So in case it's a connection string, then you say the type as SQL Server and it's if it is a Microsoft SQL or PostgreSQL respective options you defined in the slot settings as true or false. If you say false, it's like it's going to be a setting only for that particular app server. But if you say it's true when you do swapping. A concept where you move your code from one slot to other. Use swap the configuration as well. Now some of the settings come into the picture. That is the general settings. You have a technical stack setting that is in your A servers. In the same menu which I showed you earlier there is a general setting menu in which you can specify the technical stack that is like whether it's a net or specific net version or Python or a specific Python version. Platform settings you have in that you can choose bit versions between 32 to 64 bit for your OS. Websocket protocol can be enabled and disabled always on availability. And that's a concept where usually if your app service is not receiving any request for a time period like let's say 30 minutes, it is idle. It will just bring your website down. In other words, it will make it inactive. So when a first request comes, it will take some time to respond for the request. So if you turn always on, as on, there will be no idle time. That means your app is always in the hot tier, in hot mode. So every time when a request comes, it will respond. Similarly, you can set the pipeline version for DevOps. You can choose Http://protocols. You can also specify the ARR affinity and that's a concept where when you scale for multiple instances, Azure is going to just create one more virtual machine for you in the data center. So in this ARR affinity, if it is turned on, Azure knows that OK, this is something that is created for a very high availability. So let's say when we are creating more servers, we will ensure to place those more servers as physically closer as it is possible in the data center. So that's kind of algorithm that Azure will choose. So we can configure these in terms of debugging an asp.net based application or asp.net core or Node JS application debugging can be done. An incoming client certificate part. You can configure client certificate that's a transport layer. Authentication certificate can be specified by you. You can also say that only authorized connection should be allowed to log in into your application. You can even set firewall configurations if necessary. Now configuration of path mapping. So in the Linux and containerized environment you can connect an external storage to your container as a that is hosted. So apps or Windows or Linux you go for you can host both of them in the Azure app services and you can do this when it comes to Windows app which is non containerized. So in a windows environment what happens is that since the underlying storage is used as my data space including the app service, application code and everything. You can create something called virtual directories in it. For example abc.com blog. So the blog will be a virtual directory in which I can host blog separatelyabc.com API, I can host APIs in it. So this way you can add virtual directories, you can have you can even have some custom scripts that can process certain extensions that you specifically require. So that means virtual directories and pointing of those virtual directories as possible here. Now, how about diagnostics and logging? So if you want to do application logging for the Windows or Linux platform, you can easily do that. You have plenty of code libraries available and that can be used and those will be logs that are generated which can be used for analysis of your application performance. Web server logging you want to do for Windows. You can track the HTTP request data that's based on this log file format of West 3C and that's something you can enable. You want to get a detailed error log for Windows. In the HTML error pages you can also find that from the client based exception and that's something you can find out in the log folders of your route you want to track failed request. In the Windows you can do a tracing of the failed request and this can be done using your logs deployment logging When a deployment happens and fails for Windows or Linux you can track these logs by checking out the deployment log files that are available and these settings can also be configured in the platform. Going further, can I configure security certificate? Yes, it's mandatory thing in a business scenario that is like. Transport layer security I'm speaking about, but yes. And an optional perspective of it kind of pre app service managed certificate you will get depending on your configure a CDN or your configure a service called Azure application gateway you will get different choices. So you can even purchase an app service certificate. The first thing if you go to the default domain of Microsoft you get a free transport layer security certificate and SSL is given for free which is auto binder. You go for a custom domain then you may have to buy a certificate. You can import that certificate into Azure key vault and then you can upload your private. Of public certificates accordingly and you can map it. So if you have a custom domain of your own and you want to bind that with an SSL, it is perfectly possible you can easily do that. As a summary, in this module we learned about the application settings like deployment slots, installation or configuration of those certificates and a theoretical discussion, diagnostics, logging and virtual app directories we explored in this discussion. You can also do a knowledge check with the questions in the right side to do a self-assessment for.