<?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 SQP Dev</title>
    <link>/tags/homelab/</link>
    <description>Recent content in Homelab on SQP Dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/homelab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agentic AI on Bitfrost — YouTube Playlists on Demand</title>
      <link>/posts/2026-05-20-n8n-agentic-playlists/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-20-n8n-agentic-playlists/</guid>
      <description>&lt;p&gt;And now for something completely different.&lt;/p&gt;&#xA;&lt;p&gt;Last time it was monitoring — metrics, dashboards, alerts. Serious infrastructure business. This time I wanted to see what happens when you put an AI agent on &lt;strong&gt;Bitfrost&lt;/strong&gt; and give it something genuinely frivolous to do: build YouTube playlists.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-idea&#34;&gt;The Idea&lt;/h2&gt;&#xA;&lt;p&gt;The workflow is simple. You type one line:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Docker Basics | Docker tutorial for beginners&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Left of the pipe is the playlist name. Right is the search topic. Hit enter. A few seconds later a private YouTube playlist exists, populated with real videos, curated by Claude.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building a Homelab Monitoring Stack from Scratch</title>
      <link>/posts/2026-05-19-homelab-monitoring/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-19-homelab-monitoring/</guid>
      <description>&lt;p&gt;If you run a home server, you probably have a rough idea of whether things are working — you can SSH in, run &lt;code&gt;top&lt;/code&gt;, check disk space, maybe peek at some logs. But that&amp;rsquo;s reactive. You only look when something feels wrong. Proper monitoring means you know before something breaks, or at the very least, you know the moment it does.&lt;/p&gt;&#xA;&lt;p&gt;This is the story of how I set up a full observability stack on my home server, &lt;strong&gt;bitfrost&lt;/strong&gt; — an Ubuntu 24.04 machine running several Docker-based apps.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
