joakimp/pi-devbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(readme): pi-studio has --listen-all; the remote recipe describes the 0.10 URL
Lint / skill-floor (push) Successful in 9s
Details
Lint / hadolint (push) Successful in 12s
Details
Lint / doc-drift (push) Failing after 13s
Details
Lint / actionlint (push) Successful in 22s
Details

Browse Source 
README "Using pi-studio" said pi-studio hard-binds 127.0.0.1 with no bind flag.
It has had /studio --listen-all (binds 0.0.0.0) since 0.9.60; listed now as path
C, with a warning not to combine it with the studio-expose bridge on one port:
with STUDIO_EXPOSE=1, `/studio --listen-all --port 8765` fails with
"listen EADDRINUSE: address already in use 0.0.0.0:8765" (measured, tor-ms22,
v1.11.2).

The remote recipe described a 0.9 URL. Since 0.10 the printed URL also carries
studioTabState + hostedWorkspace and a token-only URL is answered 409; the
recipe now says to open the whole URL, names the wrapped-URL copy hazard
("This link looks damaged..."), says Studio must run on the published port
(only the laptop's side of ssh -L is free) and that --port does not move a
running server, adds --watch <file>, and gives an on-host curl that tells
"chain up" (403) from "Studio down or on another port" (empty reply).

All of it measured on tor-ms22 2026-10-14 (pi-studio 0.10.1): tunnel through
the host sshd + headless browser load, both modes; --listen-all reached on the
container's eth0 (200 / 403 without token). Docs only; no pin changes.
This commit is contained in:
Joakim Persson
2026-10-14 18:45:46 +02:00
parent bf265f6d54
commit 1e4c238a83
2 changed files with 70 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+26
View File
@@ -11,6 +11,32 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
---
## Unreleased
Docs only: this entry changes no pin.
### Fixed
- **README "Using pi-studio" said pi-studio has no bind flag.** It has had
`/studio --listen-all` (binds `0.0.0.0`) since pi-studio 0.9.60, so the
section now lists it as path **C**, next to host networking (A) and the
`studio-expose` bridge (B). It also warns not to combine B and C on one port.
With `STUDIO_EXPOSE=1` the bridge holds the egress IP on `$STUDIO_PORT`
from boot, and `/studio --listen-all --port 8765` then fails with
`listen EADDRINUSE: address already in use 0.0.0.0:8765` (measured on
tor-ms22, v1.11.2).
- **The remote recipe described a pi-studio 0.9 URL.** Since 0.10 the printed
URL carries `studioTabState` and `hostedWorkspace` as well as the token, and
a token-only URL is answered `409`. The recipe now says to open the whole
URL, and names the copy hazard: the URL wraps, a side panel's text can land
inside it, and Studio answers *"This link looks damaged…"*. It also says
Studio must run on the **published** port (only the laptop's side of
`ssh -L` is free to choose) and that `--port` does not move a running server
(`/studio --stop` first). Two more additions: `--watch <file>` for a rendered,
read-only preview, and an on-host `curl` that tells "chain up" (`403`) from
"Studio down or on another port" (empty reply). A remote session hit exactly
that: Studio was started on `18765` while only `8765` is published.
## v1.11.2 — 2026-10-14
**v1.11.1 was tagged and never published.** Run 724 failed one smoke assertion