<?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>Linux on Jobatronic</title>
    <link>https://jobatronic.com/tags/linux/</link>
    <description>Recent content in Linux on Jobatronic</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jobatronic.com/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Homelab</title>
      <link>https://jobatronic.com/projects/homelab/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://jobatronic.com/projects/homelab/</guid>
      <description>A compact Docker homelab running media, monitoring, productivity, and local AI services.</description>
      <content:encoded><![CDATA[<p>This is my 36-container Docker server: a small home lab built to run the services I actually use while giving me a place to experiment.</p>
<h2 id="what-it-runs">What it runs</h2>
<ul>
<li>Jellyfin for media</li>
<li>Sonarr and Radarr for automation</li>
<li>Navidrome for music</li>
<li>Grafana for monitoring</li>
<li>Vikunja for task management</li>
<li>Local AI services</li>
</ul>
<p>The hardware is intentionally modest: a ThinkCentre, an RTX 1060, and a lot of stubbornness.</p>
<h2 id="what-i-learned">What I learned</h2>
<p>The interesting part isn&rsquo;t getting a container running. It&rsquo;s making the whole stack reliable: backups, networking, updates, monitoring, and knowing what to do when something inevitably breaks.</p>
<p>More documentation will be added as the homelab evolves.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
