-
Notifications
You must be signed in to change notification settings - Fork 44
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
Use nginx as reverse proxy in production #50
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work!
i think it makes sense to leave this PR as is until #51 is merged, then ill incorporate those changes into this one |
sgtm! |
@justinrporter I combined the changes from #58 into here, as well as combined the documentation. Let me know what you think. Also, I don't see the docs page from http://localhost:7000/ or http://localhost:7000/getting-started/ does the list not autogenerate? Also: I modified /.envs/.production/.umkc to to keep DJANGO_ALLOWED_HOSTS=osler.umkc.edu, please check this is correct as it isn't present in #58 |
Uses nginx with static file caching instead of traefik
to test, .envs/.production/.secrets should resemble: