Docker Containerization Platform and Engine
View All Tags
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 running on a real domain with a padlock, and it belongs to nobody. This part claims it with the one-time owner screen, adds your first website, and gets the tracking code onto a real site — plus the origin rule that quietly explains why nothing appears when you test on localhost.
Your firewall says Default: deny (incoming). Your database is answering the internet anyway. This part shows the port scan that proves it on a real server, explains the iptables chain order that causes it, and fixes it with a Compose override file — not by fighting the firewall.
Learn how to run Dewiride Analytics on your own Ubuntu Server — an open-source web analytics engine that tells you which of your visitors were actually people. This part covers the firewall, the repository, the two passwords you must set yourself, and the single command that brings four containers up and waits until every one of them is genuinely healthy.
Your WordPress site works, but only on your own network. This part puts it on the real internet with your own domain name and free HTTPS — using a Cloudflare Tunnel, so you never open a single port or touch your router. Then we add a Redis cache, set up backups, and finish with a clean removal.
Learn how to run WordPress on an Ubuntu Server using Docker — with the website and its database in two tidy containers instead of installed all over your system. This part covers the project folder, a .env file for your passwords, the compose.yaml file explained line by line, and finishing the famous five-minute WordPress installer in your browser.
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.
