daohualiuxiang
/
dotnet-podcasts
mirror of https://github.com/microsoft/dotnet-podcasts.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add info about staging

resource-cleanup
James Montemagno 2022-12-07 15:02:49 -08:00 committed by GitHub
parent a5d4b02bbf
commit 83bba36576
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/deploy-websites-services.md
View File

@ -157,6 +157,10 @@ That's it! Now, Navigate to you https://`WEBAPP_NAME`.azurewebsites.net/ to watc
The GitHub workflow is also configured to deploy these apps only if the source within specific folders such as `src/Services/Podcasts/` is changed. So now, if you make some changes to the code, build locally, and then commit changes to see the GitHub workflow kickstart. Need any ideas for code change? You'll notice an empty `GlobalUsings.cs` in the `Podcasts.API` project. Go ahead refactor the code and move your global namespaces there.
## Staging Environment
In addition to the main CI/CD pipeline that creates and publishes the podcast app to Azure, you can also enable a full staging environment that gets run and deployed on pull requests. If you do nothing all PRs will push to your main resources, but if you setup an **Environment** named **staging** in your repos settings you can create the same GitHub Secrets outlined. The only difference being a different name such as appendng **staging** onto the end of every resource. Once these secrets are setup when you make a PR these new secrets will be used deploying to a new Azure Resource Group with new resources.
Happy Deployments!
---