[Backgroundrb-devel] strange deployment issue

Adam Williams adam at thewilliams.ws
Wed Apr 30 13:35:42 EDT 2008

So, there is some serious confusion about this in the code. I now know  
of two other folks (one you, Jason) who struggled with this besides me.

I solved it by having a shared/config/backgroundrb.yml on the server,  
which we link into config of the app on deploy (capistrano). It looks  
like this:

   :port: 11006
   :environment: staging
   :lazy_load: true
   :debug_log: true

       :trigger_args: 0 */3 * * * * *

As you can see, we have the environment in the config. The code in  
meta_worker obviously disrespects -e. Now, you ALSO need to pass -e  
staging, so that when Rails boots, it has the correct environment.  
Here is our init.d line:

   /var/www/apps/railsapplication/current/script/backgroundrb "$1" -e  
staging >> /var/log/backgroundrb

I may patch this at some point, but it's already eaten a bit too much  
time (not you, but solving it originally).


On Apr 30, 2008, at 12:49 PM, Jason Lee wrote:

> So I tried this and my debug still says the env is development..
> Guess I'll have to start hacking to see why this is..
> - jason
> On Wed, Apr 30, 2008 at 8:15 AM, Stevie Clifton <stevie at slowbicycle.com 
> > wrote:
>> Hey Jason,
>> To get the environment passed in correctly, I use:
>> RAILS_ENV=staging ./script/backgroundrb start
>> And just to make sure, you're aren't actually calling your staging
>> environment "stage" are you?  Or if you are, you have an environment
>> intentionally named that, right?  Just had to ask :).
>> stevie
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel

More information about the Backgroundrb-devel mailing list