Updated docs

This commit is contained in:
kansi 2017-10-24 18:29:31 +05:30
parent 199473178f
commit cf19a8cb93
4 changed files with 5 additions and 7 deletions

View File

@ -33,7 +33,7 @@ API Server bind? (default `localhost:9984`): 0.0.0.0:9984
Finally, run BigchainDB Server by doing:
```text
bigchaindb start
bigchaindb start --init
```
BigchainDB Server should now be running on the Azure virtual machine.

View File

@ -27,7 +27,7 @@ waiting for connections on port 27017
To run BigchainDB Server, do:
```text
$ bigchaindb start
$ bigchaindb start --init
```
You can [run all the unit tests](running-all-tests.html) to test your installation.
@ -55,7 +55,7 @@ You can verify that RethinkDB is running by opening the RethinkDB web interface
To run BigchainDB Server, do:
```text
$ bigchaindb start
$ bigchaindb start --init
```
You can [run all the unit tests](running-all-tests.html) to test your installation.

View File

@ -54,7 +54,7 @@ $ bigchaindb -y configure mongodb
I. Run BigchainDB Server:
```text
$ bigchaindb start
$ bigchaindb start --init
```
J. Verify BigchainDB Server setup by visiting the BigchainDB Root URL in your browser:

View File

@ -51,8 +51,6 @@ all database tables/collections,
various backend database indexes,
and the genesis block.
Note: The `bigchaindb start` command (see below) always starts by trying a `bigchaindb init` first. If it sees that the backend database already exists, then it doesn't re-initialize the database. One doesn't have to do `bigchaindb init` before `bigchaindb start`. `bigchaindb init` is useful if you only want to initialize (but not start).
## bigchaindb drop
@ -63,7 +61,7 @@ If you want to force-drop the database (i.e. skipping the yes/no prompt), then u
## bigchaindb start
Start BigchainDB. It always begins by trying a `bigchaindb init` first. See the note in the documentation for `bigchaindb init`.
Start BigchainDB assuming that the database has already been initialized using `bigchaindb init`. If that is not the case then passing the flag `--init` will initialize the database and start BigchainDB.
You can also use the `--dev-start-rethinkdb` command line option to automatically start rethinkdb with bigchaindb if rethinkdb is not already running,
e.g. `bigchaindb --dev-start-rethinkdb start`. Note that this will also shutdown rethinkdb when the bigchaindb process stops.
The option `--dev-allow-temp-keypair` will generate a keypair on the fly if no keypair is found, this is useful when you want to run a temporary instance of BigchainDB in a Docker container, for example.