<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Homelab on Notes</title><link>http://www.henryleach.com/tags/homelab/</link><description>Recent content in Homelab on Notes</description><generator>Hugo</generator><language>en-GB</language><copyright>© Henry Leach</copyright><lastBuildDate>Sat, 28 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://www.henryleach.com/tags/homelab/index.xml" rel="self" type="application/rss+xml"/><item><title>Basic Intrusion Detection System with mtree</title><link>http://www.henryleach.com/2026/03/basic-intrusion-detection-system-with-mtree/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>http://www.henryleach.com/2026/03/basic-intrusion-detection-system-with-mtree/</guid><description>&lt;p&gt;
After the &lt;a href="http://www.henryleach.com/2026/03/basic-freebsd-server-setup/"&gt;very basic server setup&lt;/a&gt;, having some kind of simple Intrusion Detection System (IDS) seems like a good idea. While all the previous steps were designed to prevent someone taking control of your server, if someone &lt;em&gt;has&lt;/em&gt; managed to tamper with something, short of being locked out - how would you know?&lt;/p&gt;</description></item><item><title>Basic FreeBSD Server Setup</title><link>http://www.henryleach.com/2026/03/basic-freebsd-server-setup/</link><pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate><guid>http://www.henryleach.com/2026/03/basic-freebsd-server-setup/</guid><description>&lt;p&gt;
Since starting with FreeBSD for my homelab and self-hosting experiments, I&amp;#39;ve come up with a few standard first steps that I do to any new server.&lt;/p&gt;</description></item><item><title>Setting Up a Simple Git Server - Gitweb: The Unexpected Part 2</title><link>http://www.henryleach.com/2025/06/setting-up-a-simple-git-server-gitweb-the-unexpected-part-2/</link><pubDate>Sun, 15 Jun 2025 00:00:00 +0000</pubDate><guid>http://www.henryleach.com/2025/06/setting-up-a-simple-git-server-gitweb-the-unexpected-part-2/</guid><description>&lt;p&gt;
A few weeks ago I set up a simple &lt;a href="http://www.henryleach.com/2025/05/setting-up-a-simple-git-server/"&gt;git server&lt;/a&gt; to run at home so I don&amp;#39;t have to rely on Github or similar external services. That worked fine, but two things felt unfinished: The ability to create a new repository, and an easy way of listing the existing ones, without having to SSH into the host. Luckily with GitWeb, shell scripts and CGI magic we can fix that.&lt;/p&gt;</description></item><item><title>Setting Up A Simple Git Server</title><link>http://www.henryleach.com/2025/05/setting-up-a-simple-git-server/</link><pubDate>Sat, 10 May 2025 00:00:00 +0000</pubDate><guid>http://www.henryleach.com/2025/05/setting-up-a-simple-git-server/</guid><description>&lt;p&gt;
I wanted a local Git server on my home network to store some repositories without relying on GitHub for everything. I don&amp;#39;t need a web interface, so the built &lt;a href="https://git-scm.com/docs/git-http-backend"&gt;&lt;code&gt;git-http-backend&lt;/code&gt;&lt;/a&gt; should be enough. Combined with a web server&amp;#39;s access permissions I can have anonymous cloning, protected pushing and private repositories.&lt;/p&gt;</description></item></channel></rss>