OK, thanks. I like deploying from scm , so tar/sync is out of the question right now.
And as far as developers reaching svn: they can, just not at the same time as the single arm VPN to the client needed when doing deployment with cap. So if we deploy from our office, where the svn server is, we're fine. But if we're remote, we need the vpn to the client (for the app servers) and the vpn to the office (for svn). Unfortunately not available at the same time since one is Cisco VPN and the other we use IPSecuritas. Or, would the need for two vpn arms go away if we used git? Since each repo is a complete repo of the main, it would get the current version locally, right? Thanks, Michael Check On Sep 14, 2:55 am, Lee Hambley <[email protected]> wrote: > Mike, sorry not possible (however this archaic decision is on my hit-list > for things to take care of when the time comes up) > > Your only real alternative is to do a tar/rsync deployment, cutting out SVN, > or have your IT staff take care of it (Your developers can't reach the SVN > server?!) > > - 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
