<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deployment on Luther Monson</title>
    <link>https://luth.io/tags/deployment/</link>
    <description>Recent content in Deployment on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 08 Sep 2026 20:25:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/deployment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Zero-Dependency Deployments - Single Binary for WordPress</title>
      <link>https://luth.io/blog/2026/09/single-binary-wordpress/</link>
      <pubDate>Tue, 08 Sep 2026 20:25:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/09/single-binary-wordpress/</guid>
      <description>&lt;p&gt;The standard way to run a WordPress site is four services:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;nginx for HTTP and TLS&lt;/li&gt;&#xA;&lt;li&gt;php-fpm to run PHP&lt;/li&gt;&#xA;&lt;li&gt;MySQL for data&lt;/li&gt;&#xA;&lt;li&gt;Redis, once the site gets slow enough that someone installs an object cache plugin&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;That&amp;rsquo;s four processes and four config files. There are three sockets between them and four things to upgrade. For a&#xA;big site that&amp;rsquo;s fine. For a brochure site or a staging copy it&amp;rsquo;s absurd. The same goes for a PR preview, a box at the&#xA;edge, or a CI job that needs a real WordPress to test a plugin against.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
