What happens with sidekiq current processes and capistrano -

When the deployment is done, then the running sidekick process affects, stops or hits while deploying with capitrons are given?

In your deploy.rb, the is required to enter 'sidekiq / capistrano Posted in

If you are doing something that is not pure vanilla, for example. Using the monit, you do not want to add the 'sidkyk / castestano statement to and you can write your own work and hook.

For example. After "Deployment: Stop", "Deployment: Start", "Sidekit: Start" after "Capsularano :: Configuration Interiors (: Should_Acciceist)".

 "Sidekick do Dell" silent sidekick (stop accepting new work) "Function: cool, roles =" before deployment: "Deployment: Update code", "Sidebox: quiet" "Deployment: Restart", "Start the Sidekick:" Gt; : App,: on_no_matching_servers = & gt; : Continue running "/ usr / sbin / service sidekiq cool" end details "stop stop" function: pause, roles = & gt; : App,: on_no_matching_servers = & gt; : Continue "sudo / usr / bin / monit stop sidekiq" end desc "start sideq" work: start, roles = & gt; : App,: on_no_matching_servers = & gt; : Continue running "sudo / usr / bin / monit start sidek" end details "restart" function: restart, roles = & gt; : App,: on_no_matching_servers = & gt; : Continue "sudo / usr / bin / monit restart sidekiq" and end