The plugin is still in development. My original design did not
sufficiently account for the needs of distributed SCM's, and there
are a couple people working with me on fixing that gap.
I hope to have it all ready to unveil by RailsConf in May, at the
very latest, though I'm hoping against
Hi Jacob,
I have been using this method for little while. I just hacked at
cache_svn.rb and created cache_rsync.rb.
It works like this..
1. local svn cache is updated using svn up
2. rsync sends changes (minus .svn folders, and deploy.rb) to servers
cache folder
3. simple copy from the
On Jan 24, 2007, at 7:14 AM, NeilW wrote:
Jamis,
Any particular reason why you don't just move from Subversion to SVK
and use that
as the default?
Because we use the checkout strategy, ourselves, which is why it is
the default favored by Capistrano currently. :) Having the deploy be
a
On Jan 23, 2007, at 2:42 PM, S. Robert James wrote:
I would suggest to versions of cached_repository:
1. Incremental.
2. Clean (rm -rf and sync everything from the beginning).
Could you elaborate on the difference between these?
(On Perforce, this would be p4 sync and rm -rf p4 sync
