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

Migrated from github.com/Trevato/SO-ARM100

workbenchthis machine

The Pi runs what main ships: each deploy updates the arm server on the Pi (swap, restart while idle, roll back if unhealthy) #467

shipped merged opened this has it

Landed in pull #471 · run

opened this

Found 2026-10-21 16:15Z. The Pi's arm server ran code from 2026-10-20 19:59: 25 files in src/, against 126 on main. Every server-side change since then (the Governor, zones, table offset, STOP handling, settings) had been tested only against the fake bus and never run on the real arm. No step updates the Pi.

What the steward did: swapped main @ 2a725c7 onto the Pi by hand, at /home/dietpi/so101. The old tree is at so101-prev-20261021 and src.old-20261021. Then restarted so101. It is live with real joints. tableOffsetMm is now −20 (owner: "the table is too high… impedes control").

Done when:

  • The Pi follows the deployed commit automatically. After a production deploy of trevato/arm, the hosted app (or a deploy step) checks the Pi's /version. If it differs, it copies Software/so101 to the Pi as crew over SSH (key: the ARM_PI_SSH_KEY secret; port 22 egress is already allowed) into a new directory, swaps directories atomically, and restarts so101, only while nobody holds a turn.
    • Keep the previous tree for rollback.
    • If /status isn't live within 10 s, roll back automatically.
  • The Pi reports its commit: GET /version on the arm server returns the commit, and the page footer shows both commits (app and Pi). A mismatch shows as a warning on the admin page.
  • Test: a fake "Pi" target directory, a deploy of a new commit, the swap, and a rollback when the health check fails.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs