-
Notifications
You must be signed in to change notification settings - Fork 31
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
Upgrade Middleware for Production #3131
Conversation
This was missed in 3a73743, and has caused Staging and Production deploys to fail.
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.
Looks good to me
This was updated for the new style middleware in 3a73743 but was not a complete migration. As of Django 1.10 django/django@05c888f, we need to use _get_response().
d5a02e2
to
7d2f25f
Compare
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.
I get a 301 when I http --print HhBb :8000/health-check
, but this looks good. 👍
Hmm, so do I actually. The 301 redirects to:
so it drops the port and adds a slash. I think that is happening because model-my-watershed/src/mmw/mmw/settings/base.py Lines 258 to 271 in 63a746d
But the health check is working correctly, which is the main issue. So I'll take that approval and run with it. |
Overview
This was missed in 3a73743, and has caused Staging and Production deploys to fail. Also fixes the health-check endpoint which was failing.
Connects #3130
Demo
http://civicci01.internal.azavea.com/view/mmw/job/model-my-watershed-packer-app-and-worker/1165/console
and
Testing Instructions