mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
Document how to run BigchainDB with MongoDB (#1116)
* Document changes in the configure command. Document new add/remove replicas commands. * updated quickstart with mongodb instructions * Docs on how to setup mongodb dev node with and without docker. Update replSet option in docker-compose * Fixed typo. More explicit on how to run the tests. * Fixed typo in mongodb docker instructions. More explicit about requiring mongodb 3.4+
This commit is contained in:
@@ -15,18 +15,22 @@ Show the version number. `bigchaindb -v` does the same thing.
|
||||
|
||||
## bigchaindb configure
|
||||
|
||||
Generate a local config file (which can be used to set some or all [BigchainDB node configuration settings](configuration.html)). It will auto-generate a public-private keypair and then ask you for the values of other configuration settings. If you press Enter for a value, it will use the default value.
|
||||
Generate a local configuration file (which can be used to set some or all [BigchainDB node configuration settings](configuration.html)). It will auto-generate a public-private keypair and then ask you for the values of other configuration settings. If you press Enter for a value, it will use the default value.
|
||||
|
||||
Since BigchainDB supports multiple databases you need to always specify the
|
||||
database backend that you want to use. At this point only two database backends
|
||||
are supported: `rethinkdb` and `mongodb`.
|
||||
|
||||
If you use the `-c` command-line option, it will generate the file at the specified path:
|
||||
```text
|
||||
bigchaindb -c path/to/new_config.json configure
|
||||
bigchaindb -c path/to/new_config.json configure rethinkdb
|
||||
```
|
||||
|
||||
If you don't use the `-c` command-line option, the file will be written to `$HOME/.bigchaindb` (the default location where BigchainDB looks for a config file, if one isn't specified).
|
||||
|
||||
If you use the `-y` command-line option, then there won't be any interactive prompts: it will just generate a keypair and use the default values for all the other configuration settings.
|
||||
```text
|
||||
bigchaindb -y configure
|
||||
bigchaindb -y configure rethinkdb
|
||||
```
|
||||
|
||||
|
||||
@@ -83,3 +87,25 @@ Set the number of replicas (of each shard) in the underlying datastore. For exam
|
||||
```text
|
||||
$ bigchaindb set-replicas 3
|
||||
```
|
||||
|
||||
## bigchaindb add-replicas
|
||||
|
||||
This command is specific to MongoDB so it will only run if BigchainDB is
|
||||
configured with `mongodb` as the backend.
|
||||
|
||||
This command is used to add nodes to a BigchainDB cluster. It accepts a list of
|
||||
space separated hosts in the form _hostname:port_:
|
||||
```text
|
||||
$ bigchaindb add-replicas server1.com:27017 server2.com:27017 server3.com:27017
|
||||
```
|
||||
|
||||
## bigchaindb remove-replicas
|
||||
|
||||
This command is specific to MongoDB so it will only run if BigchainDB is
|
||||
configured with `mongodb` as the backend.
|
||||
|
||||
This command is used to remove nodes from a BigchainDB cluster. It accepts a
|
||||
list of space separated hosts in the form _hostname:port_:
|
||||
```text
|
||||
$ bigchaindb remove-replicas server1.com:27017 server2.com:27017 server3.com:27017
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user