From 2cd796349c36069ddad5bfd69570ab6130bdf9ae Mon Sep 17 00:00:00 2001 From: troymc Date: Mon, 8 Aug 2016 18:28:31 +0200 Subject: [PATCH] docs: bolierplate for prod node setup & mgmt section --- docs/source/clusters-feds/set-up-a-federation.md | 5 +++-- docs/source/index.rst | 1 + 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/source/clusters-feds/set-up-a-federation.md b/docs/source/clusters-feds/set-up-a-federation.md index c139eb4a..401fae43 100644 --- a/docs/source/clusters-feds/set-up-a-federation.md +++ b/docs/source/clusters-feds/set-up-a-federation.md @@ -19,8 +19,9 @@ The federation must decide some things before setting up the initial cluster (in 2. What will the replication factor be? (It must be 3 or more for [RethinkDB failover](https://rethinkdb.com/docs/failover/) to work.) 3. Which node will be responsible for sending the commands to configure the RethinkDB database? -Once those things have been decided, each node operator can begin setting up their BigchainDB node. -The steps to set up a cluster node are outlined in the section titled [Set Up and Run a Node](../dev-and-test/setup-run-node.html). Each node operator will eventually need two pieces of information from all other nodes in the federation: +Once those things have been decided, each node operator can begin [setting up their BigchainDB (production) node](../prod-node-setup-mgmt/index.html). + +Each node operator will eventually need two pieces of information from all other nodes in the federation: 1. Their RethinkDB hostname, e.g. `rdb.farm2.organization.org` 2. Their BigchainDB public key, e.g. `Eky3nkbxDTMgkmiJC8i5hKyVFiAQNmPP4a2G4JdDxJCK` diff --git a/docs/source/index.rst b/docs/source/index.rst index c90bd9a8..df70a80b 100644 --- a/docs/source/index.rst +++ b/docs/source/index.rst @@ -12,6 +12,7 @@ Table of Contents node-cluster-fed nodes/index dev-and-test/index + prod-node-setup-mgmt/index server-reference/index drivers-clients/index clusters-feds/index