I added some course examples from my Microsoft courses in the Coursecontent. Clone that repo, do not fork it, I am consolidating 4-5 repos all in this one. It contains:
- Azure PowerShell and CLI examples
- DSC examples (IIS on Windows and LAMP stack on Linux)
- Great diagrams about Github relational structures
- Bicep examples
- Much more...
For Azure App Service related demos, clone or fork Slots
- Create an App Service
- Configure an Environment variable for each of the custom properties in the appsettings.json file in the root of the repo (dbconn, site, colour and auth - don't forget to save 😉)
- Create a second deployment Slot - make sure to copy the config of the Production slot, else you will have to recreate the fields as opposed to just setting new values (both slots will merely render the appsettings.json file settings if not set in the app service slots)
- In the second slot (I will call mine UAT as I setup Github Approval for a UAT Environment in that repo hehee Mr fancypants)
- Got to the second Slot Deployment blade, and deploy the app from Github into your second slot. You should see the values you set fo rhte second slot in the app UI
- Swap slots or you can opt for auto Swap which will basically not allow for testing but rather give you a zero downtime type deployment
For container (Docker) demos, clone or fork docker-app. It has several folders but once pushed to ACR, you can easily deploy the container image to ACI, ACA, App Services and AKS. There is a workflow for thislast one, follow these steps:
- In the root of the repo there is a Dockerfile referencing the actual app in /src directory
- There is Github workflow called "Build and deploy an app to AKS" which will require you to setup a service principal in Github for your Azure Subscription (Service Princial needs Contribute to Subscription)
- deployment.yaml will be referenced in the Workflow and deploy the app to an AKS cluster so you should update this file with the corresponding changes in the workflow file where relevant