From e7717a889090e152a87e60b5466ff923e106dd97 Mon Sep 17 00:00:00 2001 From: troymc Date: Thu, 25 Aug 2016 20:53:39 +0200 Subject: [PATCH] docs: minor edit re/ status of Ansible playbook --- docs/source/prod-node-depl-tplt/start-one-m-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/prod-node-depl-tplt/start-one-m-node.md b/docs/source/prod-node-depl-tplt/start-one-m-node.md index fab89289..8b427d44 100644 --- a/docs/source/prod-node-depl-tplt/start-one-m-node.md +++ b/docs/source/prod-node-depl-tplt/start-one-m-node.md @@ -30,7 +30,7 @@ where `` should be replaced by the name of the SSH private key you cre What did you just do? Running that playbook ensures all the software necessary for a one-machine BigchainDB node is installed, configured, and running properly. You can run that playbook on a regular schedule to ensure that the system stays properly configured. If something is okay, it does nothing; it only takes action when something is not as-desired. -Note: At the time of writing, the playbook only installs, configures and runs an NTP daemon, but more is coming soon. +Note: At the time of writing (Aug. 25, 2016), the playbook isn't complete, so not all of the above happens yet. ## Optional: Create an Ansible Config File