sidekiq worker is not getting triggered when rediscloud url is used in heroku

Question

I am new to Ruby on Rails, I am facing an issue where sidekiq with redis (redis://localhost:6379) on local is working fine(getting triggered) but is not working with rediscloud in heroku. What can be the issue?

My procfile contains:

web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq -q critical -q applications -q default

silly question, but how do you know it isn't getting triggered? What logfiles are you looking at? And do you know the port numbers in question? — ezuk

Mike Perham Mike Perham · Accepted Answer · 2016-03-09T16:43:59

The wiki notes how to set up your Redis provider on Heroku:

heroku config:set REDIS_PROVIDER=REDISCLOUD_URL

https://github.com/mperham/sidekiq/wiki/Using-Redis#using-an-env-variable

sidekiq worker is not getting triggered when rediscloud url is used in heroku

1 Answers