Skip to content

Use the default EMAIL_BACKEND not celery

decentral1se requested to merge fix_default_email_backend into develop

Created by: tomd-aptivate

Celery isn't installed by default so the site is broken with the current starting configuration (so we should either include django celery in the default packages or not require it).

I've gone for the not requiring it route as it's not clear if we always want to start with Celery as the email backend (a simple site may not need it).

Merge request reports