https://eliorion.github.io/My-blog/tags/docker/Recent content in Docker on Eliorion blogHugoenFri, 29 May 2026 09:00:00 +0200https://eliorion.github.io/My-blog/11---posts/2026-05-29---mve-itguard-bootstrap/Fri, 29 May 2026 09:00:00 +0200https://eliorion.github.io/My-blog/11---posts/2026-05-29---mve-itguard-bootstrap/<h2 id="the-goal-a-reproducible-server">The Goal: A Reproducible Server</h2> <p>The worst kind of infrastructure is a server that nobody fully understands anymore. Things were installed over time, configuration changed in place, and the mental model of how it all fits together lives only in the memory of whoever last touched it. If that server dies, rebuilding it requires archaeology.</p> <p>The goal for mve-itguard was the opposite: a fresh Debian machine should go from zero to fully operational — users created, Docker installed, runners running, services ready to deploy — with a single command that anyone with the repository and the AGE key can run.</p>https://eliorion.github.io/My-blog/11---posts/2026-05-25---mve-itguard-gitops/Mon, 25 May 2026 09:00:00 +0200https://eliorion.github.io/My-blog/11---posts/2026-05-25---mve-itguard-gitops/<h2 id="gitops-is-a-principle-not-a-tool">GitOps Is a Principle, Not a Tool</h2> <p>When people talk about GitOps, Kubernetes quickly enters the conversation. FluxCD, ArgoCD, Helm — the ecosystem is rich, and the tooling handles a lot of the heavy lifting. The platform continuously watches the repository and reconciles the cluster state to match what Git declares.</p> <p>But the underlying principle has nothing to do with Kubernetes specifically. GitOps is simpler than that: <strong>Git is the single source of truth. No change happens outside of Git. Automation applies what Git declares.</strong></p>https://eliorion.github.io/My-blog/11---posts/2026-05-24---mve-itguard/Sun, 24 May 2026 09:00:00 +0200https://eliorion.github.io/My-blog/11---posts/2026-05-24---mve-itguard/<h2 id="the-problem-with-commercial-solutions">The Problem with Commercial Solutions</h2> <p>When I started thinking about home security cameras, the obvious path was a commercial solution — Ring, Nest, or one of the dozens of cloud-connected systems on the market. Plug it in, create an account, and you&rsquo;re done.</p> <p>I did not go that route. Not because it is difficult to set up, but because of what it implies: your video footage lives on someone else&rsquo;s server, your access depends on a subscription, and if the company changes its pricing or shuts down, you lose everything you built around it.</p>