similar to: Mongrel Cluster 0.2.1 prerelease

Hey y''all: I''ve added some new stuff to mongrel_cluster. Give it try and let me know if it works for you. * Added ''--clean'' to cluster::start to force removal of the pidfile before trying to start the cluster member. This is useful for recovering from unexpected process death. * Added ''--only PORT'' to cluster::* to support running a

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first

Hi y''all, A prerelease of mongrel_cluster 0.1.3 is available for testing with the Mongrel 0.3.13 prerelease. This release contains bug fixes and adds a Ruby script for managing all applications on a server with a single command. To install: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added a

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

Hi y''all; A quick note to announce the release of mongrel_cluster, a gem_plugin for Mongrel. This plugin provides commands for managing multiple Mongrel processes behind a reverse-proxy server and load balancer. To install: gem install mongrel_cluster Configure (use -h to options): mongrel_rails cluster::configure Start: mongrel_rails cluster::start I''ve posted a quick

I wanted to be able to specify in my /etc/rc.conf file whether mongrel_cluster should be enabled and the mongrel_cluster_config file for the init script, so I wrote this simple rc.d style script. Just throw it in /usr/local/etc/rc.d/ and do a chmod +x /usr/local/etc/rc.d/mongrel_cluster.sh To enable the script, add mongrel_cluster_enable="YES" to /etc/rc.conf and optionally add

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

I have installed mongrel and mongrel_cluster fine and have them running great with my app. I tried using the init.d script provided with mongrel_cluster 2.1 to start it up on boot but it doesn''t. mongrel_cluster_ctl works fine for me by hand and so does /etc/init.d./mongrel_cluster start. I am on Debian so I installed the service links with sudo update-rc.d mongrel_cluster defaults. And

It appears the spawner in Rails 1.2 will do Mongrel clustering. I''m curious what this means for mongrel_cluster. They appear to overlap in features quite a bit. I don''t think the spawner uses a config, so that''s one difference. Will they be different enough? I only ask because mongrel_cluster could, theoretically, be made extinct if the spawner script has all the same

What''s the difference, architecturally between cluster::restart and cluster::stop/start (I haven''t looked at the code, which is kinda lazy of me to ask the question I know) If they aren''t very different actually, can I put a plug in for having cluster::restart do a "start" if something''s happened and mongrel is stopped for that configuration?

Hi, I''m trying to setup my mongrel clusters to start on boot. I have followed the instructions under the "On Boot Initialization Setup" section at http://mongrel.rubyforge.org/docs/mongrel_cluster.html. When I try to start it up, I get the following error: me at mybox.com: sudo /etc/init.d/mongrel_cluster start Starting all mongrel_clusters... !!! Path to log file not

If this was in the docs, I''ve missed it. How can I have multiple mongrel clusters on a server? All the documentation that I am seeing seems to assume that I am only running one cluster.

Hi y''all, An prerelase of mongrel_cluster 0.1.3 is available for testing with the Mongrel 0.3.13 prerelease. This release contains bug fixes and adds a Ruby script for managing all applications on a server with a single command. To install: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added

Hi all: Here''s a pre-release for mongrel_cluster to support current Mongrel 0.3.13.4 pre-release. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. -

Hi, I''m running CentOS 4.3 and the latest Mongrel (0.3.13.3) and mongrel_cluster (0.2.0). I have set up a cluster, following the instructions at http://mongrel.rubyforge.org/docs/mongrel_cluster.html . I created a symbolic link in the directory /etc/mongrel_cluster . When I run mongrel_rails cluster::start -c test.yml, the mongrel servers start up. But at boot, the command

I was able to find some information about this in the list archives, but it ended with a possible patch being submitted for Mongrel. I tried to follow a few of the instructions, but I''m still kind of stuck, since I''m not sure if what I''m seeing is the proper results. I have an application running on a cluster of mongrel servers, which is behind pen, which in turn is

Hi all, I am having trouble transitioning from fastcgi to Mongrel. I have it all working apart from one small part, I can''t get the service to start on boot. I have followed the instructions and if I call the script directly: i.e. "/etc/init.d/mongrel_cluster start" it works fine, but if I call it using "service mongrel_cluster start" it fails with the

Hi everyone, I am going crazy over here! :) I just want to be able to use --clean with my mongrel_rails cluster::start command. I''ve upgraded to mongrel_cluster 1.0.1.1 and mongrel_rails 1.0.1. my config file is in /etc/mongrel_rails/config.yml and contains: --- log_file: log/mongrel.log port: 8000 pid_file: /var/run/mongrel_cluster/mongrel.pid servers: 2 address: 127.0.0.1 environment:

Hi, I''m in the process of moving my blog over from lighttpd -> apache 2.2 + mongrel. Everything works fine as long as I don''t reboot :) On reboot apache comes up but mongrel_cluster doesn''t start up the pooches... I have added the mongrel_cluster call to my startup scripts like so: www:/etc/init.d# update-rc.d mongrel_cluster defaults Adding system startup for

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I