1268277 - Switch to Celery-recommended Django integration

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: Code Cleanup, enhancement)

Description

[John Whitlock [:jwhitlock]]

What problem would this feature solve?
======================================
Kuma currently uses the django-celery package to integrate async tasks with Django.  However, with Celery 3.1, the django-celery package was deprecated and a new integration was recommended:

http://docs.celeryproject.org/en/latest/django/first-steps-with-django.html

Who has this problem?
=====================
Staff contributors to MDN

How do you know that the users identified above have this problem?
==================================================================
We are calling calling djcelery.setup_loader() in the configuration file to collect tasks, instead of the current recommended way.

How are the users identified above solving this problem now?
============================================================
django-celery works with Django 1.8, used in production.  It may not work with future versions of Django,

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Follow the new instructions, creating the new files (celery.py, etc.) as needed. Remove 'djcelery' from INSTALLED_APPS.

Is there anything else we should know?
======================================
The SCL3 hosts use a puppet-controlled settings file instead of environment variables to configure the Kuma hosts.  The documented configuration bases this file on the DJANGO_SETTINGS_MODULE environment variable. Work may be needed to ensure this works correctly in SCL3.

My recommendation is to wait until after containerization and moving to AWS.

Comment 1

[John Whitlock [:jwhitlock]]

The django-celery project is lightly maintained, and was updated to Django 1.10. It works in Django 1.11, but may not work in Django 2.x or later.

Comment 2

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.