<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systemd on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/systemd/</link><description>Recent content in Systemd on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Sun, 03 May 2026 07:14:29 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>Four production deploy gotchas: systemd, V8 JIT, tsc noEmit, Caddy</title><link>https://startaitools.com/posts/five-releases-fifteen-minutes-mandy-cutover-and-freeze-break/</link><pubDate>Sat, 02 May 2026 08:00:00 -0500</pubDate><guid>https://startaitools.com/posts/five-releases-fifteen-minutes-mandy-cutover-and-freeze-break/</guid><description>&lt;p&gt;Two release cadences collided on the same day. One was a thoughtful CI redesign that finally broke a four-month npm publish freeze across 400+ packages — good engineering, well-trodden ground. The other was a fifteen-minute production firefight on &lt;code&gt;mandy.intentsolutions.io&lt;/code&gt; that surfaced four cross-layer deploy gotchas you would never know to look for until they hit you. Five releases in fifteen minutes, six commits, four production fixes, and a sixth release for the next layer of the system. The firefight is the one worth keeping in your runbook.&lt;/p&gt;</description></item></channel></rss>