cookiecutter/cookiecutter-django
1
1
Fork 0
mirror of https://github.com/cookiecutter/cookiecutter-django.git synced 2025-08-09 22:44:54 +03:00
Code Issues Packages Projects Releases Wiki Activity

Added note regarding celery always eager

Browse Source 
Added a note around CELERY_TASK_ALWAYS_EAGER = True in docker config for local development. This causes tasks to be executed on the 'main' thread rather than by the workers. I understand why that might be desirable, but thought it worth calling out incase (like me) it makes people think something is broken.
This commit is contained in:
keithjeb 2019-02-21 22:19:22 +01:00 committed by GitHub
parent b09d840b54
commit c75cd7d41f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/developing-locally-docker.rst
View File

@ -171,6 +171,13 @@ When developing locally you can go with MailHog_ for email testing provided ``us
.. _Mailhog: https://github.com/mailhog/MailHog/ .. _Mailhog: https://github.com/mailhog/MailHog/
.. _`CeleryTasks`:
Celery tasks in local development
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
By default Celery tasks are set to 'eager' during local development. This results in tasks being evaluated as normal functions which will not reach the redis queue.
If you need tasks to be executed by a worker during development set CELERY_TASK_ALWAYS_EAGER = False in config/settings/local.py
.. _`CeleryFlower`: .. _`CeleryFlower`: