Some checks are pending
offline / test (push) Waiting to run
Restarts crashed units unless the admin console paused or stopped them. Fleet writes per-instance intent.json. Tested on 138: crash-restart, pause-hold, watch respawn of keep.
1.3 KiB
1.3 KiB
verae-keep
Host keep-alive for Verae workers. Restarts a unit that crashed unless the operator console paused or stopped it.
Forgejo: https://git.georgelambert.org/marchon/verae-keep
Two processes:
| Process | Port | Job |
|---|---|---|
node src/keep.js |
:3860 |
Probe units, spawn if intent is run |
node src/watch.js |
:3861 |
Restart keep if /health fails |
scripts/guard.sh |
— | Restart watch if watch exits |
Intent is run | pause | stop. Sources, newest wins:
POST /intent/:id(admin / API)~/verae-fleet-runtime/data/<instance>/intent.json(fleet writes this on start/pause/stop)- live
FLEET_URL/api/statuswhen set - unit
defaultIntent(run)
Pause: leave the process down or POST /pause. Stop: SIGTERM and do not spawn. Run: spawn if health fails.
NS1 (70.88.205.138)
KEEP_UNITS=$HOME/verae-keep/units.ns1.json KEEP_STATE=$HOME/verae-keep/data \
nohup bash scripts/guard.sh >/tmp/verae-keep-guard.out 2>&1 &
Or systemd user unit systemd/verae-keep-guard.service (loginctl enable-linger).
Units: NATS (observe only), job-poller, webhook-deliver, archive-aggregator, archive-worm ×3, tree-node ×3.
API
GET /healthGET /statusPOST /intent/:id{"state":"pause|stop|run"}POST /reconcile