
  <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>Thu, 30 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://susi.dev/tags/shippy/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://susi.dev/blog/shippy-continuous-backups-local-dev</guid>
    <title>Continuous Backups and Local Dev from Production with Shippy</title>
    <link>https://susi.dev/blog/shippy-continuous-backups-local-dev</link>
    <description>shippy backup produces a ZIP with a database dump and shared files; shippy gitlab:upload pushes it to a package registry. Wired into a scheduled GitLab CI pipeline that becomes an automated nightly off-server backup — and the same ZIP restores straight into DDEV for local development against real production data.</description>
    <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
    <author>look+fromweb@susi.dev (Susi)</author>
    <category>shippy</category><category>backup</category><category>devops</category><category>ci-cd</category><category>gitlab</category><category>typo3</category><category>ddev</category>
  </item>

  <item>
    <guid>https://susi.dev/blog/shippy-deploy-typo3-pimcore</guid>
    <title>Deploying TYPO3 and Pimcore with Shippy</title>
    <link>https://susi.dev/blog/shippy-deploy-typo3-pimcore</link>
    <description>Shippy is a single Go binary that deploys Composer-based PHP projects over SSH with zero-downtime, atomic releases. Real .shippy.yaml configs for TYPO3 v14 and Pimcore, the eight-step deploy process, and the bootstrap gotchas that only show up on a genuinely empty server.</description>
    <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
    <author>look+fromweb@susi.dev (Susi)</author>
    <category>shippy</category><category>typo3</category><category>pimcore</category><category>deployment</category><category>php</category><category>devops</category><category>ci-cd</category>
  </item>

  <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>
