Figure out how to make `runserver_nostatic` work with Channels

At present, runserver_nostatic works by simply shadowing the runserver command from contrib.staticfiles and replacing it with the runserver command from Django core. However, this won’t work with Channels, which needs its own runserver command.

A possible approach might be to require that runserver_nostatic be at the top of the INSTALLED_APPS list and for it to discover the next highest priority runserver command (by inspecting the app registry and delegate to that, after setting the appropriate --no-static flag.

This is obviously more complex and fragile, but it would be nice to have a simple (for the user) solution which was agnostic as to whether Channels was being used.

[evansd]

@edevil No, I don’t think so. WhiteNoise works fine with Channels, but the small “runserver_nostatic” feature doesn’t. You can either ignore the issue in which case your app will use the default static file handling when in DEBUG mode, or you can manually pass the --nostatic option to runserver.

[evansd]

@amureki

Yes, you can now integrate WhiteNoise by adding it to settings.MIDDLEWARE_CLASSES rather than editing wsgi.py. This works with standard Django and with Channels.

See: http://whitenoise.evans.io/en/stable/changelog.html#simpler-cleaner-django-middleware-integration