From 393fb4d70fc6bf88debc4ca13d644ea7de9602f5 Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 17 Nov 2026 16:32:23 +0000 Subject: dashboard: the federation, in a swarm holding a store MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In a swarm holding a store, the snapshot names the node's party, and the document box shows what counts as the node reads it, read every 5 s: the current version, the parties with their keys and nodes, the rules, the values at places as a tree with who writes there, the proposals on the version with where each stands, who voted what and what its version changes, and what the node refused. `document` beside `remake…` shows the document underneath. Where the node votes for its party by itself, a proposal that can still pass has a vote of each kind, cast through the node on a second click. The page writes no values: a party signs its writes with its key. --- docs/guides/federation/watching.md | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'docs/guides/federation/watching.md') diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md index b66d5b4..c04a6a3 100644 --- a/docs/guides/federation/watching.md +++ b/docs/guides/federation/watching.md @@ -23,6 +23,13 @@ besides it, the node's store, through its API and its log. checkpoint would let nodes forget; a node voting by itself proposes one at a count you set ([`voting-by-itself.md`](voting-by-itself.md)). +## On the dashboard + +A node's dashboard (`/admin/dashboard`) shows the same in its document box, read every +5 s: the version, the parties and which of their nodes are members, the values, the +proposals with who voted what and what each changes, and what the node refused +([`dashboard.md`](../../dashboard.md), Federation). + ## In the log At warn or error: -- cgit v1.3.1