similar to: Setting environment

Hey guys, I just opened up my first installation of BackgrounDRb and so far I love it. I''ll have to share this plugin at my next Ruby Brigade meeting! I have one question though: Is there a way that I can run the BackgrounDRb server in a "test" mode that will reload my changes without having to restart every time? (Similar to how mongrel does this with my

Not sure this is known behaviour but it seems that if want to set the environment to, for example, test, and you want to use Active Record you have to both explicitly set the RAILS_ENV and the BackgrounDRb environment. So, if you have a config file backgroundrb_test.yml (as well as the default) and set the environment to test in that, this is what *seems* to happen: $

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

this patch adds a LogFile option to sshd_config. it just logs messages directly to a file instead of stderr or syslog. the largest change is an additional argument to log_init() in log.c for the log file name (and then changes to the rest of the tools to add a NULL arg). galt -------------- next part -------------- diff -urN openssh-3.5p1-orig/log.c openssh-3.5p1/log.c ---

Rsync team, and interested parties: i was attempting to get rsync to launch from tcpserver[0] (an inetd replacement from djb) and log to stderr for logging via multilog[1] (syslog replacement by djb) and i was unable to get it to log to stdout/ stderr at all. [0] http://cr.yp.to/ucspi-tcp/tcpserver.html [1] http://cr.yp.to/daemontools/multilog.html i have attached a patch that allows

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 have been strugging with getting backgroundrb to stay in the correct environment using multiple configuration files and the -c switch when starting backgroundrb. If I start brb like this: ./script/backgroundrb run RAILS_ENV=development -- -c ../config/development_background.yml where development_background.yml specifies "development" for rails_env and environment, the first worker

I''m running a fresh checkout of release 1.0.1 ... It''s now 11:32 am local time on January 31. I''ve configured a single worker for a test. If I use the following schedule in my background.yaml file: :schedules: :debugger_worker: :ping: :trigger_args: 0 35 11 * * * * Backgroundrb starts up without error. If I make the following

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

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

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

upgraded to 0.3.13.4 this morning in order to correct the above titled problem but mongrel is still not writing the pid file when starting with a config file verified i am running 03.13.4 with --version if i run this command: mongrel_rails start -p 3000 -e production -d --user mongrel --group webdev mongrel DOES create the pid file if i run the same, and include -G config/mongrel.conf, the

I''ve been trying to store the pid file option for Mongrel and it seems that I can only set it from the command line options, not from the configuration file. I''m using Mongrel gem version 0.3.13.3. Has anyone else experiend something like this? Here''s an example of a config file I generated using the -G option. The address and port options work fine but the pid file

I am running mongrel-0.3.13.1. Have used lighty and fcgi in the past, and I must say that apache-2.0.x proxying to mongrel is much nicer to deal with! I am having this problem, however. If I am in root''s homedirectory, and start mongrel with this command: --------- mongrel_rails start -a 127.0.0.1 -e production -c /home/www/rails/myapp -l log/mongrel.log --user mongrel --group mongrel

Hi Folks, I''d love for everyone to grab the 0.3.12 pre-release gems from http://mongrel.rubyforge.org/releases/ and tell me if their stuff breaks. You can get it with a simple: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ This release features the following goodies: * The -n and -t options to mongrel_rails start have changed in meaning to be the maximum number

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>

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

Here''s my config: :debug: false :daemon: true - mongrel :log_file: log/mongrel.log :pid_file: log/mongrel.pid :environment: development And I start Mongrel with: mongrel_rails -C config/mongrel.yml It starts up fine, and creates and logs to the log file, but I haven''t seen it create a pid file yet. Any idea why? BTW, why does Mongrel generate a config with vars like :var:

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: