[Backgroundrb-devel] Setting Product Env

Chris Bruce cbruce at sleeter.com
Wed Sep 6 13:06:57 EDT 2006

I double and triple checked that.  Not sure how it is getting development.  Do you know of any way to force it?


From: backgroundrb-devel-bounces at rubyforge.org [mailto:backgroundrb-devel-bounces at rubyforge.org] On Behalf Of Jonathan Métillon
Sent: Wednesday, September 06, 2006 1:08 AM
To: Backgroundrb-devel at rubyforge.org
Subject: Re: [Backgroundrb-devel] Setting Product Env


Maybe you are using version control and when you deploy to your server, you don't update your newly checked out version so it uses production. That's what happened to me. For example in my deploy recipe I have: 

run "cat #{release_path}/config/backgroundrb.yml | sed 's#development#production#g' > #{release_path}/config/backgroundrb.yml"

Just before the BackgrounDRb restart:

sudo "#{release_path}/script/backgroundrb/restart" 
On 9/6/06, Chris Bruce <cbruce at sleeter.com> wrote:

When I am using my rails models in my worker class, it appears the
background worker class is always using development no matter what I do.
I set background.yml to production.  I even have ENV['RAILS_ENV'] ||=
'production uncommented in environment.rb.  I don't have the development
db even created on my production box, so not sure where it is getting
development from.  I am using fastcgi and have the environment correctly 
specified in my fastcgi config.

Any ideas?


Backgroundrb-devel mailing list
Backgroundrb-devel at rubyforge.org

More information about the Backgroundrb-devel mailing list