Now what are AZURE_CONTAINER_APPs? It's the ability to have server-less infrastructure for your deployments. It allows you to deploy an actual container, and not think about anything else. This is a very powerful way to deploy Hugging Face models, and in fact actually pretty much anything machine-learning models-wise. You will see that you have instant scale, and ability to select different things when you're creating one. So I'm going to go ahead, and go into create a container application, which is the first step in order to try to deploy, and then we'll go, and try to go through the steps that will be needed in order to have the deployment. Let's take a look at the process here. When I click "Create container app", and I click this, it's going to load. The subscription, that's fine. The resource group, we've been using one that is demo-container, and that'll be great, that's exactly what we need. The container app name is pretty important because if we choose something here, whatever name we pick will be used for automation later. Actually I want to show you here why is that important? Because here we will need to update these values. The AZURE_CONTAINER_APP_NAME is demo-container, The AZURE_GROUP_NAME source name the same, these are options, and these are variables actually. So these values can be whatever you are using. Demo dash-container is fine. If I go back here, demo dash-container is correct, and container app name will have to be something unique. If I was doing only demo, let's see, well that's still works, and that's fine. But demo-container sounds fine to me. I don't understand why this is suggesting Canada Central, that's fine. I want to East U.S. and we will be doing "Review, and Create". Then this looks correct to me. Let's see. Accepting traffic from anywhere on port 8000. These are some of the settings that we'll be using, and this looks okay. Let's actually take a quick look at some of the things that we have here. Well this a Quickstart image. Let's take a look at the Quickstart image. Simple hello world container, that sounds fine. This all looks okay, and the target port is 80, we'll be able to change those later. So I'm going to go click "Create" and then wait a second until it completes. This completed. So let's go to the resource here. I'm going to click "Go into the Resource". This has loaded. This is fine. Let's take a look at some of the different things that we have here. So we have an application URL. Actually, if I go there, we'll have a welcome to Azure Containers Apps, which is the basic example container that's going to be used, and we are going to be using some of those. Now, you have the ability to pass in secret, set up continuous deployment, and manage your app through revision. That looks pretty good. We have monitoring as well, if there are any problems, we can take a look there, and then we can see what Ingress looks like. Here we'll have the ability to map some of the ports. Now, remember, if I go here to my tab, remember that if I'm using Hugging Face, actually FastAPI, the UE corn setting. If I take a look at the Docker file over here, we'll be using port 8000. We'll need to make sure that those are updated. But these effectively allows us to have everything ready. I'm going to make that tiny change, I'm going to make sure that this is port 8000 on the target port. The Ingress type HTTP for now, accepting traffic from anywhere, that looks okay. I'm going to click "Save", and then that's it. This is going to update the Ingress, and then that is going to be mapped when we do an actual deployment to Azure. Updating Ingress has been completed, and there you go. This is how you create a container app. Then we'll go, and proceed to see how we can automate, and push something so that this is working, serving, or Hugging Face with FastAPI model, and application.
