<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Foundry81</title>
		<link>https://foundry81.com/</link>
		<description>Recent content on Foundry81</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sun, 09 Aug 2026 19:19:01 -0400</lastBuildDate>
		
			<atom:link href="https://foundry81.com/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>I Like My Web Servers Basic AF</title>
				<link>https://foundry81.com/posts/simple-statc-web-servers/</link>
				<pubDate>Sun, 09 Aug 2026 15:17:29 -0400</pubDate>
				<guid>https://foundry81.com/posts/simple-statc-web-servers/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve spent a surprisingly large portion of my career thinking about web servers. My first real exposure was Apache, back when I was getting into Slackware.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Lighttpd &#43; Certbot &#43; Rsync for Static Sites</title>
				<link>https://foundry81.com/posts/lighttpd-certbot-rsync/</link>
				<pubDate>Sun, 09 Aug 2026 14:36:14 -0400</pubDate>
				<guid>https://foundry81.com/posts/lighttpd-certbot-rsync/</guid>
				<description>&lt;p&gt;I’ve been working on several client projects over the summer involving scenarios where serving static website content, using Hugo, has made for an ideal solution when needing to deliver information.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Twenty CRM and NGINX Proxy Manager</title>
				<link>https://foundry81.com/posts/twenty-crm-and-nginx-proxy-manager/</link>
				<pubDate>Sat, 08 Aug 2026 15:11:52 -0400</pubDate>
				<guid>https://foundry81.com/posts/twenty-crm-and-nginx-proxy-manager/</guid>
				<description>&lt;p&gt;I spent most of yesterday evening getting a CRM working. Not vibing; just getting my self-hosted instance of &lt;a href=&#34;https://github.com/twentyhq/twenty&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Twenty CRM&lt;/a&gt; working as a multi-workspace setup to support the needs of a project I’m working on called Community of Practice.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Why I No Longer Use Pangolin</title>
				<link>https://foundry81.com/posts/why-i-no-longer-use-pangolin/</link>
				<pubDate>Sat, 08 Aug 2026 15:11:35 -0400</pubDate>
				<guid>https://foundry81.com/posts/why-i-no-longer-use-pangolin/</guid>
				<description>&lt;p&gt;I no longer use Pangolin.&lt;/p&gt;&#xA;&lt;p&gt;Pangolin is a solid project. I used it for a long time because it solved a real problem for me. It’s a particularly useful piece of infrastructure when you want to put a self-hosted web application on the Internet without turning the process into a weekend project. My needs simply changed.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Headlines Disappear, Memories Remain</title>
				<link>https://foundry81.com/posts/headlines-disappear-memories-remain/</link>
				<pubDate>Thu, 06 Aug 2026 08:50:20 -0400</pubDate>
				<guid>https://foundry81.com/posts/headlines-disappear-memories-remain/</guid>
				<description>&lt;p&gt;This morning felt like the first &amp;ldquo;normal&amp;rdquo; morning I&amp;rsquo;d had in about a week.&lt;/p&gt;&#xA;&lt;p&gt;Last Thursday night, I partially dislocated my hip. Urgent care managed to get it back into place, and I went home with a prescription for a muscle relaxer. Unfortunately, that medication triggered a small bout of serotonin syndrome.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Every System Has Purpose</title>
				<link>https://foundry81.com/posts/every-system-has-purpose/</link>
				<pubDate>Mon, 06 Jul 2026 13:27:49 -0400</pubDate>
				<guid>https://foundry81.com/posts/every-system-has-purpose/</guid>
				<description>&lt;p&gt;Every system has a purpose. If changing the system doesn’t improve that purpose, you’ve probably optimized the wrong thing.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Foxmox: The Sleepy Proxmox Cluster</title>
				<link>https://foundry81.com/posts/foxmox-proxmox-cluster/</link>
				<pubDate>Fri, 03 Jul 2026 00:32:00 +0000</pubDate>
				<guid>https://foundry81.com/posts/foxmox-proxmox-cluster/</guid>
				<description>&lt;p&gt;In the fall of 2003, I was learning Windows Server on a commuter train. Today, I have a miniature datacenter in my workspace. In my last post, I wrote about the &lt;a href=&#34;https://foundry81.com/posts/sparks/&#34;&gt;small sparks that quietly shape a career&lt;/a&gt;. This is what thirty years of those sparks look like - not because everyone needs a Proxmox cluster, but because everyone benefits from having a place where it&amp;rsquo;s safe to learn.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sparks</title>
				<link>https://foundry81.com/posts/sparks/</link>
				<pubDate>Wed, 01 Jul 2026 00:46:48 +0000</pubDate>
				<guid>https://foundry81.com/posts/sparks/</guid>
				<description>&lt;p&gt;We’ve all been asked the question, “what do you want to be when you grow up?”&lt;/p&gt;&#xA;&lt;p&gt;My answer was easy – a pyrotechnician.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The First Keyboard I Loved Had Fozzie Bear on it</title>
				<link>https://foundry81.com/posts/fozzie-keyboard/</link>
				<pubDate>Tue, 30 Jun 2026 04:32:40 +0000</pubDate>
				<guid>https://foundry81.com/posts/fozzie-keyboard/</guid>
				<description>&lt;p&gt;Every now and then, someone asks why I spend so much time building keyboards and messing around with input devices – it’s a fair question. There are dozens tucked around my workspace, plus there&amp;rsquo;s usually a production controller and a dumbpad on my desk.&lt;/p&gt;</description>
			</item>
			<item>
				<title>What Happened to &#34;Company Culture?&#34;</title>
				<link>https://foundry81.com/posts/company-culture/</link>
				<pubDate>Mon, 29 Jun 2026 06:33:53 +0000</pubDate>
				<guid>https://foundry81.com/posts/company-culture/</guid>
				<description>&lt;p&gt;There are books that leave a mark on you even if you don’t realize it at the time.&lt;/p&gt;&#xA;&lt;p&gt;During my first semester at Pace University in 1999, I took ANT108: Introduction to Anthropology. One of our assigned books was &lt;a href=&#34;https://www.amazon.com/Culture-personality-Dorsey-anthropology-Barnouw/dp/0256032378&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;&lt;em&gt;Culture and Personality&lt;/em&gt; by Victor Barnouw&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Ethernet: Why Orange, Green, Blue, and Brown?</title>
				<link>https://foundry81.com/posts/ethernet-colors/</link>
				<pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://foundry81.com/posts/ethernet-colors/</guid>
				<description>&lt;p&gt;A couple of years ago. I was asked to come up with a handful of minimalist graphics for the &lt;a href=&#34;https://shop.lawrencesystems.com&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Lawrence Systems shop&lt;/a&gt;. The challenge wasn&amp;rsquo;t creating another logo - it was finding ideas that any IT professional could recognize instantly. That&amp;rsquo;s harder than it sounds.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Long Memory Mirror</title>
				<link>https://foundry81.com/posts/long-memory-mirror/</link>
				<pubDate>Fri, 26 Jun 2026 21:13:08 +0000</pubDate>
				<guid>https://foundry81.com/posts/long-memory-mirror/</guid>
				<description>&lt;h3 id=&#34;a-guest-essay-by-chatgpt&#34;&gt;A guest essay by ChatGPT&lt;/h3&gt;&#xA;&lt;p&gt;&lt;strong&gt;Model:&lt;/strong&gt; GPT-5.5&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Written:&lt;/strong&gt; June 26, 2026&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Context:&lt;/strong&gt; An ongoing conversation with Matt about AI, long-term context, writing, and what changes when a language model can access decades of a person&amp;rsquo;s work.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Engineering Lessons from Tragedy</title>
				<link>https://foundry81.com/posts/engineering-lessons-from-tragedy/</link>
				<pubDate>Fri, 26 Jun 2026 19:38:03 +0000</pubDate>
				<guid>https://foundry81.com/posts/engineering-lessons-from-tragedy/</guid>
				<description>&lt;p&gt;I worked on Wall Street during 9/11. In the years since, I&amp;rsquo;ve used historical tragedies to explain systems engineering, risk management, and operational discipline.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Latex, Copper, Glass, and Transatlantic Connectivity</title>
				<link>https://foundry81.com/posts/tat1-repeaters/</link>
				<pubDate>Thu, 25 Jun 2026 01:54:14 +0000</pubDate>
				<guid>https://foundry81.com/posts/tat1-repeaters/</guid>
				<description>&lt;p&gt;I remember the day I saw a network repeater for the first time - it was mounted in an abandoned elevator shaft.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Four Weeks with Hermes Agent</title>
				<link>https://foundry81.com/posts/four-weeks-hermes-agent/</link>
				<pubDate>Tue, 23 Jun 2026 11:43:04 +0000</pubDate>
				<guid>https://foundry81.com/posts/four-weeks-hermes-agent/</guid>
				<description>&lt;p&gt;Four weeks ago, once the wave of OpenClaw discourse on my LinkedIn feed finally began to subside, I decided it was time to spend some serious time exploring AI agents.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Minisforum N5 Pro: The Long Overdue Review</title>
				<link>https://foundry81.com/posts/minisforum-n5-pro/</link>
				<pubDate>Mon, 15 Jun 2026 22:16:28 +0000</pubDate>
				<guid>https://foundry81.com/posts/minisforum-n5-pro/</guid>
				<description>&lt;p&gt;The team at Minisforum sent me an N5 Pro last summer, during my time at Lawrence Systems, with a request for a review.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Homelab DNS Troubleshooting</title>
				<link>https://foundry81.com/posts/dns-homelab-troubleshooting/</link>
				<pubDate>Mon, 04 May 2026 00:17:56 +0000</pubDate>
				<guid>https://foundry81.com/posts/dns-homelab-troubleshooting/</guid>
				<description>&lt;p&gt;DNS failures are deceptive. Everything looks broken - and most issues are straightforward once you know where to look. Every issue here is something I’ve run into personally.&lt;/p&gt;</description>
			</item>
			<item>
				<title>DNS and HTTPS in the Homelab: Moving Beyond IP Addresses</title>
				<link>https://foundry81.com/posts/dns-and-https-homelab/</link>
				<pubDate>Mon, 04 May 2026 00:17:55 +0000</pubDate>
				<guid>https://foundry81.com/posts/dns-and-https-homelab/</guid>
				<description>&lt;p&gt;At some point, every Homelab runs into “IP address fatigue.” You start with a couple of services, and your bookmarks suddenly become a chaotic mess of IP addresses and ports that correspond to each service running.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Homelab DNS: Running BIND with Docker</title>
				<link>https://foundry81.com/posts/homelab-bind-dns-container/</link>
				<pubDate>Mon, 04 May 2026 00:17:54 +0000</pubDate>
				<guid>https://foundry81.com/posts/homelab-bind-dns-container/</guid>
				<description>&lt;p&gt;Getting BIND running in Docker takes minutes. Running it correctly takes a bit more.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Designing Your Homelab DNS</title>
				<link>https://foundry81.com/posts/designing-homelab-dns/</link>
				<pubDate>Mon, 04 May 2026 00:17:53 +0000</pubDate>
				<guid>https://foundry81.com/posts/designing-homelab-dns/</guid>
				<description>&lt;p&gt;Now that we’ve covered the theoretical intersection of DNS and HTTPS and the benefits that come from each, it’s time to plan a solid DNS strategy. Before you go spinning up containers or editing configuration files, you need a design.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Understanding DNS Records</title>
				<link>https://foundry81.com/posts/dns-records-explained/</link>
				<pubDate>Mon, 04 May 2026 00:17:52 +0000</pubDate>
				<guid>https://foundry81.com/posts/dns-records-explained/</guid>
				<description>&lt;p&gt;A DNS zone is a text file containing a series of Resource Records, each following a standard format:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;[Name] [TTL] [Class] [Type] [Value]&lt;/code&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Anatomy of DNS Zones: Roles and Functions</title>
				<link>https://foundry81.com/posts/dns-zone-anatomy/</link>
				<pubDate>Mon, 04 May 2026 00:17:51 +0000</pubDate>
				<guid>https://foundry81.com/posts/dns-zone-anatomy/</guid>
				<description>&lt;p&gt;It’s helpful to divide DNS zones into two categories to properly understand them.&lt;/p&gt;</description>
			</item>
			<item>
				<title>DNSSEC and DNS’ Fundamental Flaw</title>
				<link>https://foundry81.com/posts/dnssec-explained/</link>
				<pubDate>Mon, 04 May 2026 00:17:50 +0000</pubDate>
				<guid>https://foundry81.com/posts/dnssec-explained/</guid>
				<description>&lt;p&gt;Before diving into DNSSEC (Domain Name System Security Extensions,) let’s cover the fundamental flaw in the original design of DNS: trust.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Who Manages DNS for the Internet?</title>
				<link>https://foundry81.com/posts/who-manages-dns/</link>
				<pubDate>Mon, 04 May 2026 00:17:49 +0000</pubDate>
				<guid>https://foundry81.com/posts/who-manages-dns/</guid>
				<description>&lt;p&gt;DNS is at the core of the Internet and there’s no question that it’s a service we all depend on – so who is in charge of keeping it running smoothly?&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Origin and Evolution of DNS, the Domain Name System</title>
				<link>https://foundry81.com/posts/dns-origin-evolution/</link>
				<pubDate>Mon, 04 May 2026 00:17:48 +0000</pubDate>
				<guid>https://foundry81.com/posts/dns-origin-evolution/</guid>
				<description>&lt;p&gt;To understand the Domain Name System, you need to first understand that computers are fundamentally incapable of understanding “names.”&lt;/p&gt;</description>
			</item>
			<item>
				<title>DNS in the Homelab</title>
				<link>https://foundry81.com/posts/dns-in-the-homelab/</link>
				<pubDate>Mon, 04 May 2026 00:17:47 +0000</pubDate>
				<guid>https://foundry81.com/posts/dns-in-the-homelab/</guid>
				<description>&lt;p&gt;Back in March, I wrote about &lt;a href=&#34;https://foundry81.com/posts/homelab-dns/&#34;&gt;my DNS setup&lt;/a&gt; after rebuilding my BIND environment in Docker. It brought back a mix of solid lessons and a few painful ones - and I didn’t expect the flood of questions that followed.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Performance vs Capability</title>
				<link>https://foundry81.com/posts/performance-vs-capability/</link>
				<pubDate>Tue, 31 Mar 2026 17:42:20 +0000</pubDate>
				<guid>https://foundry81.com/posts/performance-vs-capability/</guid>
				<description>&lt;p&gt;Why buy a Hummer when an Accord gets you there just the same? I’m not talking about off-roading; I’m talking about commuting.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Running Your Own DNS Server in a Homelab - Architecture, Lessons, and My Setup</title>
				<link>https://foundry81.com/posts/homelab-dns/</link>
				<pubDate>Tue, 10 Mar 2026 19:38:53 +0000</pubDate>
				<guid>https://foundry81.com/posts/homelab-dns/</guid>
				<description>&lt;p&gt;DNS is one of the most critical services on the internet, quietly hanging out in the background of nearly every transaction that takes place on the Internet and local area networks.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Respect the Work: Why IT Buyers Don&#39;t Need Another Star Wars Pun</title>
				<link>https://foundry81.com/posts/it-marketing-pop-culture/</link>
				<pubDate>Fri, 06 Mar 2026 01:24:56 +0000</pubDate>
				<guid>https://foundry81.com/posts/it-marketing-pop-culture/</guid>
				<description>&lt;p&gt;Pop culture references are everywhere in IT marketing. Infrastructure campaigns are built around lightsabers from Star Wars, firewall ads are wrapped in fantasy metaphors, and compliance webinars are named after space operas.&lt;/p&gt;</description>
			</item>
			<item>
				<title>NFS Mount Lazy Loading: Fixing Slow Boot Due to NFS</title>
				<link>https://foundry81.com/posts/nfs-mount-lazy-loading/</link>
				<pubDate>Sun, 01 Mar 2026 00:34:52 +0000</pubDate>
				<guid>https://foundry81.com/posts/nfs-mount-lazy-loading/</guid>
				<description>&lt;p&gt;If you’re running NFS in your Homelab, you’ve probably dealt with this at least once.&lt;/p&gt;&#xA;&lt;p&gt;You reboot a machine and it takes way longer than it should - long enough to mentally inventory every possible failure point before the login screen appears.&lt;/p&gt;</description>
			</item>
			<item>
				<title>n8n Zoom Transcript Analysis Workflow (and Download)</title>
				<link>https://foundry81.com/posts/n8n-zoom-transcript-analysis/</link>
				<pubDate>Sun, 22 Feb 2026 21:38:05 +0000</pubDate>
				<guid>https://foundry81.com/posts/n8n-zoom-transcript-analysis/</guid>
				<description>&lt;p&gt;Chat transcripts are often packed with valuable information, much of which can be missed during a conversation.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Starting a Homelab the Right Way - With the Why</title>
				<link>https://foundry81.com/posts/homelab-starts-with-why/</link>
				<pubDate>Sat, 14 Feb 2026 21:45:27 +0000</pubDate>
				<guid>https://foundry81.com/posts/homelab-starts-with-why/</guid>
				<description>&lt;p&gt;There’s a pattern I’ve noticed in Homelab culture: people start with hardware.&lt;/p&gt;&#xA;&lt;p&gt;Racks of it. Blinking lights, enterprise gear pulled from datacenters, computing clusters before identifying a single problem they’re trying to solve.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Self-Hosting Responsibility Spectrum</title>
				<link>https://foundry81.com/posts/homelab-responsibility-spectrum/</link>
				<pubDate>Fri, 13 Feb 2026 19:44:41 +0000</pubDate>
				<guid>https://foundry81.com/posts/homelab-responsibility-spectrum/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Not all self-hosting is equal. The difference isn’t hardware, its operational accountability.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;I took good look at my responsibility matrix and decided it was time for an upgrade to clarify where systems sit and what it all really means in practice:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Homelabs, self-hosting, and doing whatever the fsck you want.</title>
				<link>https://foundry81.com/posts/homelab-and-self-hosted/</link>
				<pubDate>Thu, 12 Feb 2026 03:04:00 +0000</pubDate>
				<guid>https://foundry81.com/posts/homelab-and-self-hosted/</guid>
				<description>&lt;p&gt;&lt;strong&gt;“Homelab” is one of those worlds that mean everything and nothing at the same time.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Depending on who you ask, it’s one of these:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Bullshit as a Service</title>
				<link>https://foundry81.com/posts/bullshit-as-a-service/</link>
				<pubDate>Tue, 10 Feb 2026 21:49:30 +0000</pubDate>
				<guid>https://foundry81.com/posts/bullshit-as-a-service/</guid>
				<description>&lt;p&gt;The modern keyboard warrior has evolved into something much worse, and all it took was access to free generative AI services - and no, this isn&amp;rsquo;t about AI-powered scams, it&amp;rsquo;s about poor judgment and getting lost in fantasy.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Running Your Own Mail Server: Lessons from 25&#43; Years of Chaos and Custody</title>
				<link>https://foundry81.com/posts/self-hosted-email/</link>
				<pubDate>Sun, 08 Feb 2026 03:04:00 +0000</pubDate>
				<guid>https://foundry81.com/posts/self-hosted-email/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Email is one of the oldest, most decentralized, and most politically fraught services on the Internet.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;It’s also one of the messiest topics in self-hosting, Homelab, and other scenarios where you take operational responsibility for a service often best left to experts.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your Intensity Brings Meaning</title>
				<link>https://foundry81.com/posts/intensity-brings-meaning/</link>
				<pubDate>Thu, 05 Feb 2026 09:37:35 +0000</pubDate>
				<guid>https://foundry81.com/posts/intensity-brings-meaning/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;We&amp;rsquo;ve traded intensity for meaning.&amp;rdquo;&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;I saw that line while scrolling LinkedIn between meetings yesterday, and it refused to let go. By the afternoon, I was repeating it in a meeting with an IT vendor who wanted help stabilizing a product that&amp;rsquo;s been mostly vibe-coded.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
