DevOps Practices, Tooling, and Automation
View All Tags
Your manager, client, or product owner wants to see project progress without you exporting a status report every week. Most platforms have some kind of view-only role for this — but "free" means three very different things, and picking the wrong one is how teams end up with a surprise invoice.
A running installation is not a finished one. This part backs up both stores with the two different methods they actually need, proves the backups restore, automates them with a systemd timer, updates the stack without losing anything — and shows you how to remove the whole thing cleanly if you decide it is not for you.
Your installation is collecting. This part reads every panel on the dashboard — and starts with the thing that makes this product different: it tells you in plain sentences why it thinks a visit was a person or a machine, states how many readings each figure could actually be taken from, and says "not known" rather than guess.
Getting an app deployed is the easy half. This final part covers what you actually do with a running app: read its logs, understand how it scales, know what it costs — and take it all down again.
This is the part where it becomes real. Four tabs in the Azure portal and your container gets a public HTTPS address that anyone in the world can open.
This is the shortest part of the series and the one most likely to save you an afternoon. Pushing an image is three commands — but if you're on an Apple Silicon Mac, one missing flag produces a container that builds perfectly, pushes perfectly, and then refuses to start on Azure.
Your container image is stuck on your laptop, and Azure can't reach your laptop. In this part you'll create the two Azure resources that fix that: a resource group to hold everything, and a container registry to store the image.
Your app works on your machine because your machine happens to have .NET 10 installed. A container removes that "happens to" — it packages the app and the runtime into one box that behaves identically everywhere.
Most "deploy to the cloud" tutorials skip the part where you actually understand what you built. This series does the opposite: six short parts that take you from an empty folder to a real, public URL on Azure, explaining every command along the way.
Learn how to install Docker Engine on Ubuntu Server using Docker's official apt repository. This step-by-step guide covers setting up the Docker repository, installing the engine and CLI, running Docker without sudo, enabling it to start on boot, and verifying everything works with the hello-world container.
