
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>susi.dev</title>
      <link>https://susi.dev/blog</link>
      <description>Personal site and blog of Susi</description>
      <language>en-us</language>
      <managingEditor>look+fromweb@susi.dev (Susi)</managingEditor>
      <webMaster>look+fromweb@susi.dev (Susi)</webMaster>
      <lastBuildDate>Tue, 11 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://susi.dev/tags/comparison/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://susi.dev/blog/shippy-vs-deployer-vs-capistrano</guid>
    <title>Shippy vs. Deployer vs. Capistrano</title>
    <link>https://susi.dev/blog/shippy-vs-deployer-vs-capistrano</link>
    <description>All three deploy zero-downtime releases with the same releases/current/shared symlink pattern — Capistrano invented it, Deployer and Shippy both cite it as their inspiration. The real differences are the runtime each one needs to deploy, the config format, and what ships built in beyond the deploy itself.</description>
    <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
    <author>look+fromweb@susi.dev (Susi)</author>
    <category>shippy</category><category>deployer</category><category>capistrano</category><category>deployment</category><category>comparison</category><category>php</category><category>devops</category>
  </item>

    </channel>
  </rss>
