Introduction & Overview
Creating an App Service Web App
Configuring a Web App
Creating Web Service Containers
The course is part of these learning pathsSee 2 more
You’ve got an idea for a great web app, or maybe you’ve already started building it. The next question is how are you going to get it out there on the Internet?
In this course, you will learn how you can quickly and easily set up a website and publish your app to the world with Azure App Service. Of course, web apps are a lot more complex and varied than just HTML pages and we will see how App Service supports a range of programming languages, frameworks, and even operating systems. We will explore features that greatly simplify application deployment and management, as well as those that will increase your app’s functionality like authentication and accessing on-premise data. App Service as with other Azure products has a raft of tools for monitoring and logging so you can make sure your app is performing optimally.
For any feedback, queries, or suggestions relating to this course, please contact us at firstname.lastname@example.org.
- Deploy apps using the Azure App Service
- Create a web app using the Azure Portal
- Create a web app using Visual Studio
- Understand the configuration and diagnostic capabilities available from Azure App Service
- Understand the advanced features of the service such as container deployment and deployment slots
This is a beginner level course suited developers or anyone wanting to know how to deploy web apps to the Azure cloud.
To get the most from this course, you should have a basic understanding of the software development lifecycle, while knowing how to code would be a plus.
Course source code
I want to briefly go through the process of creating a Docker container web app from scratch and using Docker Hub to deploy to an Azure Linux container App Service app. I’ll start with a standard MVC web app using the .Net Core framework and check the Enable Docker Support. As the project wizard says you’ll need to download Docker Desktop and install it. While you’re at it create a Docker account that will allow you to upload container images. Once my template web app has been created I can set it as the startup project. You’ll notice that there is now a Docker option in the debug dropdown list. With Docker Desktop installed I can run and debug the web application within the container locally. As you can see in the output window Visual Studio is checking that the project’s target operating system, Linux, matches the Docker Desktop’s OS setting. Having established this, it downloads the container image that will host the application. When you install Docker Desktop it sits in your system tray. Ok, we’ve established that the application runs in the container locally, now we need to upload or publish it to Docker Hub. This time when I’m picking my publishing target I’ll check Docker Hub from the container registry options. This will require me to enter my Docker credentials. One thing to note here is that “Publish to a personal repository” is not the same as publishing to a private repository. With a free Docker account, you get 1 private repository, but by default repositories are public. This subtle difference can be confusing when creating the App Service. Take note of the image tag, which defaults to latest. I’ll create the container app image and publish it to Docker Hub. Now that’s done let’s create the App Service. It will be another Docker Container hosted in Linux, but this time the image source will be Docker Hub. This is where private personal confusion can arise. Unless you have explicitly published to a private repository leave access type as public. The image and tag field will be your Docker id followed by a forward slash and the app name, then a colon followed by the image tag, in this case, latest. With that all done, let’s finish the rest of the setup and deploy the service app. As with the last container, we see the log shows the successful deployment and we can go to dockerhubapp.azurewebsites.net to see the finished article running.
About the Author
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.