<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on flove · blog</title><link>https://flove.org/development/blog/categories/infrastructure/</link><description>Recent content in Infrastructure on flove · blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 01 Aug 2026 11:15:00 +0000</lastBuildDate><atom:link href="https://flove.org/development/blog/categories/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Infrastructure — how flove ships</title><link>https://flove.org/development/blog/posts/infrastructure-how-flove-ships/</link><pubDate>Sat, 01 Aug 2026 10:45:00 +0000</pubDate><guid>https://flove.org/development/blog/posts/infrastructure-how-flove-ships/</guid><category>Infrastructure</category><description>&lt;p&gt;Nobody talks about plumbing until it leaks. That&amp;rsquo;s the compliment flove pays its
infrastructure: it&amp;rsquo;s the least poetic part of the project, and the one
everything else stands on. This shelf is where the plumbing gets explained — how
flove runs, how it gets published, and what keeps it from falling over when the
network drops.&lt;/p&gt;
&lt;h2 id="whats-on-it"&gt;What&amp;rsquo;s on it&lt;/h2&gt;
&lt;p&gt;At the center is a &lt;strong&gt;self-hosted &lt;a href="https://gitea.io/"&gt;Gitea&lt;/a&gt; server&lt;/strong&gt;, running in
Docker on a machine in the same house that builds flove, holding &lt;strong&gt;eight
repositories&lt;/strong&gt;. It&amp;rsquo;s the wall of the workshop: private source lives behind it,
and only what&amp;rsquo;s meant to be public walks out.&lt;/p&gt;</description></item></channel></rss>