sscoble/pi-mono
1
0
Fork 0
mirror of https://github.com/badlogic/pi-mono.git synced 2026-11-05 23:37:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

feat: p2 TUI through Radius (npm run tui -- --radius)

Browse source 
The launcher signs in to Radius itself and reaches its server as a Radius
client; the brain answers client channels with loopback requests as the
relay owner. Temporary: one Radius connection per request, bundle check
every 10 s; docs/p2-notes.md describes the single-connection follow-up.
This commit is contained in:
David Brailovsky 2026-11-05 20:26:03 +01:00
parent e3c8c3b486
commit d9af3d73af
15 changed files with 1159 additions and 335 deletions
Download patch file Download diff file Expand all files Collapse all files

19
apps/p2/docs/p2-notes.md
View file

@ -432,6 +432,25 @@ npm start
admission and provider access, HTTP credit in both directions, congestion, forwards, redirects, WebSockets,
unavailable ports and anonymous public/private gates. All listeners use port 0 and private temporary data.
### TUI through Radius
`npm run tui -- --radius [<server-id>]` reaches the server through Radius, without a tunnel or owner link. The
launcher signs in to Radius itself (device code, saved in `~/.pi/p2-tui/radius.json`, separate from any server's
`radius.json`), picks the given server or the user's only online one (`GET /v1/servers`), and connects to
`/v1/servers/<id>/connect` with its bearer token (`pi-server.client.v2`). Radius admits only the server's owner and
opens a `ws` channel without a request; the brain ("Client channels" in `brain.ts`) reads the request from the
client's first message and makes it a loopback request marked like the owner's browser requests, without a shell
origin (`access: "relay"`: no owner links). The launcher's requests go through a transport (`tui-transport.ts`,
`tui-radius.ts`); the direct cookie transport is unchanged. Only v5 relays (channel sockets) carry client channels.
**Temporary: one Radius connection per request.** Radius allows 120 new connections a minute per user, shared with
the server's own reconnects, so through Radius the launcher checks for a new bundle every 10 s instead of every
second, and every request (owner check, manifest, bundle, downloads, uploads) and every chord link reconnect costs a
connection setup. The proper form keeps one connection per launcher and carries all of its requests and its chord
link over it: every message labelled with the request it belongs to, both sides sorting them, and large transfers
taking turns with the chord link so a download cannot hold up live output. Then the 1 s bundle check returns.
`test/p2/radius.test.ts` and `test/p2/tui-radius.test.ts` cover client channels with the same fake relay.
## Browser navigation
`src/web/navigation.ts` is an independent, minimized copy of Pi Mobile's stack. `src/runtime/web.tsx` exposes