Archived
docs: use extensionless canonical URLs
This commit is contained in:
@@ -108,7 +108,7 @@ PI WEB keeps its own state intentionally small:
|
||||
|
||||
## Machine federation
|
||||
|
||||
The Machines section lets one PI WEB instance act as a gateway to other PI WEB runtimes. Register a remote machine from **Actions → Add Machine** with the remote PI WEB base URL, for example a URL reachable over NetBird, Tailscale, WireGuard, an SSH tunnel, or a trusted reverse proxy. The browser continues talking to the local PI WEB origin; project, workspace, file, git, session, activity, and terminal HTTP/WebSocket traffic is proxied server-to-server. See the [Fleet guide](https://pi-web.dev/machines.html) for setup, trust model, and troubleshooting details.
|
||||
The Machines section lets one PI WEB instance act as a gateway to other PI WEB runtimes. Register a remote machine from **Actions → Add Machine** with the remote PI WEB base URL, for example a URL reachable over NetBird, Tailscale, WireGuard, an SSH tunnel, or a trusted reverse proxy. The browser continues talking to the local PI WEB origin; project, workspace, file, git, session, activity, and terminal HTTP/WebSocket traffic is proxied server-to-server. See the [Fleet guide](https://pi-web.dev/machines) for setup, trust model, and troubleshooting details.
|
||||
|
||||
Remote model-provider credentials and OAuth state stay on the target machine. API-key provider configuration can be proxied, but OAuth login should be completed by opening the remote PI WEB directly. Register remote machines only when you trust the endpoint and the network path: adding a machine gives this PI WEB server permission to contact that URL with the optional bearer token you configured.
|
||||
|
||||
@@ -122,7 +122,7 @@ A useful prompt for AI agents:
|
||||
|
||||
```text
|
||||
Build a PI WEB plugin for this project. Goal: <describe the UI behavior>.
|
||||
Before coding, read https://pi-web.dev/plugins.html and https://pi-web.dev/plugins.md.
|
||||
Before coding, read https://pi-web.dev/plugins and https://pi-web.dev/plugins.md.
|
||||
Create it under ~/.pi-web/plugins/<plugin-id> using the documented PI WEB v1 plugin API.
|
||||
Validate with /pi-web-plugins/manifest.json and explain reload/debug steps.
|
||||
Do not modify PI WEB itself.
|
||||
|
||||
Reference in New Issue
Block a user