diff options
| author | tv <tv@krebsco.de> | 2026-11-19 19:00:05 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 20:13:16 +0100 |
| commit | c66f0f8f7297484e095e02d259c84469b6c42367 (patch) | |
| tree | bb12683c006ef734689deb0fbe7bad40edc04dc8 /docs/lifecycle.md | |
| parent | 2a8575ce6562e1579f9c9bd9c9964e3ef36d08f1 (diff) | |
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.
Diffstat (limited to 'docs/lifecycle.md')
| -rw-r--r-- | docs/lifecycle.md | 4 |
1 files changed, 3 insertions, 1 deletions
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 |
