Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update application code to use Django 3.x #47

Merged
merged 15 commits into from
Aug 8, 2020
Merged

Update application code to use Django 3.x #47

merged 15 commits into from
Aug 8, 2020

Conversation

KHIT93
Copy link
Owner

@KHIT93 KHIT93 commented Aug 2, 2020

We have been waiting with upgrading to Django 3.x as some of the packages used, were not yet compatible.

We have decided to remove the current audit logging functionality, which was provided by django-auditlog

Additionally, we have retired django-encrypted-model-fields, as it had some issues with the generated encryption key on new installs. We have instead using django-cryptography instead.

We will need to provide a migration path between the two libraries, as users with 2FA enabled, will loose the configuration.
If a valid migration path cannot be found, then users would need to re-enable 2FA on their account

With this change, we are also changing some of the terminology used, to better align with MailScanner.
See here for related information: MailScanner/v5#492

@KHIT93 KHIT93 changed the title Update application code to use Django 3.0.x Update application code to use Django 3.x Aug 8, 2020
@KHIT93 KHIT93 merged commit 90c1adb into master Aug 8, 2020
@KHIT93 KHIT93 deleted the upgrade-django3 branch August 8, 2020 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant