From d7651adc5b9dd53d80adbe9d74fc0803b3deba67 Mon Sep 17 00:00:00 2001 From: Matt Westcott Date: Thu, 11 Sep 2014 14:30:38 +0100 Subject: [PATCH] side-step the 'a large number of emails is' vs 'a large number of emails are' grammatical debate --- docs/howto/performance.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/howto/performance.rst b/docs/howto/performance.rst index f87e405c0..57bac2131 100644 --- a/docs/howto/performance.rst +++ b/docs/howto/performance.rst @@ -31,7 +31,7 @@ Without a persistent cache, Wagtail will recreate all compressable assets at eac Sending emails in the background using Celery --------------------------------------------- -Various actions in the Wagtail admin backend can trigger notification emails - for example, submitting a page for moderation. In Wagtail's default configuration, these are sent as part of the page request/response cycle, which means that web server threads can get tied up for long periods if a large number of emails is being sent. To avoid this, Wagtail can be configured to do this as a background task, using `Celery `_ as a task queue. To install Celery, add ``django-celery`` to your requirements.txt. A sample configuration, using Redis as the queue backend, would look like:: +Various actions in the Wagtail admin backend can trigger notification emails - for example, submitting a page for moderation. In Wagtail's default configuration, these are sent as part of the page request/response cycle, which means that web server threads can get tied up for long periods if many emails are being sent. To avoid this, Wagtail can be configured to do this as a background task, using `Celery `_ as a task queue. To install Celery, add ``django-celery`` to your requirements.txt. A sample configuration, using Redis as the queue backend, would look like:: import djcelery