Skip to content
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

apps.base's static url conflicts with the django development server's built-in static assets #21

Open
bradmontgomery opened this issue Oct 31, 2014 · 2 comments

Comments

@bradmontgomery
Copy link
Contributor

By default, the django development server will serve all static files (images, js, css) at /static/. Unfortunately, The ^static$ url in app.base.urls conflicts with this, and anyone trying to get the registryServer running in a development environment will have troubles.

Is the related view app.base.views.static even used anywhere? The comment a few lines above this makes me think this might be cruft.

Would it be safe to remove this code?

@RogerTangos
Copy link

pinging @brian717

@brian717
Copy link
Member

The static view and corresponding URL are terrible. No idea why they're there, but they predate even my involvement with the project. Feel free to remove them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants