-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resque-pool defaulting to test environment #158
Comments
I ended up changing my Procfile to
and the environment was picked up correctly. Any idea why there is a difference in behaviour? |
I'm just seeing this too. It turns out that For some reason, this does not set Unfortunately, Rails 4.2.7.1 sets [...] OK so it looks like |
Thank you for the PR @brucek hopefully this will be merged some days :). I had the same problem today, however, couldn't switch to So I ended up doing:
to force dev users to set the |
I set up resque-pool locally today and I have noticed some strange behaviour. I had previously got plain old resque up and running no problem. My jobs were failing because records could not be found. When I dug into this I found that this is because the workers are being set up with the test configuration. I'm using foreman/heroku local and my .env file sets the environment
RACK_ENV=development
, I also tried added aRACK_ENV=development
Sample set up output
My tasks/resque.rake file
I'm not sure why the environment variables aren't being picked. I'm also a little surprised that resque-pool is defaulting to test. I'm using 0.6.0 in a rails 5.0 api only app. I'm sure I must be doing something silly but I can't see what it it
Just in case it helps, messing around with byebug
The text was updated successfully, but these errors were encountered: