Change server port to 9984

docs/source/bigchaindb-cli.md

@@ -90,4 +90,7 @@ environ variable you need to use colon (`:`) as separator.
 - BIGCHAINDB_STATSD_RATE
 - BIGCHAINDB_API_ENDPOINT
 - BIGCHAINDB_CONSENSUS_PLUGIN
+- BIGCHAINDB_SERVER_BIND
+- BIGCHAINDB_SERVER_WORKERS
+- BIGCHAINDB_SERVER_THREADS
 ```

docs/source/http-client-server-api.md

@@ -2,10 +2,15 @@
 
 When you start Bigchaindb using `bigchaindb start`, an HTTP API is exposed at:
 
-[http://localhost:5000/api/v1/](http://localhost:5000/api/v1/)
+- [http://localhost:9984/api/v1/](http://localhost:9984/api/v1/)
 
-Right now, that API can only be accessed from localhost (i.e. not remotely). In the future, we'll enable remote access and explain how that works. See [Issue #149](https://github.com/bigchaindb/bigchaindb/issues/149) on GitHub.
 
-The HTTP API currently exposes two endpoints, one to get information about a specific transaction id, and one to push a transaction to the BigchainDB cluster. Those endpoints are documented at:
+Please note that by default the server binds to `0.0.0.0:9984`, hence the API
+is exposed to the world.
+
+The HTTP API currently exposes two endpoints, one to get information about a
+specific transaction id, and one to push a transaction to the BigchainDB
+cluster. Those endpoints are documented at:
+
+- [http://docs.bigchaindb.apiary.io/](http://docs.bigchaindb.apiary.io/)
 
-[http://docs.bigchaindb.apiary.io/](http://docs.bigchaindb.apiary.io/)

docs/source/installing-server.md

@@ -94,10 +94,16 @@ $ rethinkdb
 
 Then open a different terminal and run:
 ```text
-$ bigchaindb start
+$ bigchaindb init
 ```
 
-During its first run, BigchainDB Server takes care of configuring a single node environment.
+During its first run, the command takes care of configuring a single node environment.
+
+
+After configuring the node, you can start it with:
+```text
+$ bigchaindb start
+```
 
 
 ## Run BigchainDB with Docker