On Jan 24, 2:47 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
> the default favored by Capistrano currently. :) Having the deploy be
> a real checkout has advantages, such as if the only change is a
> wording change in a template, you just have to do svn up on each box
> and Rails automatically picks it up, without any restarts being
> necessary. I know not everyone likes that approach, however, and that
You can do that with SVK as well because it is just a flash version of
SVN.
> If you are volunteering to implement an SVK module for Capistrano,
> I'd be happy to work with you to make that happen. ;) If you have any
> interest in that, please let me know.
Here it is:
require 'capistrano/scm/subversion'
module Capistrano
module SCM
class SVK < Subversion
def diff(actor, from=current_revision(actor), to="HEAD")
`#{SCM_COMMAND} diff -r #{from}:#{to} #{configuration.repository}`
end
private
SCM_COMMAND='svk'
def svn
configuration[:svn] || SCM_COMMAND
end
def svn_log(path)
`#{SCM_COMMAND} log -q --limit 1 #{path}`
end
end
end
end
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
