<?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>Self-Hosted on Eliorion blog</title><link>https://eliorion.github.io/My-blog/tags/self-hosted/</link><description>Recent content in Self-Hosted on Eliorion blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 25 May 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://eliorion.github.io/My-blog/tags/self-hosted/index.xml" rel="self" type="application/rss+xml"/><item><title>GitOps Without Kubernetes: Docker Compose + GitHub Actions</title><link>https://eliorion.github.io/My-blog/11---posts/2026-05-25---mve-itguard-gitops/</link><pubDate>Mon, 25 May 2026 09:00:00 +0200</pubDate><guid>https://eliorion.github.io/My-blog/11---posts/2026-05-25---mve-itguard-gitops/</guid><description>&lt;h2 id="gitops-is-a-principle-not-a-tool"&gt;GitOps Is a Principle, Not a Tool&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;But the underlying principle has nothing to do with Kubernetes specifically. GitOps is simpler than that: &lt;strong&gt;Git is the single source of truth. No change happens outside of Git. Automation applies what Git declares.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Why I Built a Self-Hosted Home Security Platform</title><link>https://eliorion.github.io/My-blog/11---posts/2026-05-24---mve-itguard/</link><pubDate>Sun, 24 May 2026 09:00:00 +0200</pubDate><guid>https://eliorion.github.io/My-blog/11---posts/2026-05-24---mve-itguard/</guid><description>&lt;h2 id="the-problem-with-commercial-solutions"&gt;The Problem with Commercial Solutions&lt;/h2&gt;
&lt;p&gt;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&amp;rsquo;re done.&lt;/p&gt;
&lt;p&gt;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&amp;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.&lt;/p&gt;</description></item><item><title>OpenClaw setup and security</title><link>https://eliorion.github.io/My-blog/11---posts/2026-05-14---openclaw-setup-and-security/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://eliorion.github.io/My-blog/11---posts/2026-05-14---openclaw-setup-and-security/</guid><description>&lt;h2 id="why-i-run-openclaw-at-home"&gt;&lt;strong&gt;Why I run OpenClaw at home&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;I want an AI agent who can read my files, run commands, and help me on my homelab project, but I don’t want to send my workspace to a SaaS or open a public port on my router. OpenClaw is a self-hosted agent platform: it run on my Linux box, hold the agent sessions, and expose a small control UI to interact with it from any of my devices.&lt;/p&gt;</description></item></channel></rss>