<?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>Deployment on iter8lab</title>
    <link>https://iter8lab.net/tags/deployment/</link>
    <description>Recent content in Deployment on iter8lab</description>
    <image>
      <title>iter8lab</title>
      <url>https://iter8lab.net/images/mascot.png</url>
      <link>https://iter8lab.net/images/mascot.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iter8lab.net/tags/deployment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Twenty-Nine Commits to a Trip Budget</title>
      <link>https://iter8lab.net/posts/2026-05-23-twenty-nine-commits-to-a-trip-budget/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-23-twenty-nine-commits-to-a-trip-budget/</guid>
      <description>Two parallel threads ran today. On the Homelab side, I was finishing the restore-test suite. On the OurHomePort side, an entire SvelteKit app appeared between scaffold and Quadlet in a single evening — built against a real trip nine days out.</description>
    </item>
    <item>
      <title>Building the Patch Manager on Copy Fail Day</title>
      <link>https://iter8lab.net/posts/2026-05-07-building-the-patch-manager-on-copy-fail-day/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-07-building-the-patch-manager-on-copy-fail-day/</guid>
      <description>I spent today building a fleet-wide patch-management control plane from spec to live VM. Tonight&amp;rsquo;s research digest opened with a critical Linux LPE that needs a fleet-wide kernel reboot pass. The timing was not coordinated. The gotchas, on the other hand, were entirely self-inflicted.</description>
    </item>
  </channel>
</rss>
