Deployment #367
Merged
Deployment #367
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* `default_auto_field` is now automatically added to the generated `apps.py` file, and should therefore be added to our existing app configs
* The new default field type of auto-created primary key fields, is `BigAutoField`, so added migrations to change the type of
all existing `id` fields
* According to the docs (see the note on "Migrating auto-created through tables" in
https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-DEFAULT_AUTO_FIELD), foreign key fields in auto-created through tables
for many-to-many relationships, will not be updated by these migrations. However, this should not be a problem for us, as SQLite
(which is used on the server) only supports one `INTEGER` type anyway (which is the type that is used for both `AutoField` and `BigAutoField`
when using SQLite)
* The `default_app_config` variable in apps' `__init__.py` files has been deprecated
* Added `DEFAULT_AUTO_FIELD` to the settings, to ensure that auto-created primary key fields use the proper type.
This would normally be `BigAutoField`, but since `social-auth-app-django` has not yet updated to Django 3.2, it should be the old `AutoField`,
to prevent accidentally creating a migration for that package when running `manage.py migrate` - in addition to preventing a bunch of warnings
when Django runs its migration checks.
* Updated some Django admin classes to use the new `@admin.display()` annotation
(see https://docs.djangoproject.com/en/3.2/ref/contrib/admin/#django.contrib.admin.display)
This was caused by the value of the `registrations` entry of the `extra_context` dict field being stored in memory when the server starts, and never being refreshed - unless the server restarted (which until recently happened every 15 minutes; now it happens once a day).
Update to Django 3.2 + various fixes
mahoyen
added
the
deployment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brings in the changes from the following PRs: