refactor: remove S3 dependencies, use Django 5 STORAGES #11
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.
BREAKING CHANGE: Removed S3-specific storage configuration in favor of Django 5's STORAGES system
Changes:
Documentation updates:
Migration guide:
Applications should now configure storage backends using Django's STORAGES setting: STORAGES = {
'logs': {
'BACKEND': 'django.core.files.storage.FileSystemStorage',
'OPTIONS': {'location': '/var/log/myapp'},
}
}
Use get_log_storage() to access the configured log storage backend.