fork/django-q2
1
0
Fork 0
mirror of https://github.com/django-q2/django-q2.git synced 2026-09-15 13:37:56 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update documentation to say tasks are signed, not encrypted

Browse Source 
This resolves #300.
This commit is contained in:
Alejandro Sedeño
2020-04-17 14:25:35 -04:00
parent a53edd2a4e
commit 4429f99095
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/configure.rst
View File

@@ -33,7 +33,7 @@ On most broker types this will be used as the queue name.
Defaults to ``'default'``.
.. note::
Tasks are encrypted. When a worker encounters a task it can not decrypt, it will be discarded or failed.
Tasks are signed. When a worker encounters a task with an invalid signature, it will be discarded or failed.
workers
~~~~~~~
@@ -207,7 +207,7 @@ of the cache connection you want to use instead of a direct Redis connection::
.. tip::
Django Q uses your ``SECRET_KEY`` to encrypt task packages and prevent task crossover. So make sure you have it set up in your Django settings.
Django Q uses your ``SECRET_KEY`` to sign task packages and prevent task crossover. So make sure you have it set up in your Django settings.
.. _disque_configuration:

2
docs/index.rst
View File

@@ -14,7 +14,7 @@ Features
- Multiprocessing worker pools
- Asynchronous tasks
- Scheduled and repeated tasks
- Encrypted and compressed packages
- Signed and compressed packages
- Failure and success database or cache
- Result hooks, groups and chains
- Django Admin integration