<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>deploy on Dr. SeViR</title><link>http://www.sevir.org/en/tags/deploy/</link><description>Recent content in deploy on Dr. SeViR</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 14 Feb 2015 10:00:00 +0200</lastBuildDate><atom:link href="http://www.sevir.org/en/tags/deploy/index.xml" rel="self" type="application/rss+xml"/><item><title>Deployer, a good alternative to Capistrano</title><link>http://www.sevir.org/en/blog/deployer-a-good-alternative-to-capistrano/</link><pubDate>Sat, 14 Feb 2015 10:00:00 +0200</pubDate><guid>http://www.sevir.org/en/blog/deployer-a-good-alternative-to-capistrano/</guid><description>&lt;p&gt;For a long time at DIGIO we&amp;rsquo;ve been going round in circles about how to deploy our projects to the server better. Our workflow was based on a Git repository that was updated from the server with a simple &lt;code&gt;git pull&lt;/code&gt;, so if anything went wrong we could reset to a version in the Git history.&lt;/p&gt;</description></item></channel></rss>