From 7fc844ff0167fb0943e3fa85af671d8f3bbf005d Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 17 Nov 2026 16:18:58 +0000 Subject: continuum-party: options from configuration files, as the node's `continuum-party` takes its options (`node`, `token`, `key`, `record`: `config::PARTY_OPTIONS`) on the command line and in configuration files of the node's format: `--config`, repeatable, arguments winning, `--unset`, includes and imports. The configuration's loader takes the options it reads as a table (`config::with_options`, `config::merged`, `file::load_with`), the node's or the client's, and a key naming none of them is an error in either; `node` and `token` are secrets, never logged. --- docs/guides/federation/getting-started.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'docs/guides/federation') diff --git a/docs/guides/federation/getting-started.md b/docs/guides/federation/getting-started.md index 8ce4c19..5d46192 100644 --- a/docs/guides/federation/getting-started.md +++ b/docs/guides/federation/getting-started.md @@ -114,7 +114,11 @@ continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv. # 3a9f… taken ``` -The value is JSON. lass reads it on its node, with everything else that counts: +The value is JSON. The client's options can go in a configuration file instead, as the +node's do ([`configuration.md`](../../configuration.md), The party's client): +`continuum-party --config tv.toml write …`. + +lass reads it on its node, with everything else that counts: ```sh curl -s -u lass:secret localhost:3000/events/counts | jq .values -- cgit v1.3.1