Why? Run multiple containers doing different things all at once. Maybe you want to simulate a microservices based application on your PC before deploying its parts to the cloud.
Utilize docker to setup a simple micro services based application One image to serve our website One image to serve a database One image to serve a web service
Setup your project to auto-build and deploy whenever a code change happens in your cloud repo. We’re going to create a repo in GitHub or Azure Repos Setup a build pipline to listen to the repo
How to use docker to setup continuous deployment to the Azure cloud (Azure app service) PC -> docker build image -> push image to azure container registery -> app service listens and auto-deploys when new image available
How to dockerize an application… A hugo static website built into a docker image and then run as a container serving up the website using Nginx Build the site by installing hugo, running npm install and running hugo to compile the static file
How to backup the gigabytes and terabytes of photos my family takes and ensure nothing ever gets lost, still have enough space on my PC and also keeping the cost down… the good news: it is possible!
When I’m writing code I often need to send my committs to a remote repository. I’m using GitHub and also Azure DevOps depending on the project. It can be frustrating at first to successfully begin sending commits to those repo services and also to automate authentication where you don’t need to enter a password on each Git push.
Here is a quick rundown graph TD Localhost -- Git Push --> G["Github (Master Branch)"] G -- Trigger --> A["Azure DevOps Pipeline Build"] A -- Trigger --> R["Azure DevOps Pipeline Release"] R -- Push to --> B["Azure Blob Storage"] B -- Auto Sync to --> C["Azure CDN"]