<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: A Really Simple Capistrano Recipe</title>
	<atom:link href="http://morethanseven.net/posts/a-really-simple-capistrano-recipe/feed/" rel="self" type="application/rss+xml" />
	<link>http://morethanseven.net/posts/a-really-simple-capistrano-recipe/</link>
	<description>Morethanseven is where Gareth Rushgrove plays with the web</description>
	<pubDate>Fri, 16 May 2008 06:57:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: gareth</title>
		<link>http://morethanseven.net/posts/a-really-simple-capistrano-recipe/#comment-8741</link>
		<dc:creator>gareth</dc:creator>
		<pubDate>Mon, 28 Apr 2008 13:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/?p=218#comment-8741</guid>
		<description>@Simon I might duplicate the above recipe with Fabric if time permits as that would then amount to the sum total of all the documentation on the subject. Be interested in seeing your Django deploy script though.</description>
		<content:encoded><![CDATA[<p>@Simon I might duplicate the above recipe with Fabric if time permits as that would then amount to the sum total of all the documentation on the subject. Be interested in seeing your Django deploy script though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Scarfe</title>
		<link>http://morethanseven.net/posts/a-really-simple-capistrano-recipe/#comment-8740</link>
		<dc:creator>Simon Scarfe</dc:creator>
		<pubDate>Mon, 28 Apr 2008 13:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/?p=218#comment-8740</guid>
		<description>Deployment "recipes" and what not are something I've been exploring a fair bit recently. I looked at Capistrano and the Python-equivalent, Fabric - both of which are really good tools for performing this kinda job - my big issue was that anyone else checking out the project would need to have the right tool installed. Capistrano relies on a load of Ruby dependencies and Fabric is still quite early in its implementation (&#60; 6 months). So I essentially ripped-off the Fabric core and directly used the Paramiko Python package to create a Django custom command that does something incredibly similar to this recipe any time I type ./manage.py deploy.</description>
		<content:encoded><![CDATA[<p>Deployment &#8220;recipes&#8221; and what not are something I&#8217;ve been exploring a fair bit recently. I looked at Capistrano and the Python-equivalent, Fabric &#8211; both of which are really good tools for performing this kinda job &#8211; my big issue was that anyone else checking out the project would need to have the right tool installed. Capistrano relies on a load of Ruby dependencies and Fabric is still quite early in its implementation (< 6 months). So I essentially ripped-off the Fabric core and directly used the Paramiko Python package to create a Django custom command that does something incredibly similar to this recipe any time I type ./manage.py deploy.</p></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gareth</title>
		<link>http://morethanseven.net/posts/a-really-simple-capistrano-recipe/#comment-8739</link>
		<dc:creator>gareth</dc:creator>
		<pubDate>Mon, 28 Apr 2008 11:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/?p=218#comment-8739</guid>
		<description>In the above example I'm running an _svn export --force_ command on the remote server. This exports an entire copy of the repository contents into the specified folder minus all the subversion config files. No diff is going on, it always dumps the whole repository. Alternatively you could run set up the directory as a subversion working copy and then run _svn up_ to only update the files that have changed.</description>
		<content:encoded><![CDATA[<p>In the above example I&#8217;m running an <em>svn export&#8212;force</em> command on the remote server. This exports an entire copy of the repository contents into the specified folder minus all the subversion config files. No diff is going on, it always dumps the whole repository. Alternatively you could run set up the directory as a subversion working copy and then run <em>svn up</em> to only update the files that have changed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Pennell</title>
		<link>http://morethanseven.net/posts/a-really-simple-capistrano-recipe/#comment-8738</link>
		<dc:creator>Matthew Pennell</dc:creator>
		<pubDate>Mon, 28 Apr 2008 11:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/?p=218#comment-8738</guid>
		<description>What does the script/Capistrano actually do? Is there some diff comparison going on, or does it just copy everything out of your repos and onto the server?</description>
		<content:encoded><![CDATA[<p>What does the script/Capistrano actually do? Is there some diff comparison going on, or does it just copy everything out of your repos and onto the server?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
