You want to set ssh_options[:keys], which can be an array.  
The :host_key option says which kind of key you want the remote host  
(the host you are connecting to via Capistrano) to use, and you almost  
never care about that.

However, note that Capistrano doesn't use Net::SSH when connecting to  
your source repository--only when connecting to the destination host.  
Thus, you'll need to make sure that CVS (or whatever SCM you use) is  
using the right key to get at your source repo. That configuration is  
out of Capistrano's hands.

- Jamis

On Jun 2, 2008, at 3:11 PM, David K. wrote:

>
> I've been trolling over the internet for days trying to find a
> solution to a problem I'm having at work.  My understanding of the
> issue is likely incorrect so please, correct me if I'm wrong.
>
> I'm trying to deploy a Rails application at work from CVS using
> Capistrano (obviously).  There are a lot of comments and articles
> online saying to do this or that but perhaps my situation is a special
> case - I know it must boil down to SSH keys though. (I'm doing this
> from my Macbook btw, running Leopard).
>
> When I ssh to our CVS server a key gets added to my known_hosts file
> that is "ssh-rsa".  When I ssh to our dev box I get another key that
> is "ssh-dss".  Since I'm only aware of being able to set a single
> host_key in the deploy file are my issues a result of having 2
> different types of keys when Capistrano is trying to use only the one
> I define?
>
> The flip side of this is that if I run "cap deploy" and let it create
> the keys I get the same thing but if I do it through Capistrano I
> don't get a HostKeyMismatch error that I get when my keys are
> generated by simple ssh'ing in to the servers.
>
> Can I define one type of host_key for CVS and another for the app
> server?
> >


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to