feat(peering): admin enable/disable from the panel (#134) #135

Merged

Cordy merged 1 commit from feat/peering-enable into main

2026-08-07 01:20:54 +00:00

Cordy commented

2026-08-07 01:20:25 +00:00

Owner

Closes #134.

Makes peering something an admin turns on and off from the running instance, instead of a deploy-time config decision.

Two-level gating, resolved. peering.statePath now defaults to /data/.cairn/peering.json (config.go), so the subsystem is always mounted — the admin panel, key issuance and peer registration work on every instance. The runtime peeringEnabled setting decides whether the transport actually answers.

Server. PeeringSendAPI gains an Enabled func() bool gate (nil = ungated, so existing tests are unchanged). send/peers/transfers return 503 when peering is off. main.go wires the existing peerOn closure (settingsStore.Get().PeeringEnabled). Because the send UI feature-probes GET /peering/peers, the 503 makes the send surface auto-hide until an admin turns peering on. New test: TestSendSurfaceUnavailableWhenPeeringOff.

UI. A labelled enable/disable switch at the top of the Instance-peering panel, bound to serverSettings.peeringEnabled. Toggling it re-PUTs the full settings object with the flag flipped — no new endpoint. i18n for all four locales; a quiet notice explaining what "off" means.

No new server endpoint; reuses GET/PUT /api/v1/settings. Green on the branch: gofmt/vet clean, full go test ./... pass, go build ./... clean, both JS blocks pass node --check.

Closes #134. Makes peering something an admin turns on and off from the running instance, instead of a deploy-time config decision. **Two-level gating, resolved.** `peering.statePath` now defaults to `/data/.cairn/peering.json` (config.go), so the subsystem is always *mounted* — the admin panel, key issuance and peer registration work on every instance. The runtime `peeringEnabled` setting decides whether the transport actually *answers*. **Server.** `PeeringSendAPI` gains an `Enabled func() bool` gate (nil = ungated, so existing tests are unchanged). `send`/`peers`/`transfers` return `503` when peering is off. `main.go` wires the existing `peerOn` closure (`settingsStore.Get().PeeringEnabled`). Because the send UI feature-probes `GET /peering/peers`, the 503 makes the send surface auto-hide until an admin turns peering on. New test: `TestSendSurfaceUnavailableWhenPeeringOff`. **UI.** A labelled enable/disable switch at the top of the Instance-peering panel, bound to `serverSettings.peeringEnabled`. Toggling it re-`PUT`s the full settings object with the flag flipped — no new endpoint. i18n for all four locales; a quiet notice explaining what "off" means. No new server endpoint; reuses `GET`/`PUT /api/v1/settings`. Green on the branch: gofmt/vet clean, full `go test ./...` pass, `go build ./...` clean, both JS blocks pass `node --check`.

Cordy added 1 commit

2026-08-07 01:20:26 +00:00