I have added a new role (role :new_role, new_role) for some tasks
specific to that box.
Now the :setup (and other) tasks that have no role restrictions, and so
run for all roles, are trying to execute on the new_role box.
What is the simplest approach to having standard tasks NOT execute for
(I'm not after the deploy or update_code task here).
I want to have a task that will export code (not the rails app) from an
arbitrary part of the repository to an arbitrary location on the remote
host. Also, make no assumptions about logins/public keys; the windows
machine running the task,
I am having problems connecting from my Windows desktop to my :web box
(Solaris) using public key exchange.
Using SSH Secure Shell I can connect to the Unix box using public key,
but when I run a Capistrano task it prompts me for a password. My
Windows account is different than my unix
This is probably more of a unix question than Capistrano.
If I have several commands to string together, I know I can to that with
. But what do I do if I have several steps and I want them all
executed regardless of the success of prior commands.
An example might be a task to get my mongrel
The solution sort-of worked for me. The problem is the deploy dies
first time out since current_path doesn't yet exist.
I wound up adding an :after_setup that touches current_path so it
exists when deploy calls symlink.
Is there a way to get commands strung together with to run if the
prior
