Bugfixes: - https://github.com/devilry/devilry-django/issues/477 - https://github.com/devilry/devilry-django/issues/478 -
The most significant change is django-celery-email as email backend.
django-celery-email sends all email into the Celery task queue, which then sends email in the background one at a time. This fixes scalibility problems when adding feedback in bulk. The issue that triggered this change was https://github.com/devilry/devilry-django/issues/477.
BACKUP. YOUR. DATABASE. AND. FILES.
Previous versions of devilry-deploy defined the logdir in the [supervisor]-section of buildout.cfg. This has been moved to [variables]. You should end up with something like this:
[variables]
logdir = /var/log/devilry
Update REVISION to v1.3.5 using the instructions in the update guide, but stop after step 3.
Note
Settings are configured in devilry_prod_settings.py (see Build Devilry).
The default location is /etc/devilry, but it may have been placed in a custom location (also explained in Build Devilry).
To configure Devilry to use django-celery-email, do the following:
Make a backup of your current devilry_prod_settings.py, and put it somewhere safe in case the new email backend does not work correctly.
Replace the value of your EMAIL_BACKEND-setting with djcelery_email.backends.CeleryEmailBackend.
Prefix all other EMAIL_*-settings with CELERY_. You should end up with something like this:
EMAIL_BACKEND = 'djcelery_email.backends.CeleryEmailBackend'
CELERY_EMAIL_HOST = 'smtp.example.com'
CELERY_EMAIL_PORT = 25
Run the last step of the update guide.
The that sending email works. You can do this as follows:
If you have the correct email address configured in Devilry, you should receive an email if sending is workin.
If it does not work, you should restore the old devilry_prod_settings.py and restart Devilry.