Capistrano deploy:stop

Rails
1

Hello, everybody.

After following like 20 sources on how to set up a mongrel cluster, I
got most of it working. There are some nagging questions though…

  1. In my mongrel_cluster.yml, I specified the pid name to be
    mongrel.pid. When I tried cap deploy:stop, it called reaper, which was
    looking for pids with the default pattern (with the word “dispatch” in
    it), couldn’t find my mongrel pids and failed measurably. I looked all
    over for an option to specify the pid pattern in deploy.rb, but alas,
    no cigar. So, I just changed the pid name to dispatch.pid. Needless to
    say, this drives me slightly mad.

Somewhere on the net I found how to override the stop task, but that
failed measurably too. The code was this (to be put in deploy.rb):

namespace :deploy do
task :restart do
mongrel_cluster cluster::stop
mongrel_cluster cluster::start
end
end

But it’s not very important. I would just like to know how to pass
options to reaper.

  1. the cap:web:disable command works fine – the page is uploaded but
    the site still works like nothing happened. What could be the reason?

Thanks for any ideas.

Sergei

2
  1. the cap:web:disable command works fine – the page is uploaded but
    the site still works like nothing happened. What could be the reason?

Please ignore the second issue… I just read in Rails Cookbook (I
still have the one that covers RoR 1.2!) that Apache is to detect the
presence of that file. I thought it was automatic somehow.

3
  1. In my mongrel_cluster.yml, I specified the pid name to be
    mongrel.pid. When I tried cap deploy:stop, it called reaper, which was
    looking for pids with the default pattern (with the word “dispatch” in
    it), couldn’t find my mongrel pids and failed measurably. I looked all
    over for an option to specify the pid pattern in deploy.rb, but alas,
    no cigar. So, I just changed the pid name to dispatch.pid. Needless to
    say, this drives me slightly mad.

Yep, ignore this one too. Turns out mongrel_cluster comes with mongrel
recipies that override the fastcgi ones. But hold on, what if I run
only one instance of mongrel without using a cluster? How would pass a
parameter to reaper then? This is pretty much just thinking out loud.