use_sudo option in multistage

[Bryan Richardson]

Hi All,

Does :use_sudo work in multistage? I have a production stage that runs
on a server requiring sudo, but a staging stage that runs on a
different server not requiring sudo. I tried "set :use_sudo, false" in
my config/deploy/staging.rb file, but it looks like Capistrano is
still trying to execute some commands on the staging server using
sudo...

Any ideas?!

--
Thanks!
Bryan

[Lee Hambley]

Bryan,

Can you post said files as requested in the group notes.

-- Lee Hambley

Twitter: @leehambley | @capistranorb

[Bryan Richardson]

Sorry...

"ruby --version" => ruby 1.8.7 (2009-06-12 patchlevel 174) [i486-
linux]
"cap --version" => Capistrano v2.5.10

Rails environment:
Ruby version 1.8.7 (i486-linux)
RubyGems version 1.3.5
Rack version 1.0
Rails version 2.3.2
Active Record version 2.3.2
Action Pack version 2.3.2
Active Resource version 2.3.2
Action Mailer version 2.3.2
Active Support version 2.3.2
Environment development

The significant parts of the deploy config files are as follows:
config/deploy.rb:

after "deploy:symlink_file_space", "deploy:update_crontab"

namespace :deploy do
desc "Update the crontab file"
task :update_crontab, :roles => :db do
run "cd #{release_path} && whenever --update-crontab #
{application}"
end
end

config/deploy/staging.rb:

set :use_sudo, false

The staging server I'm using doesn't allow me to run anything as sudo,
so I set :use_sudo to false. However, when I deploy to the staging
server and it attempts to run the :update_crontab task above it tries
to run it as sudo...

Thanks for the help!

--
Bryan

[Lee Hambley]

Bryan, was this ever resolved?