(For some reason GMail is clipping your message before any content, I only saw '... [Message clipped]' and had to click to see it all)
I'm not that familiar with the static file storages, but it seems to me like it's not going to be that controversial deprecate it in order to save this duplication. The docs do read: CachedStaticFilesStorage isn’t recommended – in almost all cases > ManifestStaticFilesStorage is a better choice. On 15 September 2017 at 17:58, <emor...@mozilla.com> wrote: > Hi! > > Currently when using `ManifestStaticFilesStorage`, collectstatic generates > duplicate versions of some files. For example looking at the output for > contrib.admin for Django 1.11.5, there is: > - admin/css/base.css > - admin/css/base.5af66c1b1797.css > - admin/css/base.6b517d0d5813.css > - admin/css/base.31652d31b392.css > > This is exacerbated when using something like WhiteNoise's > CompressedStaticFilesMixin, > which then has to spend extra time generating gzip and Brotli compressed > versions of every file (or else try and work around it). > > I was going to file a ticket about fixing this, however it appears to be > unavoidable/working as intended according to: > https://code.djangoproject.com/ticket/24452#comment:16 > > In that ticket and corresponding PR, it's mentioned several times that > CachedStaticFilesStorage is suboptimal and should probably be removed, and > if that occurred it would then be possible to avoid the duplication. > > As such, I'd like to propose that `CachedStaticFilesStorage` be marked as > deprecated for the Django 2.0 release (with the warning suggesting people > use `ManifestStaticFilesStorage` instead), so we could then remove it and > make these optimisations in Django 3.0. > > Thoughts? > > Many thanks, > > Ed > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/b5a12c9b-ab4b-4431-b633- > 43a0ddfdd534%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/b5a12c9b-ab4b-4431-b633-43a0ddfdd534%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Adam -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM3q9DgEqMNV%3DtwU%2BajbzodOZnyeTH_h%3DnQbjE0n4DK3LQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
