-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Port additional features to proxito #6286
Conversation
Co-Authored-By: Manuel Kaufmann <humitos@gmail.com>
…org into proxito-cleanup
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.
Look good to me! I left some comments about style or to improve tests readability.
I can do some QA once we have the PR for ops with the NGINX required changes.
self.assertEqual( | ||
response.status_code, 404 | ||
) |
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.
We may want to assert that we are receiving the content of the custom page here as well and not the default maze.
robots.txt, sitemap.xml and custom 404 (on latest, on specific version and not on latest) work properly with the NGINX fallback. |
Co-Authored-By: Manuel Kaufmann <humitos@gmail.com>
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.
Everything looks good to me!
This moves over almost all of the doc serving logic from Django into Proxito. Most importantly:
It also fixes some of the bugs that we saw during the initial deployment:
/en/latest/foo
where it should servefoo/index.html
This required additional nginx configuration changes, which I will put in another PR in ops. It would be cool to be able to test them against this, but not quite there yet.
Closes #6331
Closes #6332