[Capistrano] Re: One App/ Multiple :deploy_to's

[Jamis Buck]

Jon,




  LIST_OF_DEPLOY_DIRS = %w(/var/client1 /var/client2 /var/client3)

  task :deploy_to_all_clients do
    LIST_OF_DEPLOY_DIRS.each do |dir|
      set :deploy_to, dir
      deploy
    end
  end



- Jamis

On Nov 3, 2006, at 10:59 AM, Jon Garvin wrote:

I've never done this (and would be curious to hear from people who have), but my recommendation would be to see if something like the following would do the trick: (That may very well NOT work--capistrano caches the values of some variables, which may defeat the dynamic changing of the deploy_to variable.)

a table in the databases to turn certain features on and off per
instance. I've been using capistrano for a while on a personal project

new server, so now seems like the opportune time to migrate to cap as
well. Does anybody have any suggestions  on how to arbitrarily deploy
the app to one instance on the server?  Obviously, the default tasks

that sets up the variables and then runs the default tasks?

--~--~---------~--~----~------------~-------~--~----~

We've got one Rails application that we deploy to multiple instances on our server, each with their own mongrel_clusters, databases, etc. We use and want us to start using it on our big app at work. We're moving to a won't be enough, but I'm curious if anyone else has dealt with this, and if so, how they handled things like the :deploy_to variable, roles, etc. Maybe it's simply a matter of creating a task like 'deploy_to_client1', To unsubscribe from this group, send email to capistrano- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/capistrano

-~----------~----~----~----~------~----~------~--~---

smime.p7s
Description: S/MIME cryptographic signature