similar to: Using :config_script to set environment variables

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

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)

This GemPlugin will gzip your HTTP responses from mongrel if the client says that it supports it (eg, most modern browsers). I''ve tested it in IE6, Firefox 1.5 and Firefox 2.0RC3 Install: gem install gzip_filter --source http://edenli.com Configure (assuming rails): cd RAILS_ROOT echo ''uri "/", :handler => plugin("/handlers/gzipfilter")''

Hello all, I''m new to Mongrel and am very impressed with what I see so far. This thing beats FastCGI hands down, and is even simpler to use than SCGI. Great job Zed! Thanks for all the hard work. I am a bit surprised at the memory usage patterns though. I''m not sure if I''m doing something wrong (most likely I am), or if this is a problem with the app I''m

Hi There, I''ve got a mongrel cluster running on redhat 9 proxied behind an Apache 2.2 installation. I have run into a real stumbling block in that, while the rails app runs in production mode (you get a production.log file, for example, and I see this in the mongrel log: ** Starting Rails with production environment ... ), it always loads the development database configuration

I just got the mongrel_upload_progress set up with drb and the setup was quick and easy, thanks to the good documentation on http://mongrel.rubyforge.org/docs/upload_progress.html I''d like to get this set up with capistrano, but there are 3 things I can''t figure out: - First, I can''t get lib/upload.rb to run in the background - I''m not familiar with

Hello! hey, I''ve been writing this man page for mongrel_rails for some time and now I wanted the list to take a look at it and see if it''s good. After it''s ok, and if zed want to integrate it in mongrel (or any other distribution wants it), the debian note can be removed :D Manual Page: .TH MONGREL_RAILS 1 "2006-11-17" "Mongrel Rails" .SH NAME

Can anyone tell me how to get x_send_file working with mongrel 1.1.1 and apache 2.2? I''ve installed the mod_xsendfile apache module from http://tn123.ath.cx/mod_xsendfile/ and it works fine serving content from a PHP script, but I can''t get it to work with my single Mongrel instance and ProxyPass. I''m using the following Apache configuration: <VirtualHost *:80>

I''m newbie to mongrel, I''m not able to config mongrel_cluster in order to host multiple web sites added/remove as apache VirtualHost. I followed codahale http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ mixed with Wiki Radiant (I use Radiant as a rails apps to be deployed, 1 domain 1 radiant sites with its own document tree

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

Hi guys, I''m looking for a way to pass environment variables to my Rails app via Mongrel. I want to conditionally execute code in environment.rb based on these environment variables. Background: 1. I have some special stuff I want to do when my Rails app first starts 2. So, stuff it in environment.rb in after_initialize, right? 3. Not this time. I have several other background

Hi all, I''m trying to start Mongrel using a configuration file, but Mongrel complains: $ sudo mongrel_rails start --config /usr/local/www/xltester.com/config/mongrel.yml !!! Path to log file not valid: log/mongrel.log mongrel::start reported an error. Use mongrel_rails mongrel::start -h to get help. I''m using sudo above to replicate monit, not because I run Mongrel as root.

hey all, I''m trying to do a mongrel_cluster+apache2 config. this is my testapp.conf: <VirtualHost *:80> Include /etc/apache2/conf.d/testapp.common # ErrorLog logs/testapp_errors_log # CustomLog logs/testapp_log combined </VirtualHost> this is my testapp.common: ServerName myapp.com DocumentRoot /home/patcito/testapp/public/ <Directory

Dear all, In the past, I''ve been successfully using mongrel_cluster following codahale setup [1]. Now I updated mongrel_cluster through gem to 1.0.2, and my previosly worked config is not working anymore. I report below a snip of one of logfile, it seems to me it is a missing gem problems, but this sounds strange to me, because my config was ok before the upgrade. Does

The Rails app I''m working on requires an environment variable to be set. I thought I could do this in my cap deploy script. Unfortunately, it seems that the Mongrel processes that are started up by Mongrel Cluster have their own environments and any environment variables set in the deploy script aren''t passed on. I was able to verify this by having my deploy script run a rake

Alright, I have googles and read through the docs on monit I get this error when adding -v starting monit monit: Cannot connect to the monit daemon. Did you start it with http support? monit: Cannot connect to the monit daemon. Did you start it with http support? Am I missing something here? set daemon 120 set logfile syslog facility log_daemon set mailserver localhost set httpd port 28212

Hi all, I am out of my head here... I have a 3 node cluster with 10 mongrels running on each. When I deploy, I break all the mongrels every time. I have tried just about everything. I can restart my mongrels without a hitch manually, it''s only when I use cap deploy. Maybe I am missing something here... so if I can get some help it would be appreciated. The errors are the typical mongrel

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

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

Bradley couldn''t make it so I''m filling in for him. This is a short announcement to tell everyone using the mongrel_cluster gem to manage their Mongrels that there''s a new official version out. Version 0.2.0 is sporting the following features: * Added support for specifying user to run * Added script, mongrel_cluster_ctl for starting/stopping all clusters on a server.