diff options
Diffstat (limited to 'docs/configuration.md')
| -rw-r--r-- | docs/configuration.md | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/docs/configuration.md b/docs/configuration.md index ea401f5..0efdfc3 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -275,8 +275,16 @@ continuum-party vote 8d02 yes # krebs, the only one Where `node` names no user and no `token` is given, the client logs in to the node as its party, by `key`, where the federated node takes it: a party's session, which reads and puts events and nothing else ([`guides/federation/running-a-node.md`](guides/federation/running-a-node.md), -[Its API](guides/federation/running-a-node.md#its-api)). So `node = "https://node.example"` -and a key whose party a version names are all a party's people need. +[Its API](guides/federation/running-a-node.md#its-api)). The party is the one its record +names, or, without a record, `party`: a record is what votes go by, and what `again` +signs anew from, so one who only reads needs none. So a federation's directory with this +`party.toml` is all one of a party's people needs to read (`status`, `values`): + +```toml +node = "https://node.example" +key = "/home/alice/.ssh/laptop.pub" +party = "tv" +``` `key` is an OpenSSH private key file, or a public key an ssh-agent holds: the key itself (`key = "ecdsa-sha2-nistp256 AAAA…"`), or a file of such lines, whose first signs |
