From c66f0f8f7297484e095e02d259c84469b6c42367 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 19:00:05 +0000 Subject: continuum node-id: a node key's ID, without starting the node The founders name each node by its ID in the first version, before the federation starts; getting it meant starting a node once with --node-key-create and reading its log. `continuum node-id FILE` prints the node ID of the key FILE holds and exits, `--create` making the key there first where there is none (saying so on standard error). Logs are off for it, as for --print-config: the ID goes to standard output alone. --- docs/guides/federation/getting-started.md | 10 +++++----- docs/lifecycle.md | 4 +++- 2 files changed, 8 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/guides/federation/getting-started.md b/docs/guides/federation/getting-started.md index fb4c791..d148672 100644 --- a/docs/guides/federation/getting-started.md +++ b/docs/guides/federation/getting-started.md @@ -32,14 +32,14 @@ Here one key does everything a party signs. ## A node for each party Each node needs its node key, a user of its API, and its node ID, which the first -version names before the federation starts. A node makes its key with -`--node-key-create` and logs its ID before anything else (`Node identity`): start it so -once, with nothing of a swarm, and stop it. +version names before the federation starts. `continuum node-id` makes the key and says +the ID, without starting the node: ```sh +continuum node-id --create node.key +# a new node key in node.key: a new node +# continuum:5be1… printf '%s' 'secret' | argon2 "$(openssl rand -hex 16)" -id -e | sed 's/^/tv:/' > htpasswd -continuum --node-key-file node.key --node-key-create --htpasswd htpasswd --mycelium-enable -# INFO Created a new node key: this is a new node node_id=continuum:5be1… ``` ## The first version diff --git a/docs/lifecycle.md b/docs/lifecycle.md index 47cf051..a221063 100644 --- a/docs/lifecycle.md +++ b/docs/lifecycle.md @@ -45,7 +45,9 @@ What happens before the node talks to anyone, in order: 2. **The node key** (`--node-key-file`) and **the swarm key** (`--swarm-key-file`) are read, so a bad file fails at once. A missing key file is an error, unless `--node-key-create` asks for a new node key (a new node), or `--swarm-key-create` - for a new swarm key (on the swarm's first node; the others need a copy). + for a new swarm key (on the swarm's first node; the others need a copy). `continuum + node-id FILE` prints the node ID of the key `FILE` holds, without starting a node + (`--create` makes the key first, where there is none). 3. **The state file** (`--state-file`) is read: the swarm ID the node belongs to and members to reach it through. 4. **A document to start on**, if any: the document file (`--document-file`) or a -- cgit v1.3.1