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) It's quite slick, and very easy to write your own deployment strategies if none of the above work for you. I'm hoping the SCM abstraction is easy for other SCM maintainers to implement, too. We shall see! I'll be polishing it off this week, and as soon as I hear from the other maintainers I'll release it for people to play with. (With all kinds of caveats, of course--it is highly experimental at this point.) - Jamis --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
