Create the server token at install and document the security boundary

This commit is contained in:
2026-11-10 00:59:39 +00:00
parent 547d4d9822
commit 12a74247ae
7 changed files with 245 additions and 1 deletions
+3
View File
@@ -15,6 +15,9 @@ service manager directly. Legacy Python-managed installations require an explici
`PIPELINES_PREFIX`; no configuration is inferred from the executable's location.
For source development, use `go run ./cmd/pipelines help`; start the native server
separately. Set `PIPELINES_URL` or pass `--url` to select another server.
A loopback server started with `-token-file` requires the shared token; the CLI
reads it from `PIPELINES_SERVER_TOKEN_FILE` or `~/.config/pipelines/server-token`
and sends it only to loopback URLs (`docs/notes/security-boundary.md`).
## Dashboard and status