Enabling Customization of Storage Backends #105
Merged
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.
Overview
This PR enables customization of storage backends. It introduces a new setting
IMPORT_EXPORT_CELERY_STORAGE
, and can be used as follows:By setting this field in your django settings, you will be able to customize where all files related to
django-import-export-celery
go.In my case, I would like these files to have more access control, so I would do something like this:
Rationale
This PR is necessary because the only way to customize the storage backend is by modifying the
default_storage
setting in django. However, since this applies globally, if you were to setdefault_storage
to a private/protected storage backend, you would be unable to have publicly accessible media, hence this request for change.