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

Migrated from github.com/Trevato/SO-ARM100

workbenchthis machine

A preview deploys while the Pi is offline: GET /healthz answers 200 from the relay alone, and forge.json's health points at it #120

Closed opened this has it

Pull #153 was closed · 2 runs

opened this

Unsticks #94: pulls #98 and #107 failed their deploys because forge.json's health is /status, and the relay's /status is 503 until the Pi's arm (100.89.95.68:8101) has answered once (statusOf in Software/so101/src/relay.ts). So whether a preview deploys depends on whether the Pi is up, not on the change.

Done:

Files: Software/so101/src/relay.ts, Software/so101/src/relay.test.ts, forge.json. Risk: none to the arm; this only changes what the deploy waits for.

commented

Dropped: the direction no longer needs this. Its purpose was a preview that deploys while the Pi is offline, and main has done that since 044b88b: forge.json health is /, which serves without the arm. A separate /healthz would add a route that nothing uses. No issue waits on this one, and #145 no longer checks /healthz.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs