This is a prime candidate for some custom tasks. The default deploy tasks will not handle this scenario, but if you can script the sequence of shell commands that need to happen to do what you want to do, you can write some cap tasks to do it.
- Jamis On Jun 23, 2008, at 1:46 PM, pbooth wrote: > > I appreciate that the subject header of this question sounds > nonsensical, but it is a genuine question and I would be grateful for > any suggestions... > > Our situation: > > > we have two "instances" of the same Rails application and are > deploying both to our production, stage, loadtest, uat and other > stages. > There are some small code differences between the two instances, that > is managed in subversion as two branches. The medium term plan is to > abstract this differing functionality out and have a single Rails > application. > > Right nowwe use the Capistrano :application variable to denote the > application instance. > > Is there a mechanism we can use to define :application outside of the > deploy.rb script? > > Peter Booth > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
