Sidekiq should use the RAILS_ENV variable if available about opsworks-sidekiq

[atomgiant]

@chrisnicola - This for your feedback. Are you suggesting I just remove the -e production which will cause this set_environment to run within Sidekiq?

[chrisnicola]

Actually a lot of what is in the default "run_command" is just the defaults. I would suggest the following command: bundle exec sidekiq -d -l log/sidekiq.log

The -d tells it to run as a daemon and the -l specifies the log file. Alternatively you could specify no options and let sidekiq.yml specify everything, but you probably want to specify a log file as that isn't on by default.

As another alternative you could use a sidekiq.yml.erb template instead.

[chrisnicola]

Ok there is a bit more to this than I originally assumed. The RAILS_ENV variable is not included with the other variables in @env. I'm going to submit a pull request after further testing.

[atomgiant]

That's great @chrisnicola. Thanks for looking into this.