From e31a436383fd5d3aac2d9c2c95db1ef377fa154f Mon Sep 17 00:00:00 2001
From: Art <artiom.lukyanchyk@hs-hannover.de>
Date: Wed, 5 Dec 2018 22:48:27 +0100
Subject: [PATCH] Update README.md
---
README.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 5b6da07..d18c303 100644
--- a/README.md
+++ b/README.md
@@ -88,13 +88,15 @@ You are done after creating queues for each of your tasks. Don't need anything e
* Decide which tasks should the client use. Let's say these are `task1` and `task2` (you should have the corresponding queues already).
* For each of the tasks, create a new binding for the exchange `client.out`, with `routing key == queue name == task name`
* e.g. `exchange = client.out`, `routing key = task1`, `queue = task1`
- * User permissions:
+ * RabbitMQ user permissions:
* Configure: empty string (no config permissions)
* Write: `^client.out$` (replace with the name of your exchange)
* Read: empty string (no read permissions, RPC results/replies will still work)
+ * Pikatasks settings:
+ * ```pikatasks.settings.CLIENT_EXCHANGE_NAME = "client.out"``` (replace `client.out` with you know what`)
##### Worker:
- * User permissions:
+ * RabbitMQ user permissions:
* Configure: empty string (no config permissions)
* Write: `.*` (everything) or `^amq.default$` (`amq.default` is required to send "direct reply-to")
* Read: `^(task1|task2)$`, replace `taskN` with whatever your task names are
--
GitLab