<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Named-Volumes on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/named-volumes/</link><description>Recent content in Named-Volumes on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Mon, 27 Jul 2026 04:24:13 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/named-volumes/index.xml" rel="self" type="application/rss+xml"/><item><title>The Third State: When Your Checkout, Image, and Docker Volume All Disagree</title><link>https://startaitools.com/posts/checkout-image-volume-three-way-drift/</link><pubDate>Sun, 26 Jul 2026 08:00:00 -0500</pubDate><guid>https://startaitools.com/posts/checkout-image-volume-three-way-drift/</guid><description>&lt;p&gt;A rebuild succeeded. Docker reported healthy. The site served the same bytes it had been serving for weeks.&lt;/p&gt;
&lt;p&gt;That was July on &lt;code&gt;now-lms&lt;/code&gt;, a fork of an open source Flask learning management system that Intent Solutions runs in production at &lt;code&gt;learn.intentsolutions.io&lt;/code&gt; (Contabo VPS, Docker Compose, PostgreSQL 16, Caddy in front). Fork issue #14 recorded the actual problem: nobody could answer &amp;ldquo;what is deployed?&amp;rdquo; without shelling into the running container and hashing files by hand. Three artifacts each claimed a different answer.&lt;/p&gt;</description></item></channel></rss>