Forward /.well-known/ to backend in custom Nginx configuration - #1107
Forward /.well-known/ to backend in custom Nginx configuration#1107Harry-Chen wants to merge 1 commit into
Conversation
|
@Harry-Chen is attempting to deploy a commit to the goldflag's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe self-hosting Nginx guide now proxies ChangesSelf-hosting Nginx guide
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the self-hosting “custom Nginx” documentation to route /.well-known/* requests to the backend, enabling OAuth auto-discovery for the MCP client.
Changes:
- Expands backend proxy routing to include
/.well-known/*alongside/api/*via a singlelocationrule. - Renames location comments (“API requests” → “Backend service”, “Client app” → “Client service”).
- Fixes the trailing code fence alignment at the end of the document.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
MCP client depends on this path for OAuth auto-discovery.
Summary by CodeRabbit