|
Some checks are pending
offline / test (push) Waiting to run
Paused or unhealthy replicas mark the service degraded even if the tree-node floor is still met. Unmanaged NATS with no process is down. |
||
|---|---|---|
| .. | ||
| public | ||
| services | ||
| src | ||
| test | ||
| .gitignore | ||
| fleet.json | ||
| NATS.md | ||
| package.json | ||
| README.md | ||
| SERVICES.md | ||
| SUMMARY.md | ||
verae-fleet
Operator control plane for Verae Time × Zapier runtime services:
- a list of every service and its config file
- a central replica spec (
fleet.json) — how many copies must be up - a monitor of active / paused / unhealthy replicas
- restart when a copy is offline or fails
/health - on / off / pause / resume per service or per instance
- keepFloor on tree nodes so at least
mincopies stay available (paused copies do not count)
cd packages/verae-fleet
npm test
node src/cli.js list
node src/cli.js serve # http://127.0.0.1:3850/
Against a running daemon:
node src/cli.js status
node src/cli.js pause tree-node-0 # floor starts another tree-node
node src/cli.js resume tree-node-0
node src/cli.js restart tree-node-1
node src/cli.js stop webhook-deliver # disable that service
node src/cli.js start webhook-deliver
Zapier cloud apps are listed but not spawned. NATS on NS1 is monitored only (loopback :4222, never a public bind).
Clone: ssh://git@git.georgelambert.org:2223/marchon/verae-fleet.git