https://eliorion.github.io/My-blog/tags/age/Recent content in Age 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-27---mve-itguard-secrets/Wed, 27 May 2026 09:00:00 +0200https://eliorion.github.io/My-blog/11---posts/2026-05-27---mve-itguard-secrets/<h2 id="the-problem-every-project-has">The Problem Every Project Has</h2> <p>Every project that deploys to a real server has secrets. Tokens, passwords, API keys — values that should not be publicly visible but that the application needs to run.</p> <p>The GitOps approach makes this harder to ignore. If Git is the single source of truth and all configuration lives in the repository, where do the secrets go? Committing them in plaintext is an obvious mistake. Leaving them outside Git means the repository is no longer the complete source of truth — some knowledge lives only in someone&rsquo;s head or in a separate system.</p>