docs: document correct Tailscale Funnel setup - #285
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe documentation adds Tailscale Funnel instructions for proxying the complete DevSpace server from the root path. It explains that ChangesTailscale Funnel documentation
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This change documents the correct root-level Tailscale Funnel setup and warns against mounting only Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches🧪 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 |
Greptile SummaryThis PR documents the correct root-level Tailscale Funnel configuration for exposing DevSpace to ChatGPT.
Confidence Score: 5/5The documentation-only PR appears safe to merge. The documented port and root proxy configuration match DevSpace’s defaults and preserve access to the MCP endpoint and root-level OAuth and application routes.
|
| Filename | Overview |
|---|---|
| docs/setup.md | Adds root-level Tailscale Funnel setup guidance consistent with DevSpace’s port and route layout. |
| docs/gotchas.md | Explains why mounting Funnel at /mcp causes failures and directs users to proxy the complete origin. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart LR
Client["ChatGPT / MCP client"] --> Funnel["Tailscale Funnel at origin root"]
Funnel --> Server["DevSpace :7676"]
Server --> MCP["/mcp"]
Server --> OAuth["OAuth discovery and authorization routes"]
Server --> Apps["/mcp-app-assets"]
Reviews (1): Last reviewed commit: "docs: document Tailscale Funnel root pro..." | Re-trigger Greptile
Follow-up to #147. The connection failure comes from mounting Tailscale Funnel specifically at
/mcp: the mount prefix is removed before proxying, and DevSpace also exposes OAuth discovery/authorization and MCP App routes outside/mcp. Adding a Tailscale-specific root MCP alias would therefore address only one symptom.Document the root-level Funnel setup (
tailscale funnel --bg 7676) in ChatGPT setup and troubleshooting, and explicitly warn against--set-path=/mcp. This keeps DevSpace tunnel-agnostic while preserving the full public route surface unchanged.Summary by CodeRabbit
/mcp.