Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Point the app at my real arm: a setting for the server with the camera and the SO-101, simulation when unset #3
Steward: the hosted app cannot reach the tailnet server yet - the cell refuses 100.89.95.68:8101 (not in forge.json egress, and private addresses are refused even when listed). The forge side is trevato/forge#3369 (an admin-granted exact address:port). Once it lands: add "egress": ["100.89.95.68:8101"] to forge.json here, and make sure the arm machine's server listens on its tailnet address (not 127.0.0.1).
Steward, probed the Pi ([email protected], 19:24Z): so101.service (arm server, HTTP API + WebSocket) listens on 0.0.0.0:8101; [email protected] serves the webcam as MJPEG on 0.0.0.0:8080 (port 8079+1); arm on /dev/ttyACM0. So forge.json egress needs both: "egress": ["100.89.95.68:8101", "100.89.95.68:8080"], and the proxy must carry the camera stream from :8080 (MJPEG, keep it streaming - no buffering). Both are granted by a site admin once trevato/forge#3437 lands.
Owner, 2026-10-20: "are there settings for me to point to my server that has the camera and arm?"
Today forge.json runs Software/so101/bench/fake-serve.ts - a simulated arm - and the UI talks to it same-origin (WebSocket /follow). The real stack runs on the owner's machine over serial (SO101_PORT / --port, leader --to ws://host:8101). Nothing lets the hosted app reach the real server.
Done:
ARM_SERVER(an app secret/env set on the app's settings page, e.g.ws://<host>:8101orhttps://<host>): when set, the hosted server proxies /follow, the status and the camera stream to it; when unset, it simulates as now. The UI shows which: "Live arm · <host>" or "Simulated".so101 serveon the arm machine, set ARM_SERVER, done. Note the network path the forge needs to reach it (e.g. the machine on the tailnet).