Skip to content

Commit f0bbf1c

Browse files
committed
Update README for renamed '--extra-settings'
Also clarify how these settings are applied.
1 parent 2f5b041 commit f0bbf1c

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

README.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ LIGHTWEIGHT_QUEUE_REDIS_PORT = 12345
6969
and then running:
7070

7171
```
72-
$ python manage.py queue_runner --config=special.py
72+
$ python manage.py queue_runner --extra-settings=special.py
7373
```
7474

7575
will result in the runner to use the settings from the specified configuration
@@ -149,10 +149,13 @@ part of a pool:
149149
$ python manage.py queue_runner --machine 2 --of 4
150150
```
151151

152-
Alternatively a runner can be told explicitly which configuration to use:
152+
Alternatively a runner can have be told explicitly how to be have by having
153+
extra settings loaded (any `LIGHTWEIGHT_QUEUE_*` constants found in the file
154+
will replace equivalent django settings) and being configured to run exactly as
155+
the settings describe:
153156

154157
```
155-
$ python manage.py queue_runner --exact-configuration --config=special.py
158+
$ python manage.py queue_runner --exact-configuration --extra-settings=special.py
156159
```
157160

158161
When using `--exact-configuration` the number of workers is configured exactly,
@@ -188,7 +191,7 @@ $ python manage.py queue_runner --machine 3 --of 3
188191
will result in one worker for `queue1` on the current machine, while:
189192

190193
```
191-
$ python manage.py queue_runner --exact-configuration --config=special.py
194+
$ python manage.py queue_runner --exact-configuration --extra-settings=special.py
192195
```
193196

194197
will result in two workers on the current machine.

0 commit comments

Comments
 (0)