From e7368bf10eb880e0d87b1c59c444eab1f6f2b771 Mon Sep 17 00:00:00 2001 From: Mike Perham Date: Sat, 17 May 2014 14:58:34 -0700 Subject: [PATCH] tweak changes --- Changes.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Changes.md b/Changes.md index 3458bb1f..f2202418 100644 --- a/Changes.md +++ b/Changes.md @@ -1,11 +1,11 @@ 3.1.0 ----------- -- New remote control feature: you can remotely trigger Sidekiq to quiet - or terminate remotely via API, without signals. This is most useful - on Heroku which does not support the USR1 'quiet' signal. Now you can +- New **remote control** feature: you can remotely trigger Sidekiq to quiet + or terminate via API, without signals. This is most useful on JRuby + or Heroku which does not support the USR1 'quiet' signal. Now you can run a rake task like this at the start of your deploy to quiet your - set of Sidekiq processes. + set of Sidekiq processes. [#1703] ```ruby namespace :sidekiq do task :quiet => :environment do @@ -13,7 +13,7 @@ namespace :sidekiq do end end ``` -- The Web UI can now quiet or stop all Sidekiq processes on the Busy tab. +- The Web UI can use the API to quiet or stop all processes on the Busy tab. 3.0.2