The simplest way of doing multi-stage is to create separate tasks for
each stage, and define variables therein:
task :first do
set :var, "value 1"
set..
end
task :second do
set :var, "value 2"
set ..
end
and then calling cap like "cap first deploy" or "cap second deploy".
No need for anything else....
izidor
On 24.1.2008, at 16:51, me wrote:
>
> In the spirit of DRY, would it still be possible to keep things in one
> deploy.rb and just do for the following since (so far, I think) that's
> how each of the three deploy files would differ from each other?
>
> set :deploy_to, "/srv/www/htdocs/#{application}/#{stages}"
> set :mongrel_conf, "#{deploy_to}/current/config/mongrel_cluster/
> #{stages}.yml"
>
>
> On Jan 24, 9:24 am, "Rafael G." <[EMAIL PROTECTED]> wrote:
>> me escribió:
>>
>>> Forgive me if this is a basic question. I'm attempting to support
>>> multiple-stage deployment, and I start out with:
>>
>>> set :stages, %w(production staging qa)
>>> require 'capistrano/ext/multistage'
>>
>>> in my deploy.rb file.
>>
>>> But I get an error where it appears to try to find a file based on
>>> one
>>> of the environment names:
>>
>>> $ cap qa deploy:setup
>>> * executing `qa'
>>> /usr/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/capistrano/
>>> configuration/loading.rb:184:in `find_file_in_load_path': no such
>>> file
>>> to load -- config/deploy/qa (LoadError)
>>
>>> Does this mean I need to have the following files, as well?
>>> config/deploy/qa.rb
>>> config/deploy/production.rb
>>> config/deploy/staging.rb
>>
>> Yes :)
>>
>> --
>> Rafael Garcia Ortega
>>
>> rgo.vcf
>> 1KDownload
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
