archive/django-background-workers-rfc
Archived
1
Fork 0
Code Activity

Link to PRs

Browse source
This commit is contained in:
Jake Howard 2024-02-07 08:39:19 +00:00
parent 2a1ff5296b
commit a71f3a88bd
No known key found for this signature in database
GPG key ID: 8198AEBFA7E86782
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -3,6 +3,8 @@
* Author: Jake Howard, with help from the Wagtail Performance sub-team * Author: Jake Howard, with help from the Wagtail Performance sub-team
* Created: 2024-02-07 * Created: 2024-02-07
For discussions, check out the [associated PR](https://github.com/RealOrangeOne/django-background-worker-rfc/pull/1) and [Discussions](https://github.com/RealOrangeOne/django-background-worker-rfc/discussions).
## Abstract ## Abstract
Wagtail currently doesn't have a first-party solution for long-running tasks. Other CMSs in the ecosystem such as WordPress and Drupal have background workers, allowing them to push tasks into the background to be processed at a later date, without requiring the end user to wait for them to occur. Wagtail currently doesn't have a first-party solution for long-running tasks. Other CMSs in the ecosystem such as WordPress and Drupal have background workers, allowing them to push tasks into the background to be processed at a later date, without requiring the end user to wait for them to occur.