<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosting on Devops Monk</title><link>https://blog.devops-monk.com/tags/self-hosting/</link><description>Recent content in Self-Hosting on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.devops-monk.com/tags/self-hosting/index.xml" rel="self" type="application/rss+xml"/><item><title>Filing45: Designing a System Around Documents That Fight Back</title><link>https://blog.devops-monk.com/2026/09/filing45-architecture/</link><pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/09/filing45-architecture/</guid><description>Filing45 publishes every stock trade disclosed by members of Congress, the fund managers who file 13Fs, and the executive branch — each row linked back to the filing it came from.
This post is not a feature tour. It is about the architecture: why the system is shaped the way it is, which constraints did the shaping, and where I got it wrong first.
The short version: almost every design decision in this system was forced by the documents, not chosen.</description></item></channel></rss>