<?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>Nginx on Michael Johnson</title>
    <link>https://ahze.net/tags/nginx/</link>
    <description>Recent content in Nginx on Michael Johnson</description>
    <image>
      <title>Michael Johnson</title>
      <url>https://ahze.net/images/profile.jpg</url>
      <link>https://ahze.net/images/profile.jpg</link>
    </image>
    <generator>Hugo -- 0.164.0</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 01 Jul 2026 10:00:00 -0400</lastBuildDate>
    <atom:link href="https://ahze.net/tags/nginx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Speeding Up FreeBSD Hosts &amp; Container Builds with a Local pkg Cache</title>
      <link>https://ahze.net/posts/caching-freebsd-packages/</link>
      <pubDate>Wed, 01 Jul 2026 10:00:00 -0400</pubDate>
      <guid>https://ahze.net/posts/caching-freebsd-packages/</guid>
      <description>&lt;p&gt;When you run FreeBSD in a homelab across multiple servers, VNET jails, or VMs, routine maintenance quickly reveals a hidden inefficiency. Every time you provision a new jail or update your fleet, each instance independently connects to public &lt;code&gt;pkg.FreeBSD.org&lt;/code&gt; mirrors to download identical packages. If you have a dozen jails running services that need Python, SQLite, or FFmpeg, your WAN connection downloads the exact same binary archives a dozen times.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
