You might check out this project: http://trac.extendviget.com/lab/wiki/CapistranoRsyncWithRemoteCache
It looks like it might do what you need. - Jamis On 8/17/07, Andy <[EMAIL PROTECTED]> wrote: > > On Aug 17, 4:36 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > On 8/17/07, Andy <[EMAIL PROTECTED]> wrote: > > > > > 1. Does Cap by default always expect the deploy task to copy an entire > > > application to the server or can it instead comfortably connect to the > > > server, copy the application directory on the server to a 2nd > > > directory (or better still, create a hard linked version of all files > > > to the 2nd directory, thereby saving lots of disk space) and then > > > upload only the changes into this 2nd version, thereby avoiding a > > > potentially large upload? > > > > You might check out the :remote_cache strategy: > > > > set :deploy_via, :remote_cache > > Aha, so, this requires the server to access SVN directly. > Unfortunately, this is not an option for us, unless we use reverse > tunneling. Hmm. Is there any option if we are > using :deploy_via, :copy ? > > > The first time, it does a single checkout to the shared directory on > > each host, and then copies that checkout to the deployment location. > > Subsequent deploys just do an "svn up" (or whatever SCM you're using) > > in the cached dir, and then copy to the deployment dir. > > > > > 2. Does cap support checkout from an SVN branch? > > > > Yes. > > > > set :repository, "http://your.svn.repo/path/to/branch"; > > Oh yeah - doh! It's late on a Friday ;-) > > > - Jamis > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
