I'm not concerned with deploying to all of them at once. On the
contrary, just one at a time is preferred. The following additions to
my deploy.rb seem to do the trick so far. We can define the whether or
not to deploy to the QA or LIVE directories, and for which instance of
the app. Still gott
On Nov 3, 2006, at 12:12 PM, Jamis Buck wrote:
>
> On Nov 3, 2006, at 1:10 PM, Jamis Buck wrote:
>
>> Ezra,
>>
>> Capistrano is currently extremely opinionated on this point. There
>> is setting anywhere you can tweak to make Capistrano use different
>> SSH
>
> Gah. That should be "There is
On Nov 3, 2006, at 1:10 PM, Jamis Buck wrote:
Ezra,
Capistrano is currently extremely opinionated on this point. There
is setting anywhere you can tweak to make Capistrano use different SSH
Gah. That should be "There is NO setting anywhere..."
- Jamis
smime.p7s
Description: S/MIME cryp
Ezra,
Capistrano is currently extremely opinionated on this point. There is
setting anywhere you can tweak to make Capistrano use different SSH
settings for different machines. It would require some rethinking in
how portions of Capistrano are designed, in fact.
If you're interested in ha
Hello~
I am using capistrano to build Xen VM's with the whole rails stack
on them. I need to build a ton of these and would like to do it in
parallel cap style. The catch is that ssh access to all these VM's is
through the same IP address but each one is on a different ssh port
nu
Awesome. That was the trick. Thanks, Jamis.On 11/3/06, Jamis Buck <[EMAIL PROTECTED]> wrote:
To use capistrano-ext, you need to require it in your deploy.rb. Iusually just throw the following line in the bottom of my deploy.rb: require 'capistrano/ext/monitor'Eventually, I may add additional mo
Jon,
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:
LIST_OF_DEPLOY_DIRS = %w(/var/client1 /var/client2 /var/client3)
task :deploy_to_all_clients do
LIST_OF_DEPLOY_DI
To use capistrano-ext, you need to require it in your deploy.rb. I
usually just throw the following line in the bottom of my deploy.rb:
require 'capistrano/ext/monitor'
Eventually, I may add additional modules to capistrano-ext, and those
would need to be required individually, but for now
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
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
and want us to s
I must be missing something. I'm trying to use some tasks from capistrano-ext. I have installed the gem. Now what? The tasks don't magically appear to be available. Where are they defined? Do I need to "require" them somewhere? What is the required file? Where do I place the "require"?
Help
10 matches
Mail list logo
