<?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>Homelab on Hendrickx Consulting</title>
    <link>/tags/homelab/</link>
    <description>Recent content in Homelab on Hendrickx Consulting</description>
    <image>
      <title>Hendrickx Consulting</title>
      <url>/images/papermod-cover.png</url>
      <link>/images/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Hendrickx Consulting</copyright>
    <lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/homelab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Homepage Dashboard with Docker Autodiscovery</title>
      <link>/posts/homepage-autodiscovery-using-docker/</link>
      <pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate>
      <guid>/posts/homepage-autodiscovery-using-docker/</guid>
      <description>&lt;h2 id=&#34;ditching-homarr-for-homepage-with-docker-autodiscovery&#34;&gt;Ditching Homarr for Homepage with Docker Autodiscovery&lt;/h2&gt;
&lt;p&gt;Homarr has been running into memory issues on my homelab, and on top of that, every new service meant a manual trip into the UI to wire it up. That kind of overhead compounds quickly. Homepage fixes both: it is lighter, and it supports Docker label-based autodiscovery, meaning containers register themselves on the dashboard just by having the right labels.&lt;/p&gt;
&lt;h2 id=&#34;my-setup&#34;&gt;My Setup&lt;/h2&gt;
&lt;p&gt;Homepage runs on my main &lt;code&gt;lxc-homelab&lt;/code&gt; LXC container, alongside Traefik on the &lt;code&gt;proxy&lt;/code&gt; Docker network. A second container, &lt;code&gt;lxc-media&lt;/code&gt;, runs my media stack separately. Both need to show up on the dashboard, which is where things get slightly more involved.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
