No problem at all, Lee.
Before this thread goes cold, I figured I'd contribute a final post to
share my (not "the") final solution. I may have been remiss in my
contribution of one piece of critical information. Within my group,
development takes place on a central development server (rather than
on local workstations). We all use DSA keys to access the server. A
separate user ("deployuser") was created for deployment purposes on
our production servers. No surprises there.
I (needlessly) generated a DSA key-pair for my user ("devuser") on the
development server and registered the public key with "deployuser",
allowing access to production for deployment purposes. It's on the
development server that I was running into the need for key-caching
(ssh-agent is not configured to cache keys by default). What I SHOULD
have done (and now have done) was enabled agent-forwarding
("ForwardAgent yes") and registered my local workstation's public key
with "deployuser". As is common (and as you mentioned, Lee), my local
ssh-agent caches decrypted keys by default, allowing me to sign-in
effortlessly. With agent-forwarding enabled, I'm able to log into the
development server and deploy to production, without re-providing my
passphrase. No need for "default_run_options[:max_hosts] = 1" in my
deploy.rb, and no need to run "ssh-agent add ~/path/to/key" on the
development server. Problem solved.
Thanks again for the back and forth.
Best,
~ jeremy
On Sep 30, 12:34 pm, Lee Hambley <[email protected]> wrote:
> Jeremy,
>
> Glad it helped, sorry for the slightly crappy attitude this morning, just
> re-read the thread, think I chose the wrong side of the bed this
> morning. Take care, good luck deploying!
>
> - Lee
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
