Hi Lee

Thank you for the feedback.

I'm going for the fork-approach (https://github.com/jbillen/capistrano). I 
am however not familiar with ruby so it might take a while before I come up 
with something useful.

Best Regards
Jochen Billen


Op woensdag 21 mei 2014 11:22:21 UTC+2 schreef Lee Hambley:
>
> Hi Jochen,
>
> Unfortunately not, however you might try forking the gem, adding a Gemfile 
> to your project (to grab your own version of Capistrano) and modifying the 
> git.rake/git.rb tasks to sun serially, or at least in rolling groups.
>
> You could achieve this by (roughly speaking) the following:
>
> $ gem install bundler
> $ cd ./my/project/path
> $ bundle init
>
> (this will create a Gemfile)
>
> Add the line:
>
> gem "capistrano", github: 'jochen/capistrano'
>
> and, then run:
>
> $ bundle
> $ bundle exec cap production deploy
>
> You are now working on your own Capistrano version.
>
> You can also clone your own Capistrano fork to your machine, and tweak it, 
> without having to commit, and push back to Github, with something like:
>
> gem "capistrano", path: '../capistrano'
>
> If you are successful, maybe we could change the main Gem to prefer groups 
> of 5/10 servers in a rolling configuration as the default, since this is 
> larger than *most* people's starting setups.
>
> Alternatively, you can look at 
> http://blog.jayfields.com/2008/02/rake-task-overwriting.html which you 
> might use (in your deploy.rb, or Capfile) to temporarily monkey patch your 
> own installation, however I'd prefer the "own gem" solution if I were you, 
> as it leads naturally to a bit more control over your environment, and the 
> chances that we change something, and nerf your monkey patch are mitigated.
>
> Lee Hambley
> --
> http://lee.hambley.name/
> +49 (0) 170 298 5667
>
>
> On 21 May 2014 10:58, Jochen Billen <[email protected] <javascript:>>wrote:
>
>> Hi
>>
>> I'm looking into Capistrano (v3) to deploy an PHP application to 100+ 
>> servers and I'm am concerned that running the 'git update' and 'composer 
>> install' task will put to much strain on the infrastructure (git server, 
>> SAN environment and network)
>>
>> Is there an easy way to limit the number of hosts to run tasks on in 
>> parallel? Or should I override particular tasks which could be to 
>> stressful using sshkit's 'on(in: :groups, limit: 2, wait: 5) { ... }'.
>>
>> Best Regards,
>> Jochen Billen
>>
>>
>>
>>
>> Versions:
>>
>>    - Ruby: 1.9.2
>>    - Capistrano: 3.2.1 
>>    - Rake: 10.3.1
>>
>> Platform:
>>
>>    - Working on: Debian
>>    - Deploying to: Debian 
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Capistrano" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web, visit 
>> https://groups.google.com/d/msgid/capistrano/1f0ff59b-6ea1-460a-bd8c-f1acb6b62557%40googlegroups.com<https://groups.google.com/d/msgid/capistrano/1f0ff59b-6ea1-460a-bd8c-f1acb6b62557%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/capistrano/c7f06817-48a3-40a3-9155-fe88bff94ce1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to