From 0ddff4c21cb1d323c1d59bec8c3cf59253e31442 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Fran=C3=A7a?= Date: Thu, 12 Dec 2024 17:05:04 +0000 Subject: [PATCH] fmt --- docs/src/guides/advanced/16_decentralization.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/src/guides/advanced/16_decentralization.md b/docs/src/guides/advanced/16_decentralization.md index cd4c51699b89..ce7d0e219efb 100644 --- a/docs/src/guides/advanced/16_decentralization.md +++ b/docs/src/guides/advanced/16_decentralization.md @@ -34,7 +34,8 @@ If you are using the recommended file-based configuration then you'll need to ad ```yaml consensus: server_addr: '0.0.0.0:3054' - public_addr: '???' + public_addr: + '???' # Address under which the node is accessible to the other nodes. # It can be a public domain, like `example.com:3054`, in case the main node is accessible from the internet, # or it can be a kubernetes cluster domain, like `server-v2-core..svc.cluster.local:3054` in @@ -70,7 +71,8 @@ content: ```yaml server_addr: '0.0.0.0:3054' -public_addr: '???' +public_addr: + '???' # Address under which the node is accessible to the other nodes. # It can be a public domain, like `example.com:3054`, in case the main node is accessible from the internet, # or it can be a kubernetes cluster domain, like `server-v2-core..svc.cluster.local:3054` in @@ -86,8 +88,8 @@ genesis_spec: weight: 1 leader: validator:public:??? # same as above - main node will be the only validator and the only leader. seed_peers: - - key: 'node:public:ed25519:...' # node public key of the main node (copy this PUBLIC key from the secrets you generated) - addr: '???' # same as public_addr above + - key: 'node:public:ed25519:...' # node public key of the main node (copy this PUBLIC key from the secrets you generated) + addr: '???' # same as public_addr above ``` And a `consensus_secrets.yaml` file with the with the secrets you generated previously: