[Capistrano] Re: One Capfile to rule them all

[Jamis Buck]

I wonder if it wouldn't be better to make something like the following work as you would expect:

  namespace :some_app do
    load 'deploy'
  end



  namespace :some_app do
    load_into_namespace 'deploy'
  end



- Jamis

On Apr 10, 2008, at 10:14 AM, Adam Keys wrote:

I suppose there is a risk of that breaking existing scripts that depend on the current behavior, though. Could possibly introduce another keyword: I don't like 'load_into_namespace', but that's just a matter of finding a better name. If someone were to whip up a patch, I'd consider it.

On Apr 8, 2008, at 11:24 AM, Erik Hollensbe wrote:

Why not require them in the main capfile? (Use Dir[] to iterate over
them if you have to), they could inject their namespaces themselves.

should create a global cap -T listing as well.

Yeah, that's the first thing I tried. However, the standard Capistrano
recipe for Rails defines everything in the deploy namespace. I could
fork the deploy recipe from Capistrano, but that makes me sad.

Jamis, would you accept a patch that optionally defines the standard
deploy recipes in a namespace? For instance:

set :deploy_namespace, 'some_app'

load 'deploy'

$ cap some_app:update some_app:deploy:restart

--
~akk
http://therealadam.com


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

smime.p7s
Description: S/MIME cryptographic signature