Docs: design for serving multiple projects under one domain by path#13167
Draft
ericholscher wants to merge 1 commit into
Draft
Docs: design for serving multiple projects under one domain by path#13167ericholscher wants to merge 1 commit into
ericholscher wants to merge 1 commit into
Conversation
Design proposal for serving multiple projects under a single domain by path (example.com/docs/<project>/) without modeling them as subprojects, for customers who reverse-proxy a path prefix to us and can't delegate DNS. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VPEKF2tcrc5DqDLMsdkNUz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A customer wants to host many projects under a single path on their own company domain (e.g.
https://example.com/docs/<project>/…) but can't point that DNS at us. Today the only way to serve several projects under one domain by path is to model them as subprojects of a parent — which forces customers into a parent/child tree they don't otherwise want.This adds a design doc proposing the alternative: serve projects under a domain by path without a subproject relationship. It's meant to capture the approach and the open decisions before we commit to an implementation.
What
A new design doc under
docs/dev/design/that covers:custom_prefix, subprojects,X-RTD-Slug/RESOLVE_PROJECT_FROM_HEADER,USE_PROXIED_APIS_WITH_PREFIX)SERVE_PROJECTS_BY_PATHfeature and where it slots into the unresolver (after subprojects, matching the next segment to a project by slug)Related
/_/-under-prefix nginx work: Proxito: un-prefix /_/ paths served under a custom path prefix #13139The doc is deliberately scoped to the design and the decisions, so it's useful even if the prototype in #13140 changes shape.
🤖 Draft generated by Claude Code (AI agent), for review.
Generated by Claude Code