-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add whitenoise to serve static assets #10
Comments
Resolved in 83fc8dd |
"resolved in" comments should be done with PR numbers so that the issue gets closed when the PR is merged |
It's more common to do it the other way around, e.g. the PR that addresses this will say |
Got it and will do |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's some information for how we could do that (shouldn't be much different if deployed elsewhere): https://devcenter.heroku.com/articles/django-assets
This way we can have the logo, CSS, etc. all served with this project without having to go through much trouble.
The text was updated successfully, but these errors were encountered: