From d29f213632af5f2e9d148476419112b5de00422f Mon Sep 17 00:00:00 2001 From: Jakub Macina Date: Tue, 25 Jul 2017 08:55:22 +0200 Subject: [PATCH] Fix sidekiq command in docs to start all queues instead of only critical. --- docs/DEVELOPER-ADVANCED.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/DEVELOPER-ADVANCED.md b/docs/DEVELOPER-ADVANCED.md index fce07d005ca..4a258fe50cb 100644 --- a/docs/DEVELOPER-ADVANCED.md +++ b/docs/DEVELOPER-ADVANCED.md @@ -64,7 +64,7 @@ Create a test account, and enable it with: Discourse does a lot of stuff async, so it's better to run sidekiq even on development mode: ruby $(mailcatcher) # open http://localhost:1080 to see the emails, stop with pkill -f mailcatcher - bundle exec sidekiq -q critical,low,default -d -l log/sidekiq.log # open http://localhost:3000/sidekiq to see the queue, stop with pkill -f sidekiq + bundle exec sidekiq # open http://localhost:3000/sidekiq to see queues bundle exec rails server And happy hacking!