Merge pull request #1520 from bigchaindb/redo-pr-1493

Redid PR #1493

docs/server/source/index.rst

@@ -9,7 +9,7 @@ BigchainDB Server Documentation
    quickstart
    production-nodes/index
    clusters-feds/index
-   cloud-deployment-templates/index
+   production-deployment-template/index
    dev-and-test/index
    server-reference/index
    http-client-server-api

docs/server/source/introduction.md

@@ -8,7 +8,7 @@ Note that there are a few kinds of nodes:
 
 - A **dev/test node** is a node created by a developer working on BigchainDB Server, e.g. for testing new or changed code. A dev/test node is typically run on the developer's local machine.
 
-- A **bare-bones node** is a node deployed in the cloud, either as part of a testing cluster or as a starting point before upgrading the node to be production-ready. Our cloud deployment templates deploy a bare-bones node, as do our scripts for deploying a testing cluster on AWS.
+- A **bare-bones node** is a node deployed in the cloud, either as part of a testing cluster or as a starting point before upgrading the node to be production-ready.
 
 - A **production node** is a node that is part of a consortium's BigchainDB cluster. A production node has the most components and requirements.
 
@@ -16,11 +16,15 @@ Note that there are a few kinds of nodes:
 ## Setup Instructions for Various Cases
 
 * [Set up a local stand-alone BigchainDB node for learning and experimenting: Quickstart](quickstart.html)
-* [Set up and run a bare-bones node in the cloud](cloud-deployment-templates/index.html)
 * [Set up and run a local dev/test node for developing and testing BigchainDB Server](dev-and-test/setup-run-node.html)
-* [Deploy a testing cluster on AWS](clusters-feds/aws-testing-cluster.html)
 * [Set up and run a cluster (including production nodes)](clusters-feds/set-up-a-cluster.html)
 
+There are some old RethinkDB-based deployment instructions as well:
+
+* [Deploy a bare-bones RethinkDB-based node on Azure](appendices/azure-quickstart-template.html)
+* [Deploy a bare-bones RethinkDB-based node on any Ubuntu machine with Ansible](appendices/template-ansible.html)
+* [Deploy a RethinkDB-based testing cluster on AWS](clusters-feds/aws-testing-cluster.html)
+
 Instructions for setting up a client will be provided once there's a public test net.
 
 

docs/server/source/production-nodes/node-assumptions.md

@@ -13,4 +13,4 @@ We make some assumptions about production nodes:
 
 You can use RethinkDB when building prototypes, but we don't advise or support using it in production.
 
-We don't provide a detailed cookbook explaining how to secure a server, or other things that a sysadmin should know. (We do provide some [templates](../cloud-deployment-templates/index.html), but those are just a starting point.)
+We don't provide a detailed cookbook explaining how to secure a server, or other things that a sysadmin should know. We do provide some templates, but those are just starting points.

docs/server/source/production-nodes/setup-run-node.md

@@ -2,7 +2,7 @@
 
 This is a page of general guidelines for setting up a production BigchainDB node. Before continuing, make sure you've read the pages about production node [assumptions](node-assumptions.html), [components](node-components.html) and [requirements](node-requirements.html).
 
-Note: These are just guidelines. You can modify them to suit your needs. For example, if you want to initialize the MongoDB replica set before installing BigchainDB, you _can_ do that. If you'd prefer to use Docker and Kubernetes, you can (and [we have a template](../cloud-deployment-templates/node-on-kubernetes.html)). We don't cover all possible setup procedures here.
+Note: These are just guidelines. You can modify them to suit your needs. For example, if you want to initialize the MongoDB replica set before installing BigchainDB, you _can_ do that. If you'd prefer to use Docker and Kubernetes, you can (and [we have a template](../production-deployment-template/index.html)). We don't cover all possible setup procedures here.
 
 
 ## Security Guidelines