Hello everyone.
I have just upgraded to Capistrano 2.1 and installed capistrano-ext
1.2 in order to use the multistage features.
Unfortunately, when attempting to deploy to either staging or
production, my setting for the svn_username variable appears to be
ignored in favor of the username that executes the cap command. Here
is an example of the output:
$ cap staging deploy
* executing `staging'
triggering start callbacks for `deploy'
* executing `multistage:ensure'
* executing `deploy'
* executing `deploy:update'
** transaction: start
* executing `deploy:update_code'
Authentication realm: <http://subversion.host:80> AuthRealm
Password for 'shelluser':
At that point I ctrl+c out of things. Here are the contents of my
various configuration files.
Capfile:
load 'deploy' if respond_to?(:namespace) # cap2 differentiator
Dir['vendor/plugins/*/recipes/*.rb'].each { |plugin| load(plugin) }
load 'config/deploy'
config/deploy.rb:
require 'capistrano/ext/multistage'
set :application, "theapp"
set :repository, "http://subversion.host/svn/#{application}/trunk";
set :svn_username, "theapp"
set(:svn_password) { Capistrano::CLI.password_prompt("Subversion
password: ") }
config/deploy/staging.rb:
role :web, "staging.com"
role :app, "staging.com"
role :db, "db.staging.com", :primary => true
set :deploy_to, "/home/staging/apps/#{application}" # defaults to "/u/
apps/#{application}"
set :user, "staging" # defaults to the currently logged in
user
set :use_sudo, false
desc "Restart the mongrel cluster"
task :restart, :roles => :app do
send(run_method, "cd #{current_path} && mongrel_rails
cluster::restart")
end
config/deploy/production.rb is similar to staging with different
values for the variables.
Can anyone imagine what might be going on?
Thanks much
/brian
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
