 
<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Password-free deployments with Capistrano 2</title>
	<atom:link href="http://blog.adsdevshop.com/2008/01/04/password-free-deployments-with-capistrano-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.adsdevshop.com/2008/01/04/password-free-deployments-with-capistrano-2/</link>
	<description>Helping companies increase predicability and business agility.</description>
	<lastBuildDate>Tue, 16 Mar 2010 13:24:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert Dempsey</title>
		<link>http://blog.adsdevshop.com/2008/01/04/password-free-deployments-with-capistrano-2/comment-page-1/#comment-10204</link>
		<dc:creator>Robert Dempsey</dc:creator>
		<pubDate>Thu, 22 Oct 2009 06:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://rorblog.techcfl.com/2008/01/04/password-free-deployments-with-capistrano-2/#comment-10204</guid>
		<description>@blake: Great advice. Thanks.</description>
		<content:encoded><![CDATA[<p>@blake: Great advice. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.adsdevshop.com/2008/01/04/password-free-deployments-with-capistrano-2/comment-page-1/#comment-9903</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Tue, 15 Sep 2009 14:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://rorblog.techcfl.com/2008/01/04/password-free-deployments-with-capistrano-2/#comment-9903</guid>
		<description>Took me ages to find a solution for this so posting it here, since this was a key blog to get me on the way:

- deploy ability can be revoked from developer/machine as needed
- svn access can be revoked as needed
- developer knowledge of svn/deploy user passwords not required
- sudo is not required
- stored passwords not required
- sftp to target required

Thanks guys!

http://www.experts-exchange.com/Programming/Languages/Scripting/Ruby/RubyOnRails/Q_24731867.html</description>
		<content:encoded><![CDATA[<p>Took me ages to find a solution for this so posting it here, since this was a key blog to get me on the way:</p>
<p>- deploy ability can be revoked from developer/machine as needed<br />
- svn access can be revoked as needed<br />
- developer knowledge of svn/deploy user passwords not required<br />
- sudo is not required<br />
- stored passwords not required<br />
- sftp to target required</p>
<p>Thanks guys!</p>
<p><a href="http://www.experts-exchange.com/Programming/Languages/Scripting/Ruby/RubyOnRails/Q_24731867.html" rel="nofollow">http://www.experts-exchange.com/Programming/Languages/Scripting/Ruby/RubyOnRails/Q_24731867.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Dempsey</title>
		<link>http://blog.adsdevshop.com/2008/01/04/password-free-deployments-with-capistrano-2/comment-page-1/#comment-5891</link>
		<dc:creator>Robert Dempsey</dc:creator>
		<pubDate>Mon, 07 Jan 2008 04:42:42 +0000</pubDate>
		<guid isPermaLink="false">http://rorblog.techcfl.com/2008/01/04/password-free-deployments-with-capistrano-2/#comment-5891</guid>
		<description>@blake: Great advice. Thanks.</description>
		<content:encoded><![CDATA[<p>@blake: Great advice. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blake</title>
		<link>http://blog.adsdevshop.com/2008/01/04/password-free-deployments-with-capistrano-2/comment-page-1/#comment-5890</link>
		<dc:creator>Blake</dc:creator>
		<pubDate>Mon, 07 Jan 2008 01:44:40 +0000</pubDate>
		<guid isPermaLink="false">http://rorblog.techcfl.com/2008/01/04/password-free-deployments-with-capistrano-2/#comment-5890</guid>
		<description>My team accomplishes the same thing without having to relax security with sudo or encode passwords directly into the Capistrano recipes. What we do instead is use a single user for doing all deployments. Instead of a password, we all have an SSH key installed in ~/.ssh/authorized_keys on each machine. To initialize Subversion access, I logged in once to the deploy user&#039;s account and did an svn ls https://server/path/to/svn and entered the credentials, which are cached into ~/.subversion/. Then we run our Rails processes as the deployment user, so there&#039;s no need to use sudo at all for working with Mongrel.

This way lost laptops with source trees don&#039;t have keys to the kingdom and in the event of firing a developer, we just pull his SSH key from the shared account and he no longer has access. Problem solved.</description>
		<content:encoded><![CDATA[<p>My team accomplishes the same thing without having to relax security with sudo or encode passwords directly into the Capistrano recipes. What we do instead is use a single user for doing all deployments. Instead of a password, we all have an SSH key installed in ~/.ssh/authorized_keys on each machine. To initialize Subversion access, I logged in once to the deploy user&#8217;s account and did an svn ls <a href="https://server/path/to/svn" rel="nofollow">https://server/path/to/svn</a> and entered the credentials, which are cached into ~/.subversion/. Then we run our Rails processes as the deployment user, so there&#8217;s no need to use sudo at all for working with Mongrel.</p>
<p>This way lost laptops with source trees don&#8217;t have keys to the kingdom and in the event of firing a developer, we just pull his SSH key from the shared account and he no longer has access. Problem solved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
