Fixed #27929 -- Added keep_original_files option to ManifestFilesMixin. #19719
+252
−28
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.
Trac ticket number
ticket-27929
Branch description
When collecting static files with ManifestStaticFilesStorage, both hashed and original versions are created by default. This adds a keep_original_files attribute to allow removal of original non-hashed files after processing for production deployments where only hashed versions are needed.
There have already been two PR's on this #17328 by @theumang100 and #16625 by @valleyofblackpanther
This PR is more inspired by whitenoise's approach of keeping a track of which files to delete during processing and then deleting them at the end, though uses a slightly different approach.
It also makes it more convenient to update the ManifestStaticFilesStorage configuration from the already supported OPTIONS keyword of the STORAGES setting.
eg
Checklist
main
branch.