I am concerned about Cap's requirement to upload large amounts of data on a deploy (i.e an entire application rather than just the files that are new or have changed) and am also concerned about the amount of disk space used to have duplicate versions of an application on the server. With this in mind, i have 2 questions:
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? The 2 points here are of significant concern where i work as some apps (non-rails) are huge. 2. Does cap support checkout from an SVN branch? The SVN process here is to develop on branches and only merge back into head when the site has gone live and has passed test on the live server. Therefore, we'd need Cap to work of a branch id. TBH, having dug through the Cap code a bit now, i'm fairly confident that this one can easily be achieved, but your comments would are welcome. Thanks Andy --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
