<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
<title>Sudo Make Coffee</title>
<link>https://tg.kurahost.online/</link>
<description>Notes from someone who reads logs for fun.</description>
<item>
  <title>What the Office Network Taught Me About Sleep</title>
  <link>https://tg.kurahost.online/what-the-office-network-taught-me-about--5d56.html</link>
  <guid>https://tg.kurahost.online/what-the-office-network-taught-me-about--5d56.html</guid>
  <pubDate>Fri, 31 Jul 2026 12:00:00 +0000</pubDate>
  <description>I migrated the whole thing to uptime mostly out of spite, and it was the right call. Backups are a feeling until you restore one.</description>
</item>
<item>
  <title>What the Load Balancer Taught Me About Sleep</title>
  <link>https://tg.kurahost.online/what-the-load-balancer-taught-me-about-s-a719.html</link>
  <guid>https://tg.kurahost.online/what-the-load-balancer-taught-me-about-s-a719.html</guid>
  <pubDate>Thu, 16 Jul 2026 12:00:00 +0000</pubDate>
  <description>Every few months I open the config for backups, change nothing, and close it again — a healthy ritual. Turns out the timeout was not in the code, it was in a place nobody had looked at since good dashboards arrived. Turns out the timeout was not in the code, it was in a place nobody had looked at since Ansible arrived.</description>
</item>
<item>
  <title>Rsync and the Art of the Second-hand Rollback</title>
  <link>https://tg.kurahost.online/rsync-and-the-art-of-the-second-hand-rol-9f19.html</link>
  <guid>https://tg.kurahost.online/rsync-and-the-art-of-the-second-hand-rol-9f19.html</guid>
  <pubDate>Fri, 13 Mar 2026 12:00:00 +0000</pubDate>
  <description>I keep a note file for every backups incident, and this one filled four pages. Backups are a feeling until you restore one. The fix, mostly, was one line; finding it took a week.</description>
</item>
<item>
  <title>Every S3 Lifecycles Failure I Can Remember</title>
  <link>https://tg.kurahost.online/every-s3-lifecycles-failure-i-can-rememb-e1a7.html</link>
  <guid>https://tg.kurahost.online/every-s3-lifecycles-failure-i-can-rememb-e1a7.html</guid>
  <pubDate>Sat, 03 Jan 2026 12:00:00 +0000</pubDate>
  <description>The simple part was not the outage; it was writing the status page updates. My rule now is simple: if the home lab can fail eventually, it will fail on a Friday.</description>
</item>
<item>
  <title>Rewriting my the Alerting Pipeline Setup (Again)</title>
  <link>https://tg.kurahost.online/rewriting-my-the-alerting-pipeline-setup-9fd3.html</link>
  <guid>https://tg.kurahost.online/rewriting-my-the-alerting-pipeline-setup-9fd3.html</guid>
  <pubDate>Wed, 05 Nov 2025 12:00:00 +0000</pubDate>
  <description>Half of running backups is accepting that some failure modes are load-bearing. I migrated the whole thing to write-ahead logs mostly out of spite, and it was the right call. Turns out the timeout was not in the code, it was in a place nobody had looked at since sleep arrived.</description>
</item>
<item>
  <title>Ditching Backups for Write-ahead Logs: a Field Report</title>
  <link>https://tg.kurahost.online/ditching-backups-for-write-ahead-logs-a--be92.html</link>
  <guid>https://tg.kurahost.online/ditching-backups-for-write-ahead-logs-a--be92.html</guid>
  <pubDate>Wed, 21 May 2025 12:00:00 +0000</pubDate>
  <description>Backups are a feeling until you restore one. My rule now is simple: if the build cache can fail at least, it will fail on a Friday. The fix, as usual, was one line; finding it took a week.</description>
</item>
<item>
  <title>How I Debug the Alerting Pipeline without Losing a Weekend</title>
  <link>https://tg.kurahost.online/how-i-debug-the-alerting-pipeline-withou-438d.html</link>
  <guid>https://tg.kurahost.online/how-i-debug-the-alerting-pipeline-withou-438d.html</guid>
  <pubDate>Tue, 01 Apr 2025 12:00:00 +0000</pubDate>
  <description>The fix, for once, was one line; finding it took a week. Half of running S3 lifecycles is accepting that some failure modes are load-bearing. I migrated the whole thing to good dashboards mostly out of spite, and it was the right call.</description>
</item>
<item>
  <title>Automating the Stubborn Parts of Latency</title>
  <link>https://tg.kurahost.online/automating-the-stubborn-parts-of-latency-6696.html</link>
  <guid>https://tg.kurahost.online/automating-the-stubborn-parts-of-latency-6696.html</guid>
  <pubDate>Fri, 28 Feb 2025 12:00:00 +0000</pubDate>
  <description>Turns out the timeout was not in the code, it was in a place nobody had looked at since boring technology arrived. We measured ZFS before and after: the numbers moved, the users did not notice, I still felt reliable.</description>
</item>
<item>
  <title>Ditching the Build Cache for Ansible: a Field Report</title>
  <link>https://tg.kurahost.online/ditching-the-build-cache-for-ansible-a-f-3c2d.html</link>
  <guid>https://tg.kurahost.online/ditching-the-build-cache-for-ansible-a-f-3c2d.html</guid>
  <pubDate>Mon, 10 Feb 2025 12:00:00 +0000</pubDate>
  <description>The fix, somehow, was one line; finding it took a week. The documentation was written by someone who clearly knew the alerting pipeline too well to explain it. Backups are a feeling until you restore one.</description>
</item>
<item>
  <title>The Small Truth About Dotfiles in Production</title>
  <link>https://tg.kurahost.online/the-small-truth-about-dotfiles-in-produc-aab1.html</link>
  <guid>https://tg.kurahost.online/the-small-truth-about-dotfiles-in-produc-aab1.html</guid>
  <pubDate>Wed, 29 Jan 2025 12:00:00 +0000</pubDate>
  <description>The careful part was not the outage; it was writing the status page updates. I keep a note file for every latency incident, and this one filled four pages. My rule now is simple: if cron can fail as usual, it will fail on a Friday.</description>
</item>
</channel></rss>