similar to: Mongrel servers running in a subdirectory behind a proxy

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

Hi Y''all, Just a quick note announce an update to mongrel_cluster. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as

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

I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list. Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came mongrel_cluster 0.1.1 and I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did: on production machine: (debian linux, rails 1.1)

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.

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

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

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

Anybody know where to submit a bug for mongrel_cluster. Thanks _________________________________________________________________ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

Hi mongrel users! I just posted a bad-ass capistrano file that automates *everything* for setting up an apache2+mod_proxy_balancer and mongrel+mongrel_cluster -- including apache2 setups. It''s based off Coda Hale''s guide and all Bradley''s work at fluxura and RailsMachine (thanks Coda and Bradley!). It''s, well, bad-ass, if I must say so myself. My favorite

Hello Everyone, I just posted another pre-release of Mongrel that fixes a bug which caused Mongrel to claim it was getting parsing errors because the QUERY_STRINGs were too long. In actuality it was shift in the parser that made empty queries (/test?) become negative. This is fixed up now. Here''s the full list of changes: * It has a couple of fixes for win32, but I still have to

Hi all... After a few months of slumber, I''ve booted mongrel_cluster out the door. Nothing is really new from the prereleases except some bug fixes. I imagine there will still be some issues with ''ps'' on non-Linux platforms. I''ll gladly take patches. Most of the new stuff is described here: http://rubyforge.org/frs/shownotes.php?release_id=12907 Let me

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''. -

Me thinks the docs might need a bit of fleshing out ;P http://mongrel.rubyforge.org/docs/mongrel_cluster.html At the very least, what vars can go in its config. Joe -- Posted via http://www.ruby-forum.com/.

Hi *, What''s the best way to find out on which port mongrel is running from within Rails? I have a cluster of mongrels behind a balancer (Pen) behind a webserver (Apache). In Rails, request.port return 80 and request.env[''SERVER_PORT''] returns 3000 (the port of Pen) Any ideas? Cheers, Max

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

Hi list, I have tried to reach Bradley (author of mongrel_cluster) by mail, but have not gotten a response. So I''ll try trough this channel: I have ''developed''[1] a small extension to mongrel_cluster that allows selective restart of any one listener in a configuration that contains more than one listener by using a command like mongrel_rails

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

I''m currently working on 4 different RoR apps all using mongrel cluster and each with their own config file in /etc/mongrel_cluster. I would like the ability to stop|start|restart a single app. Anyone working on something like this? I''d be happy to code it up and contribute this if there''s a need. Basically I would like this: sudo /etc/init.d/mongrel_cluster restart

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: