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 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"; - Jamis --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
