<?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>Self-Hosting on 4sh.dev</title>
    <link>https://4sh.dev/tags/self-hosting/</link>
    <description>Recent content in Self-Hosting on 4sh.dev</description>
    <image>
      <title>4sh.dev</title>
      <url>https://4sh.dev/images/Ash-Drawing.jpg</url>
      <link>https://4sh.dev/images/Ash-Drawing.jpg</link>
    </image>
    <generator>Hugo -- 0.147.9</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://4sh.dev/tags/self-hosting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>One Changelog for Everything: updates.4sh.dev</title>
      <link>https://4sh.dev/posts/2026/building-updates-site/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/building-updates-site/</guid>
      <description>updates.4sh.dev is one changelog for all my apps, built from GitHub releases and the App Store, with a small JSON feed that Codex now reads to tell admins what&amp;#39;s new.</description>
    </item>
    <item>
      <title>Codex Reader: A Native iOS App for My Library</title>
      <link>https://4sh.dev/posts/2026/building-codex-reader/</link>
      <pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/building-codex-reader/</guid>
      <description>Codex Reader is out on the App Store: a native iOS and iPad reader for a self-hosted Codex library, with real offline reading and the Codex features generic clients can&amp;#39;t reach.</description>
    </item>
    <item>
      <title>Reviving an IoT Project: thetalink</title>
      <link>https://4sh.dev/posts/2026/reviving-thetalink/</link>
      <pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/reviving-thetalink/</guid>
      <description>Reviving an old LoRa plant-monitoring idea as thetalink: a local-first, long-range sensing platform for whole properties, with a hub that works without the internet.</description>
    </item>
    <item>
      <title>Codex, Nine Months In</title>
      <link>https://4sh.dev/posts/2026/codex-nine-months-in/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/codex-nine-months-in/</guid>
      <description>Five months after the last update: Codex 2.0, reading progress that finally syncs properly across devices, multi-instance deployments, and the groundwork for a native iOS app.</description>
    </item>
    <item>
      <title>Tsundoku Update: Closing the Loop with Codex</title>
      <link>https://4sh.dev/posts/2026/tsundoku-after-v1-10/</link>
      <pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/tsundoku-after-v1-10/</guid>
      <description>A short Tsundoku update: Codex and Tsundoku now talk in both directions, plus a wishlist and per-series search for the series the feed never shows.</description>
    </item>
    <item>
      <title>Building Mnemo: A Memory Layer My Agents and I Share</title>
      <link>https://4sh.dev/posts/2026/building-mnemo/</link>
      <pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/building-mnemo/</guid>
      <description>Mnemo is a self-hosted memory layer for me and my agents: decisions, notes, snippets, links and files in one place, reachable from Claude over MCP.</description>
    </item>
    <item>
      <title>Building Tsundoku: Turning a Firehose of Manga Releases into a Browsable Backlog</title>
      <link>https://4sh.dev/posts/2026/building-tsundoku/</link>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/building-tsundoku/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/Tsundoku&#34;&gt;積ん読 (tsundoku)&lt;/a&gt; is the Japanese word for the habit of acquiring books and letting them pile up unread. It&amp;rsquo;s an affectionate kind of self-deprecation, and it&amp;rsquo;s an uncomfortably accurate description of how I read manga. There&amp;rsquo;s always a new series I&amp;rsquo;ve heard is good, a sequel that just got a fresh volume, a thing someone mentioned in passing that I meant to look into. The pile only grows.&lt;/p&gt;
&lt;p&gt;A few months ago I wrote about &lt;a href=&#34;https://4sh.dev/posts/2026/building-codex/&#34;&gt;Codex&lt;/a&gt;, the Rust digital library server I built to manage the comics, manga, and ebooks I already own. Codex is great at the &amp;ldquo;own&amp;rdquo; part. It scans my files, fetches metadata, tracks what I have. But it has nothing to say about the part that actually feeds the collection: &lt;strong&gt;discovery&lt;/strong&gt;. What&amp;rsquo;s new? What got a new volume since I last looked? What have I been meaning to start but never got around to?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Codex, Three Months In</title>
      <link>https://4sh.dev/posts/2026/codex-three-months-in/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/codex-three-months-in/</guid>
      <description>Three months of daily-driving Codex: release tracking, a maturing plugin system, and the unglamorous polish that makes a side project feel lived-in.</description>
    </item>
    <item>
      <title>Why I&#39;m Building Codex: A Digital Library Server in Rust</title>
      <link>https://4sh.dev/posts/2026/building-codex/</link>
      <pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/building-codex/</guid>
      <description>&lt;p&gt;I love &lt;a href=&#34;https://komga.org/&#34;&gt;Komga&lt;/a&gt;. It&amp;rsquo;s been my go-to for managing comics, manga, and ebooks for years, and it genuinely does the job well. The UI is clean, the feature set is rich, and the community around it is great. If you self-host a digital reading collection and haven&amp;rsquo;t tried it, you should.&lt;/p&gt;
&lt;p&gt;But after years of daily use, I kept bumping into a few limitations that I couldn&amp;rsquo;t work around. And eventually, the itch to build something of my own became too strong to ignore.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
