Hi Lee! Thanks for the response, very grateful.
I'll give `:no_release => true` a try, I do actually use this for our MongoDB, but as you said it probably does some other things as well. I like the idea of creating a .deb package and letting apt manage the packages, then using Capistrano to orchestrate the "apt-get update" and stop/start of services. We did look into remote caches of GitHub and nearly started work on it, but it didn't solve the issue that quite an intensive processes is happening every deployment for N servers - The deb package seems a cleaner, more manageable solution. I'll try the above and report back. Thanks again. Stuart On Aug 15, 3:14 pm, Lee Hambley <[email protected]> wrote: > Stuart, > > The only option is `:no_release => true` on the role/server declaration, but > beware this does more than disable the clone/checkout - it also disables > anything related to source code (think… database server) > > If there's a real problem checking our your source from Git, you should > perhaps look at the remote_cache strategy, which should reduce your checkout > time. Or perhaps the murder gem from Twitter, which uses torrent to > distribute the code (very fast.) between machines; and is already rather > well integrated with Capistrano. > > An alternative would be to come up with your own deploy strategy (not that > tough, take a look in the sources) - and use something like `:once`, (old > thread here might > help:http://www.mail-archive.com/[email protected]/msg06388.html) - > to > nominate just one server to do the checkout, then you can run whatever you > need on the other machines to distribute the code. > > I'd dearly love to see a decent "checkout and share between servers" > deployment strategy; but there's some good reasons why this doesn't exist in > the defaults, so YMMV. > > - Lee > > On 15 August 2011 15:20, StuartM <[email protected]> wrote: > > > > > > > > > Hi, > > > I have multiple roles in the deploy.rb file, however, I would like to > > remove some roles from doing a git clone/pull (not sure which one it > > does). > > > The reason for this is due to it taking it quite a long time for 15+ > > machines, so my intentions is to run the normal git clone/pull on a > > single machine, then create a Debian package and distribute that > > instead. > > > Any help would be greatly appreciated. > > > Thanks > > > Stuart > > > -- > > * You received this message because you are subscribed to the Google Groups > > "Capistrano" group. > > * To post to this group, send email to [email protected] > > * To unsubscribe from this group, send email to > > [email protected] For more options, visit this group > > athttp://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
