I'm probably just overtired, but I'm not understanding why the copy strategy fails when local_repository is set? Is it because the strategy isn't doing source.local.xyz? If so, maybe we should consider patching the strategies to use source.local, since source.local just falls back to the normal repository if a local repo hasn't been specified.

- Jamis

On May 21, 2008, at 6:02 PM, Tom Copeland wrote:


Hi all -

I posted on my new bee struggles with local_repository and deploy_via
copy today:

http://tomcopeland.blogs.com/juniordeveloper/2008/05/capistrano-loca.html

Here's an ugly patch, but you get the idea:

==================================
$ diff -Naur base.rb base.new.rb
--- base.rb     2008-05-21 19:50:07.000000000 -0400
+++ base.new.rb 2008-05-21 19:49:59.000000000 -0400
@@ -43,6 +43,7 @@
        # Creates a new SCM instance with the given configuration
options.
        def initialize(configuration={})
          @configuration = configuration
+          logger.info "WARNING: You probably don't want to use
'set :deploy_via, :copy' and a :local_repository together; remove
'set :deploy_via, :copy and things will probably work as expected" if
@configuration.variables[:deploy_via] == :copy &&
@configuration.variables[:local_repository]
        end

        # Returns a proxy that wraps the SCM instance and forces it to
operate
==================================

Maybe there's a scenario when you'd want to have both those variables
set?  I noodled for a bit but couldn't think of one...

Yours,

Tom



--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to