-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
whitenoise.runserver_nostatic is ignored #4469
Comments
So... what? How does it impact you? Why is it a bug? Please provide more details about what's expected and what actually happened. |
@browniebroke There is a package installed and added to project as Middleware and installed app but as it is now it has no use case, Django staticfiles run server is picked up instead of whitenoise's, how is this not a bug? |
I never said it wasn't: I asked for more details as I found your original message was a bit vague. |
For context, this was added in #2304 I can't remeber how to identify which command is used. From what I can see in the Whitenoise docs, we seem to be doing what's needed, as the app is isntalled before cookiecutter-django/{{cookiecutter.project_slug}}/config/settings/local.py Lines 45 to 49 in eca21f5
I haven't tried to re-generate a project to try to reproduce. What options have you used? PS: we have an issue template which asks which options were used, would have been nice to follow it (yes, it's actually useful). |
I cannot reproduce. When I run
The part I'm closing this as I cannot reproduce. Please provide more details to reproduce the problem on a fresh project generated from this template: options used and steps demonstrating the issue, with expected vs actual behaviour. |
What happened?
whitenoise.runserver_nostatic has no effect because of the order of INSTALLED_APPS, so the runserver command of staticfiles app is used instead of whitenoise.runserver_nostatic app
The text was updated successfully, but these errors were encountered: