# Hosting, access and deployment The browser client is `web/serve.mjs`: static files plus a `/connect` WebSocket proxy and `/artifacts/` proxy to the Pipelines server. Plain `node serve.mjs` is enough for local work. ## Password gate `serve.mjs` refuses pages, assets, artifacts and `/connect` without a signed session cookie. The password and signing secret live outside the repository: `~/.config/pipelines/web-auth.json` (mode `600`), e.g. ```json { "password": "…", "secret": "…" } ``` The sign-in page is `/login`; **Remember me** keeps a 30-day cookie, otherwise the cookie lives until the browser closes. Wrong passwords are throttled. Tests that start their own `serve.mjs` set `PIPELINES_WEB_AUTH=disabled`; never put that in a service. Changing the password: edit the file, then restart the web service. ## Bind and exposure For an untrusted network, keep the raw ports local: - Pipelines server: `-addr 127.0.0.1:8080`. - Web proxy: `--host 127.0.0.1` (reachable through Tailscale, not the LAN). - OpenCode: `server.hostname = "127.0.0.1"` in `~/.config/opencode/opencode.json`. Tailscale can terminate HTTPS for a tailnet-only name: ```sh tailscale serve --bg --https=8443 http://127.0.0.1:8095 # https://..ts.net:8443/ ``` That gives a valid certificate and a secure context (service worker, installable web app). Only tailnet devices can resolve the name; the password still applies to the app and its WebSocket. Keep the server and web proxy supervised by the platform's service manager so they restart after a reboot. Name the service files for your installation; their labels are local choices, not part of the protocol. The HTTPS proxy rule must also survive a reboot. ## Before exposing anything Check what listens beyond loopback (`lsof -nP -iTCP -sTCP:LISTEN`). The Pipelines server and the agent harness are control APIs without their own login; bind them to localhost and expose only the authenticated web proxy. If an app-managed server cannot bind loopback, a host firewall or tailnet ACLs are the remaining options. Unrelated operating-system services are outside this deployment.