Backgroundrb devel - Feb 2007 - -c switch in the startup command

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 created does, in fact, use the development
environment. But on the second request, the configuration details from
backgroundrb.yml are used, causing the worker to be erroneously led to the
production database.

With Capistrano, I really don''t want to have to edit my background.yml
on
the server, using vi, after each deployment. But so far, I have not been
able to come up with a better solution.

Has anyone else experienced this? I hope I am just missing something simple.

Jerry Richardson
jerry at jerryr.com

P.S. I have also tried a few other startup commands, with the same problem:

./script/backgroundrb run -- -c ../config/development_background.yml
./script/backgroundrb run RAILS_ENV=development -- -c
config/development_background.yml
./script/backgroundrb run RAILS_ENV=development -- -c
~/sites/iblinkink/config/development_background.yml
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070212/b75016e2/attachment.html

Jerry-

	Why don''t you put your production backgroundrb.yml on yoru server in  
the shared directory and have it get symlinked in after deploy? This  
way the production site will always have the right yml file and you  
can modify it locally to whatever you want and still be sure it gets  
the correct one on the server.

-Ezra


On Feb 12, 2007, at 6:59 AM, Jerry Richardson wrote:
> 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 created does, in fact,  
> use the development environment. But on the second request, the  
> configuration details from backgroundrb.yml are used, causing the  
> worker to be erroneously led to the production database.
>
> With Capistrano, I really don''t want to have to edit my  
> background.yml on the server, using vi, after each deployment. But  
> so far, I have not been able to come up with a better solution.
>
> Has anyone else experienced this? I hope I am just missing  
> something simple.
>
> Jerry Richardson
> jerry at jerryr.com
>
> P.S. I have also tried a few other startup commands, with the same  
> problem:
>
> ./script/backgroundrb run -- -c ../config/development_background.yml
> ./script/backgroundrb run RAILS_ENV=development -- -c config/ 
> development_background.yml
> ./script/backgroundrb run RAILS_ENV=development -- -c ~/sites/ 
> iblinkink/config/development_background.yml
>
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel
-- Ezra Zygmuntowicz 
-- Lead Rails Evangelist
-- ez at engineyard.com
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)