7 hours 58 minutes
Welcome back. In this episode, we're going to take a look at our azure app. Service is with the demo.
My objectives include we're gonna go out and create an APP service plan and then create a Web app inside of it. Let's jump back out to the azure portal
back here in our azure portal. I've already got APP service plans ferreted on the left, so let's go and select it.
We'll click on add to create our first plan.
I already have an existing resource group that I've created called APP Service is Lennox RG.
You need to give our APP service playing a name
that's evident by the name. I'm going to select Lennox as my underlying operating system
and I'm going to select the East US region.
Finally, we need to select our pricing tier. This is gonna be what we saw in the last episode when we're checking out the azure documentation. Let's click on change size
and this page really lays out exactly what you get with each pricing tier. Let's go check out the Devon test. We have F one and be one for free and basic, but we can also expand this menu and see some other basic options that we have.
If you scroll down, we don't see many features available to us here.
So let's go back to production.
See additional options.
I'm gonna select the S one pricing tier. This is in the standard range and pretty much the lowest one we have inside of production.
Scroll down. We can see some of the features that are available, such as custom domains, the ability to auto scale and set up staging slots. Let's click on apply.
We'll review and create
Tango and create our APP service plan.
Now, with our up service plan deployed, let's go back and take a look at it.
And here we take a look at some of our configuration options.
First, in the over you page, you can see the CPU memory data in and out that air being consumed inside the APP service plan.
We can also see what APS are currently associated with the plan. Right now, we don't have any, but we're gonna create one in a couple of minutes.
We can also review the file system usage inside the APP service plan. Right now, our plan includes 50 gigabytes.
We also have the ability to scale up to another plan. If we find this one is not working out for us,
we can go to a premium orb into an isolated here.
We can select another standard tear or remove all the way to Premium.
And since we're in our standard here, we also have the option of scaling out. Right now, it's set to manual scale, which means we set the number of instances we want,
but kind of like virtual machine scale sets. We can also customize auto scale options in here we can scale based on a metric or scale to a specific instance count.
And if we click on add a rule
here, we can see some of the criteria we can set that we want to use to scale out, too.
Our common hello world example is the CPU percentage,
but we could also base it on data in or out
disc http que links memory percentage and other TCP networking options.
Now we have our APP service plan. Let's go in and go create a Web app. Lets jump back over to APP. Service is
here. Let's click on add
gonna select our existing resource group.
We'll give our Web at the name
and here I'm gonna establish some additional instance details. Right now I'm gonna publish this using code, but you do have the option of using a doctor container. Something will cover in some upcoming episodes.
And then we're gonna select our runtime stack.
I'm going deploy a Web app
using Know Js
I'm going to keep it at the east US region.
Here you can see it. Auto selected the APP service plan we just created. But if we were to select a different operating system or a different resource group or region, we would have to create one here.
So if you don't want to create an APP service plan beforehand, you can create one. When you go to create the Web app,
let's go ahead and review and create
how their resource deployed. Let's go back to APP Service is
will select our new Web app
in here. In the old review page, we can see some properties about our Web app. First we have our euro. Let's go ahead and select it.
And here Microsoft has just created a very basic Web page, just so we can sure that everything is up and running here. In a few minutes, we're gonna deploy our own code to it so we can take a look at it.
Let's go back to our portal.
Let's go check out some of our configuration settings that we covered in the slides.
Here we have our application settings that we can configure, which are just environmental variables that we can access our application at runtime.
We'll still have the ability to set connection strings.
We take a look at general settings.
We can get a little more specific about our stack and some versions with it. We could switch it to one of our other programming languages.
And if we had a specific major and minor version that we needed, we could set that here.
We also have a couple of platform settings,
such as if we want to use secure FTP. Actually, I'm gonna go ahead and set this right now,
we'll have the ability to set our Web app to be always on, which will prevent it from being shut down when it's idle due to an activity. We also select a our affinity or basically using cookie affinity with our Web app.
We also have some options around debugging and incoming client certificates.
Let's go back to the top.
Let me save this real quick.
Let's go check out our path map ings,
and here we can actually configure a mapping to azure files or blob containers to use within the Web app.
We also have the ability to set custom domains,
and we can even purchase and manage domains directly inside of Azure. Here,
and just like we saw inside the APP service plan settings, we can configure the scale up and scale out settings here is well,
and finally, if we scroll down to the bottom
under monitoring, we have APP service logs.
We do have the ability to turn on application logging.
We can send it to the file system
like we saw in the slides on the last episode. We can set a quota in our retention period days. Then down here at the bottom, we have a special FTP website that we can use to download zip files of the logs.
Now that we have our Web app, we have to get code into it somehow, and there's quite a few different ways to do that. for the purposes of the demo here, I tried to pick the easiest one I could find. So let's go back up to the top.
We're gonna go to deployment center.
We do have options like azure repose or get have bid bucket or a local get depository.
But we're gonna do is just a manual deployment. And we're gonna use FTP.
We're gonna open up its dashboard
and here we have the F. T. P s en Pointe. Remember, this is why I turned on secure FTP earlier in our settings
and we have a user name and password we can use in order to access the FTP site.
So what I've done, I've gone ahead and copied our endpoint user name and password,
and I have those saved offscreen here. Let's go ahead and close this out.
Microsoft makes available some very basic Web maps that we can use to practice deployment.
We jump out here to get hub
under azure samples. There's a no Js docks hello world, and what she'll want to do is go down here and download the zip file version of this and unzip it onto your system.
Next, you can use any FTP transfer program here. I'm using when SCP
and from our dashboard earlier. I'm just copying in our in point user name and password.
And here we are connected. And as you can see in our route, here is the web app that they have configured forest already.
I'm gonna go ahead and remove this.
And here is that no J s application that I've already downloaded.
I'm gonna take some of these and we're gonna ftp it to our www route.
If you go back to our overview and click on, browse
our web out, we'll reload, and we can see our hello world application has been deployed to the same. Your oil that we looked at before
says the very basics of creating a NAP service plan,
creating a Web app and deploying an application to it.
Let's come back to the slides and wrap this up.
Coming up next, we're going to take a look at another component of our Web Epps by talking about deployment slots. See you in the next episode.