Sorry Adam, I was referring to using the multistage module linked to by the previous poster: http://weblog.jamisbuck.org/2007/7/23/capistrano-multistage.
- Jamis On 7/28/07, Adam Salter <[EMAIL PROTECTED]> wrote: > > Jamis, How would I deploy to an individual stage using this technique? > I'm not familiar with the setup you describe... > > My own basic version was to do a normal deploy file and use: > > namespace :deploy do > task :testing, :roles => :app do > set :repository, "my_testing_repo" > set :depoy_to, "my_testing_dir" > set :deploy_via, :copy > set :copy_strategy, :export > deploy > end > end > > but the command deploy doesn't work because it's a sub-namespace (is > that the correct term? ;) > > On Jul 28, 11:16 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > You could set the repository in the config/deploy/testing.rb and > > config/deploy/production.rb files, so that each stage gets its own > > repository variable. > > > > - Jamis > > > > On 7/28/07, Thibaut Barrère <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi Adam > > > > > I think the multistage extension (http://weblog.jamisbuck.org/ > > > 2007/7/23/capistrano-multistage) should do the trick, together with > > > something like: > > > > > set(:repository) { "..." } > > > > > Not sure how to retrieve the current stage though in the block; > > > someone else will chime in (could be current_stage or stage ?) > > > > > best > > > > > Thibaut > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
