Web Deployment Automation - GitHub Actions, Azure Web Apps, and Appsettings
Vložit
- čas přidán 7. 07. 2024
- The process of deploying a web application should be an automated one. Not only is this a best practice, it is also a fairly simple process. No longer does a CI/CD process need to be intensive and scary. The same is true for handing settings and secrets on the deployed site.
In this video, we are going to build out a simple C# web application using Blazor. That is just so we have something to deploy. From there, we are going to add it to GitHub. After that, we are going to go to Azure to set up a free web application with automated deployments from GitHub using GitHub Actions. Finally, we will update the environment variables in Azure to override our settings in our Appsettings file. This process will allow us to automatically deploy new updates to our site automatically every time we push a commit to GitHub, and it will allow us to have secure settings in Azure that even our developers cannot access.
Full Training Courses: IAmTimCorey.com
Just opened CZcams search for a video to double check the process for deploying to Azure using GitHub actions and this was on my start page. Perfect timing as always Tim.
Great! I am glad it was helpful.
Oh my gosh.... it's like you read my mind on what I wanted to learn next!
Great!
I just woke up this morning smiling with this video.
Great!
Really love the video. Just on a side note, I was having tons of issues with deployment. Turns out the generated YAML file from Azure was using all the latest [use:actions] i.e @v4. Took me a while to research and then noticed your generated YAML file was using various versions of [use:actions]. Only then after 10 failed deployments did I manage to actually get it deployed successfully. Hopefully this can help anyone else running into deployment issues.
Thanks for sharing!
Thank you Tim. Really insightful
You are welcome.
Great! Thanks for this tutorial! Very useful. 😊
You are welcome.
Really good video thanks for this. I think you could have explained the Yaml file a bit and showed the difference in the CI part and CD part
Thanks for the suggestion.
The dotnet eshop demo is so great tim. Just 8 month I learn, full stack blazor, YARP, Serverside e-commerce rendering, GRPC, Minimal API, Simple Postgre, CMS, FluentUI+Tailwind, Bootstrap 5, Blazor Hybrid, Dapper DataAccess, Azure Container Apps, Redis. Not yet the Rabbit MQ. XD. Wish you open part time job to help you from Indonesia. XD
Sorry, I don't have any part-time positions available at this time.
Thanks for this, I have been doing(forced) into Azure Integration services recently, using Logic apps and functions with liquid transforms and service bus and was wondering how the website side of Azure worked. This helped me get a good starting point.
I am glad it was helpful.
Awesome tutorial! Thanks a lot Tim!
Really liked this little technique with parentheses which allows to put some complicated C# code with angle brackets inside of html stuff in Blazor and also this video allowed me to finally understand in general what is CI/CD process and how impressive Azure is (never used it though because it is not available around my parts).
I am glad it was helpful.
Hi @IAmTimCorey, Can you do a video or video series on Azure application insights, how we can use logs to investigate issues etc.
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
and just yesterday in a job interview, I said I need real-world experience for CI/CD.. :)
Now you have an example to get you started.
Thanks for the video Mr Corey. Just wondering where the CI(automated building and testing of code) takes place.
Technically, we are doing both at once with our GitHub Action. We are doing the build and then immediately deploying it. If you had unit tests, you would include those in the build process.
HOw to deploy to non azure host/server?
That depends on the system you are deploying to (there are multiple different ways to do deployments). I have it on my list to potentially show at least one way, though.
What if I want to deploy only a project in my solution? For example, there is a web API project and a blazor project and I want to deploy them on 2 separate web apps? The git repository still contains both projects.
in azure pipeline build the solution. in the release you can specify what projects to deploy from the content of the build zip
The YAML script specifies which project gets deployed. You can change this and have two scripts (one per project) or you can modify the script to have two deployments (one per project).