Ah, yeah. That's currently the expected behavior of Net::SSH, but I agree that it should not override 'user' if user is explicitly set. I'd accept a patch for that, probably.
- Jamis On May 7, 2008, at 11:39 AM, David James wrote: > > $ cap -v staging shell > cap> whoami > [establishing connection(s) to 67.207.145.254] > ** [out :: 67.207.145.254] djames > > Strange, considering that I have: > set :user, "deploy" > in deploy.rb > > Relevant parts in staging.rb: > role :app, "xx.xxx.xxx.xxx" > role :web, "xx.xxx.xxx.xxx" > role :db, "xx.xxx.xxx.xxx", :primary => true > (I don't do any [EMAIL PROTECTED]:PORT syntax, that's why I show > this) > > My initial guess was that cap is logging me in as "djames" because of > my ~/.ssh/config: > Host xx.xxx.xxx.xxx > User djames > Port yyyy > Protocol 2 > > I confirmed this by commenting out the "User" line and everything > worked as expected. > > Is this the desired behavior of Cap -- namely that a config file > username takes precedence over "set :user"? > > Thanks, > David > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
