Problems with environment when running backburner as daemon about backburner HOT 7 CLOSED

Interesting thanks for reporting, I'll take a look soon. Seems as if the issue is that the binary probably needs an explicit way to specify a config file...

from backburner.

I tried a number of mods but couldn't come up with something that would be worth pulling. Sorry.

from backburner.

This has been fixed in 0.4.1 release. Now it should properly load the app environment for Rails and Padrino. Can you try the latest version and let me know if it works OK?

Should work like:

$ bundle exec backburner -q newsletter-sender,push-notifier -d -P /var/run/backburner.pid -l /var/log/backburner.log

or add a -r flag to require a particular file (should work auto for rails and padrino)

from backburner.

Will check it out later today when I'm off work. Thanks!!!

On Jun 28, 2013, at 3:40 PM, Nathan Esquenazi [email protected] wrote:

This has been fixed in 0.4.1 release. Now it should properly load the app environment for Rails and Padrino. Can you try the latest version and let me know if it works OK?

Should work like:

bundle exec backburner -q newsletter-sender,push-notifier -d -P /var/run/backburner.pid -l /var/log/backburner.log
or add a -r flag to require a particular file (should work auto for rails and padrino)

—
Reply to this email directly or view it on GitHub.

from backburner.

I had a similar issue when I ran this command ...
bundle exec backburner -q newsletter-sender,push-notifier -d -P /var/run/backburner.pid -l /var/log/backburner.log RAILS_ENV=production
it ran in development environment instead , how to specify the environment?

from backburner.

I know this is closed, but I'm having the same problem in 1.3

from backburner.

I found a way around this using dotenv-rails.

from backburner.