Sidekiq should restart after deploy:failed

[tomdev]

Sidekiq should get restarted after a failed deploy.

Currently, Sidekiq will still be monitored but running in quiet mode a.k.a. not accepting new jobs. This state should get corrected after a failed deploy.

A failed Capistrano deploy will not trigger deploy:updated to stop Sidekiq or deploy:published to start it again.

[taariq]

@tomdev It's been a few months since you posted. How did you and your team resolve this issue? Any ideas?

[tomdev]

To make sure Sidekiq gets restarted we adding the following to our config/deploy.rb:

after 'deploy:failed', 'sidekiq:restart'

On failed deploys this will stop Sidekiq that's running in "quiet" mode and start it normally again.

[taariq]

Thanks @tomdev. We just tested it and it looks like it rocks as a way to solve this problem. @seuros. Shouldn't this be set on by default on the capistrano script?