On Thu, 2009-08-27 at 07:02 -0700, Richie Vos wrote: > Wow that got mangled. Here it is again as a properly formatted gist > http://gist.github.com/176294 >
fyi,
I am just adding:
set :user (so each deploy runs as the remote local user)
a chmod for the tree, user:www-data
and threads:
so it can run on the targets "at the same time"
as in
users.each do |user, pass|
Thread.new{ system("cap deploy:update -S user=#{user} -S
pass=#{pass}") or abort("Could not deploy to #{user}") }
end
Although I am not sure about the time gain since it's a bunch of request
to github from the same server and doesn't seem right,
So what I am doing now is first running a task that updates a repository
local to that of the remote server,
that way the threads will make sense
by doing set :repository '/user/git/repositories/app' so cap talks the
local repository (instead of sending 20 equal requests to github)
the 20 clones, will just take it from the updated local copy,
Thanks!
smime.p7s
Description: S/MIME cryptographic signature
