-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Proxito: Next steps on Improve URL Handling #9911
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
Comments
@stsewd Thoughts on next steps for this work? Wanting to make sure we don't lose it. |
So, the last thing I did related to this is #9726. There I'm refactoring the code so introducing the new resolver is easier. I was also playing with how the new implementation will look like at #9710 (DO NOT REVIEW, I'm only playing around with the new implementation). Next steps could be checking what we can remove/refactor from the middleware, so it is easy to integrate with the new implementation. I was thinking of introducing the new implementation incrementally, this is, serving some of our docs with the old implementation and other with the new one, this could be archived by splitting the traffic to each view, like serving all subprojects with the new implementation or projects that start with Oh, we also need to migrate projects using the custom URLs feature to the new implementation |
This sounds good. We could also just feature flag it?
Yea, that should be a very small number though at least. But a couple big ones on .com we want to be careful with. |
Hmm, looks like the linked PRs will close this issue when merged. |
Yea... silly. |
Fighting the bots :D |
Forgot to re-open this :D |
@stsewd can you expand here with an update for this issue? What's missing? What's blocked? What was done already? |
into a single entry point |
Excited for this! |
@stsewd are either of these good to plan on for next sprint? We need to roll out the proxito serving via feature flag more widely. Seems like the single view refactor will be easier, I'm guessing? |
That would be the final step, since it would be difficult to do that with a feature flag. |
Next steps after #10156 is merged:
|
I'm going to migrate the above comment into a new issue, since we're now done with the initial work here! The finishing work now lives in #10408 |
Design doc: https://dev.readthedocs.io/en/latest/design/better-doc-urls-handling.html
First work: #9534 #9500 #9462
What are the next steps here?
The text was updated successfully, but these errors were encountered: