Lee, Thanks for the reply.
What I've done is to duplicate the copy strategy file and added the bundler command inside this new file so the gems are installed in the checked out source directory. I've renamed the file and the strategy to BundleStrategy and copied this inside the installed capistrano gem. Then, I just need to run the task on the build host, the source code is updated (I've used source cache to speed up the checkout and the bundler process), then compressed and sent to the deployment hosts. There are some drawbacks with this approach: * I need to log to the build host to run the capistrano task * the upload process is slow because it needs to upload all the gems. I may use rsync instead of compression and scp to do this in the future. * I have to put my custom strategy source inside the capistrano sources of my build host. Yvan On Jan 13, 10:34 am, Lee Hambley <[email protected]> wrote: > ybart, > > That's not supported with the "Standard" recipes, you should start by > examining `deploy.rb` from the Gem, then you can see how the process flows. > (Expect this to be a *lot* of work.) There's an alternative that you could > stub the restart tasks, and make something that *after* a normal deploy to > the ``build host'' (which seems like massive, massive overkill for a web > application, however complex) and SCPs the result to your web hosts. > > - Lee -- * 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
