Hi Rich, Try this out for size.. http://github.com/37signals/fast_remote_cache/tree/master - it uses hardlinks to effectively abolish the time required for the copy.. and might lead you down the road of finding how a more advanced remote_cache system works.. maybe you could try your rsync mod anyway...
We deploy to a share, at work our site is ~900 meg all-in (cold, deploy), we use rsync internally, and the copy_exclude variable to exclude large directories from the copy, which we then rsync using regular run() tasks. Hope this Helps, Lee Hambley 2008/10/24 theduz <[EMAIL PROTECTED]> > > Hi, > > We have three sites larger than 1Gb, and I want to extend capistrano > to make it faster when deploying them. deploy_via :remote_cache has > made things better, but it still takes several minutes to copy the > cached version to the releases folder. > > It seems that > svn up # in cached copy > rsync -a --delete cached-copy rsynced-copy > cp -al rsynced-copy releases folder > would make the deployment time initially longer, but shorter on > updates. > > Upside: would allow a 1Gb site to deploy an update in short order. > > Downside: both a cached copy and an rsynced copy > > So, I'm sitting here looking at /usr/local/lib/ruby/gems/1.8/gems/ > capistrano-2.5.0/lib/capistrano/recipes/strategy/remote_cache.rb. It > doesn't look like it would be too hard to jam the mods here, but I'm > guessing that's not the preferred method. > > What is the correct way to extend remote_cache.rb? Should I change it > in place? copy it to remote_cache_rsync.rb in the same folder and hack > it? Put it somewhere in my project? If so, where? > > Sorry for being a cappy noob and thank you for any advice you can > offer. > > Regards, > Rich > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
