Recognize files created after WhiteNoise is started about whitenoise HOT 4 CLOSED

No, it doesn't; this is by design. WhiteNoise is only intended to be used for serving a fixed set of static assets in production. In this case, adding or modifying static files always involves re-deploying and restarting the application.

I'll admit that the docs do need to be clearer on this though. The funny thing about open source is that you find people start using your project in ways you never imagined it being used!

I've added a separate ticket (#19) to document this better.

from whitenoise.

I am serving static files and I am attempting to do so in a production environment.

I was very excited to find this project because I could get away from project specific nginx configurations and handle everything with application code. It is doing great for most of the static files. But it can't serve these few files detailed below and requires using something like nginx which sort of defeats the purpose of adding WhiteNoise to a project.

If automatic recognition wont be added, is there any chance of getting some sort of hook to trigger this manually?

What do you suggest when using something like django-compressor? I am using offline compression for most of my files, but it cannot compress a few of the files offline and they are generated when the page is requested for the first time.

Another use for watching the filesystem would be building static files on one server and pushing them to a remote storage system. When the application gets a request for a static file it pulls the file to the local file system and serves it with WhiteNoise. This is nice because bundling all static files into the application deployment archive can add significantly to the size if some of the static files are large images or videos.

from whitenoise.

Not ignoring your points here, just busy with other stuff at the moment! I've had other people request something similar so I'll have a think about the best of way of handling this.

from whitenoise.

WhiteNoise v2.0 now supports an autorefresh option which will pick up changes to files after the server has been started. This is designed for development use and I don't recommend it for production, but the feature's now there if you want to use it.

from whitenoise.