Isn't an svk mirror a cached repository. I'm sort of favouring a local proxy as the solution at the moment - probably sat on the primary database server since that is easy to reference from the standard Capistrano role models.
That way the update code doesn't need to do anything other than a checkout and/or an update from the local proxy and the problems of bringing in the code are delegated to the mirror tasks - allowing push or pull implementations as appropriate. Anybody got network implementations where the web servers and app servers couldn't see a proxy running on the primary database server? NeilW --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
