On Jan 23, 2007, at 1:20 PM, Jacob Atzen wrote: > On Tue, Jan 23, 2007 at 11:35:31AM -0700, Jamis Buck wrote: >> >> I've got a plugin working which decouples deployment from the SCM in >> use. It currently supports only Subversion (I'll be emailing the >> maintainers of the other Capistrano SCM modules to work with them on >> that), but it supports FIVE different deployment strategies (well, >> only three really, but two of them have two variations apiece): >> >> * checkout (the default) >> * export (same as checkout, but uses SCM export instead) >> * copy_checkout (does a local checkout, and then copies the result to >> the remote servers) >> * copy_export (as copy_checkout, but using SCM export) >> * cached_repository (keeps a cached checkout in the shared dir for >> each remote server, and does an update+copy on each server to deploy) > > Sounds sweet! > > Might I suggest a combination of cached_repository and copy_*? Perhaps > implemented over rsync? > > Something along the lines of: > - Checkout / export into local copy - to avoid having remote repos > access > - Rsync local copy to cached repository (or cached export) - to > minimize > bandwidth usage and deployment time > - Copy cached repository to new release > > Does this sound like a good idea to anyone but me?
If you're copying from the localhost to each server anyway, why not just copy directly to the new release directory? Perhaps I'm misunderstanding the scenario. At any rate, I think you'll find new deployment strategies ridiculously easy to write with the new system. The cached_repository strategy, for instance, is only 48 lines of code, including blank lines and comments. - Jamis --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
