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

HTTP 404 on static assets from django #1751

Closed
DerekSedlmyer opened this issue Oct 25, 2018 · 0 comments
Closed

HTTP 404 on static assets from django #1751

DerekSedlmyer opened this issue Oct 25, 2018 · 0 comments
Assignees
Labels

Comments

@DerekSedlmyer
Copy link
Contributor

When deploying StoryScapes, an HTTP 404 is returned for all non-composer static assets. Static assets were configured properly inside django as tested with:

python manage.py findstatic vendor/bootstrap/dist/css/bootstrap.min.css

When trying to access static assets through the Storyscapes URL or via http://django:8000 inside containers, an HTTP 404 is returned.

After some research, setting DEBUG=True solves this issue temporarily. Static files are not served via django unless DEBUG=True.

Recent changes to NGINX to proxy non-composer static assets to django looks to be the culprit.

The Storyscapes BOSH release has temporarily added DEBUG=True to workaround this issue.

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

No branches or pull requests

4 participants