<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Infrastructure-as-Code on Eliorion blog</title><link>https://eliorion.github.io/My-blog/tags/infrastructure-as-code/</link><description>Recent content in Infrastructure-as-Code on Eliorion blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 29 May 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://eliorion.github.io/My-blog/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>One Command to Provision a Server</title><link>https://eliorion.github.io/My-blog/11---posts/2026-05-29---mve-itguard-bootstrap/</link><pubDate>Fri, 29 May 2026 09:00:00 +0200</pubDate><guid>https://eliorion.github.io/My-blog/11---posts/2026-05-29---mve-itguard-bootstrap/</guid><description>&lt;h2 id="the-goal-a-reproducible-server"&gt;The Goal: A Reproducible Server&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description></item></channel></rss>