Also consider the media files could number into the millions (or bajizillions?). Particularly for, say, a image hosting application. Clearly it would not be feasible to enumerate all the files, and there would clearly be regular additions. It might be that this use case is simply "beyond the scope" of a django-supplied static files server, and the developer should instead use nginx, lighttpd or something similar.
On Tuesday, December 29, 2015 at 9:31:02 AM UTC-8, David Evans wrote: > > 2. Serving media files is a slightly different case. WhiteNoise was > designed around the assumption that it's serving a set of > developer-supplied, public files which remain unchanged during the lifetime > of the process. This simplifies a lot of performance and security concerns > that come with serving mutable, user-supplied files. At present, if you use > `add_files(settings.MEDIA_ROOT, prefix=settings.MEDIA_URL)` as you > suggested then WhiteNoise won't pick up any files that were uploaded after > the application was started -- at least, not unless you enable the > "autorefresh" setting which I explicitly don't recommend for production. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/d489de11-018a-40e0-8419-40b4d18de9a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
