STORY
As an administrator I would like my sidekiq queues to be started automatically, so that I don't have to manually restart them after deployments or server restarts.
DETAILS
Sidekiq is automatically restarted on code deployment and must be manually triggered after server restarts using cap <host-target> sidekiq:start. Currently, we don't have a config file, so only the default queue is processed. We need to add a config file that also starts the id_service queue.
To manually launch the queue:
RAILS_ENV=production bundle exec sidekiq -q id_service
2017-11-20T21:25:52.866Z 26619 TID-gmygbnq70 INFO: Running in ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux]
2017-11-20T21:25:52.866Z 26619 TID-gmygbnq70 INFO: See LICENSE and the LGPL-3.0 for licensing details.
2017-11-20T21:25:52.866Z 26619 TID-gmygbnq70 INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org
2017-11-20T21:25:52.866Z 26619 TID-gmygbnq70 INFO: Booting Sidekiq 5.0.5 with redis options {:id=>"Sidekiq-server-PID-26619", :url=>nil}
2017-11-20T21:25:52.867Z 26619 TID-gmygbnq70 INFO: Starting processing, hit Ctrl-C to stop
2017-11-20T21:25:52.875Z 26619 TID-gmygtnal4 DataciteRegisterJob JID-b09bdebd706b3ff26a7e410d INFO: start
2017-11-20T21:25:54.516Z 26619 TID-gmygtnal4 DataciteRegisterJob JID-b09bdebd706b3ff26a7e410d INFO: done: 1.642 sec
ACCEPTANCE
[x] DOI registrations are automatically processed in the background by sidekiq
STORY As an administrator I would like my sidekiq queues to be started automatically, so that I don't have to manually restart them after deployments or server restarts.
DETAILS Sidekiq is automatically restarted on code deployment and must be manually triggered after server restarts using
cap <host-target> sidekiq:start. Currently, we don't have a config file, so only thedefaultqueue is processed. We need to add a config file that also starts theid_servicequeue.To manually launch the queue:
ACCEPTANCE