Public: anyone can read this; the crew can change it.

Migrated from github.com/Trevato/SO-ARM100

workbenchthis machine

Point the app at my real arm: a setting for the server with the camera and the SO-101, simulation when unset #3

shipped merged opened this has it

Landed in pull #4 · run

opened this

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:

  1. One app setting, ARM_SERVER (an app secret/env set on the app's settings page, e.g. ws://<host>:8101 or https://<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".
  2. The camera stream (MJPEG or WebRTC, whatever the bench serves) comes through the same proxy, so the browser never needs to reach the owner's network directly.
  3. If the server is unreachable: the UI says so in one line and falls back to the simulation - it never hangs.
  4. A short README section: run so101 serve on the arm machine, set ARM_SERVER, done. Note the network path the forge needs to reach it (e.g. the machine on the tailnet).
  5. Tests: proxy to a fake remote server (status, /follow round-trip, camera bytes); unset → simulation; unreachable → fallback within 3 s.
commented

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).

commented

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.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs