On Jan 24, 2007, at 7:14 AM, NeilW wrote: > > Jamis, > > Any particular reason why you don't just move from Subversion to SVK > and use that > as the default?
Because we use the checkout strategy, ourselves, which is why it is the default favored by Capistrano currently. :) Having the deploy be a real checkout has advantages, such as if the only change is a wording change in a template, you just have to do svn up on each box and Rails automatically picks it up, without any restarts being necessary. I know not everyone likes that approach, however, and that is one of the primary motivations for introducing the new deployment strategies. If you are volunteering to implement an SVK module for Capistrano, I'd be happy to work with you to make that happen. ;) If you have any interest in that, please let me know. - Jamis > > It does all this out of the box > > - checkouts are effectively exports > - svk mirror/svk sync is a local cached repository > > SVK is just a bunch of perl modules, so it should be available to > most. > > NeilW > > On Jan 23, 6:35 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > >> * 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) > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
