<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Development-Workflow on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/development-workflow/</link>
    <description>Recent content in Development-Workflow on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/development-workflow/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Compose Live-Reload Solutions: Docker Compose Watch vs Mutagen vs Docker-sync (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-24-docker-compose-live-reload-solutions-docker-compose-watch-vs-mutagen-vs-docker-sync/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-24-docker-compose-live-reload-solutions-docker-compose-watch-vs-mutagen-vs-docker-sync/</guid>
      <description>&lt;p&gt;Developing with Docker Compose has long had a pain point: code changes require rebuilding the image or restarting the container to take effect. Several solutions have emerged to enable live-reload — automatically syncing code changes from your host machine into running containers without rebuilds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
