We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is it possible to set ENV variables at startup from the procfile, just like you could do with a rake task:
worker: bundle exec rake resque:work NEWRELIC_ENABLE=false
But with sidekiq?
The reason: I need to completely disable new_relic for background tasks ONLY
The text was updated successfully, but these errors were encountered:
Doesn't foreman just pass the command to the shell so you can do:
worker: ANY_ENV_VARIABLE=foo any_command
Sorry, something went wrong.
Apparently not. Any way just prepend the command with env and it will work:
worker: env ANY_ENV=foo any_command
You saved my day!
No branches or pull requests
Is it possible to set ENV variables at startup from the procfile, just like you could do with a rake task:
But with sidekiq?
The reason: I need to completely disable new_relic for background tasks ONLY
The text was updated successfully, but these errors were encountered: