jb/paseo
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add connectivity guide

Browse Source
This commit is contained in:
Mohamed Boudra
2026-08-04 00:42:34 +02:00
parent 3a9d39b63a
commit 74dea38456
7 changed files with 103 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
public-docs/web-ui.md
+1 -1
View File
@@ -63,7 +63,7 @@ The same HTTP server keeps serving the API (`/api/*`), MCP (`/mcp/*`), service-p
Three common ways to run it, in order of exposure:
- **Same machine.** Daemon and browser on one box. Open `http://localhost:6767/`. Nothing else to configure.
- **Private network (LAN or VPN).** Reach the daemon from other devices on a network you trust, a home LAN or a [Tailscale](https://tailscale.com) tailnet. Bind the daemon to that interface and connect to it by address.
- **Private network (LAN or VPN).** Reach the daemon from other devices on a network you trust, a home LAN or a [Tailscale](https://tailscale.com) tailnet. Follow the [Connectivity guide](/docs/connectivity#tailscale) for the complete direct setup.
- **Public reverse proxy or tunnel.** Expose the UI on a domain over HTTPS, terminating TLS at a reverse proxy or a tunnel. This is the full self-hosted setup.
The rest of this page builds from local to public. **Verify a direct connection works before you add a proxy in front of it**, it isolates daemon problems from proxy problems.