mirror of
https://github.com/planetmint/planetmint.git
synced 2026-03-04 16:25:10 +00:00
Removing some more remnants of bigchaindb
This commit is contained in:
Sangat Das
@@ -10,7 +10,7 @@ Code is Apache-2.0 and docs are CC-BY-4.0
|
||||
For those who like using Docker and wish to experiment with Planetmint in
|
||||
non-production environments, we currently maintain a Planetmint all-in-one
|
||||
Docker image and a
|
||||
`Dockerfile-all-in-one` that can be used to build an image for `bigchaindb`.
|
||||
`Dockerfile-all-in-one` that can be used to build an image for `planetmint`.
|
||||
|
||||
This image contains all the services required for a Planetmint node i.e.
|
||||
|
||||
@@ -21,8 +21,8 @@ This image contains all the services required for a Planetmint node i.e.
|
||||
**Note:** **NOT for Production Use:** *This is an single node opinionated image not well suited for a network deployment.*
|
||||
*This image is to help quick deployment for early adopters, for a more standard approach please refer to one of our deployment guides:*
|
||||
|
||||
- [Planetmint developer setup guides](https://docs.bigchaindb.com/projects/contributing/en/latest/dev-setup-coding-and-contribution-process/index.html).
|
||||
- [Planetmint with Kubernetes](http://docs.bigchaindb.com/projects/server/en/latest/k8s-deployment-template/index.html).
|
||||
- [Planetmint developer setup guides](https://docs.planetmint.com/projects/contributing/en/latest/dev-setup-coding-and-contribution-process/index.html).
|
||||
- [Planetmint with Kubernetes](http://docs.planetmint.com/projects/server/en/latest/k8s-deployment-template/index.html).
|
||||
|
||||
## Prerequisite(s)
|
||||
- [Docker](https://docs.docker.com/engine/installation/)
|
||||
@@ -33,19 +33,19 @@ With Docker installed, you can proceed as follows.
|
||||
|
||||
In a terminal shell, pull the latest version of the Planetmint all-in-one Docker image using:
|
||||
```text
|
||||
$ docker pull bigchaindb/bigchaindb:all-in-one
|
||||
$ docker pull planetmint/planetmint:all-in-one
|
||||
|
||||
$ docker run \
|
||||
--detach \
|
||||
--name bigchaindb \
|
||||
--name planetmint \
|
||||
--publish 9984:9984 \
|
||||
--publish 9985:9985 \
|
||||
--publish 27017:27017 \
|
||||
--publish 26657:26657 \
|
||||
--volume $HOME/bigchaindb_docker/mongodb/data/db:/data/db \
|
||||
--volume $HOME/bigchaindb_docker/mongodb/data/configdb:/data/configdb \
|
||||
--volume $HOME/bigchaindb_docker/tendermint:/tendermint \
|
||||
bigchaindb/bigchaindb:all-in-one
|
||||
--volume $HOME/planetmint_docker/mongodb/data/db:/data/db \
|
||||
--volume $HOME/planetmint_docker/mongodb/data/configdb:/data/configdb \
|
||||
--volume $HOME/planetmint_docker/tendermint:/tendermint \
|
||||
planetmint/planetmint:all-in-one
|
||||
```
|
||||
|
||||
Let's analyze that command:
|
||||
@@ -57,18 +57,18 @@ Let's analyze that command:
|
||||
* `9985` Planetmint Websocket server
|
||||
* `27017` Default port for MongoDB
|
||||
* `26657` Tendermint RPC server
|
||||
* `--volume "$HOME/bigchaindb_docker/mongodb:/data"` map the host directory
|
||||
`$HOME/bigchaindb_docker/mongodb` to the container directory `/data`;
|
||||
* `--volume "$HOME/planetmint_docker/mongodb:/data"` map the host directory
|
||||
`$HOME/planetmint_docker/mongodb` to the container directory `/data`;
|
||||
this allows us to have the data persisted on the host machine,
|
||||
you can read more in the [official Docker
|
||||
documentation](https://docs.docker.com/engine/tutorials/dockervolumes)
|
||||
* `$HOME/bigchaindb_docker/tendermint:/tendermint` to persist Tendermint data.
|
||||
* `bigchaindb/bigchaindb:all-in-one` the image to use. All the options after the container name are passed on to the entrypoint inside the container.
|
||||
* `$HOME/planetmint_docker/tendermint:/tendermint` to persist Tendermint data.
|
||||
* `planetmint/planetmint:all-in-one` the image to use. All the options after the container name are passed on to the entrypoint inside the container.
|
||||
|
||||
## Verify
|
||||
|
||||
```text
|
||||
$ docker ps | grep bigchaindb
|
||||
$ docker ps | grep planetmint
|
||||
```
|
||||
|
||||
Send your first transaction using [Planetmint drivers](../../drivers/index).
|
||||
@@ -80,8 +80,8 @@ Assuming you have Docker installed, you would proceed as follows.
|
||||
|
||||
In a terminal shell:
|
||||
```text
|
||||
git clone git@github.com:bigchaindb/bigchaindb.git
|
||||
cd bigchaindb/
|
||||
git clone git@github.com:planetmint/planetmint.git
|
||||
cd planetmint/
|
||||
```
|
||||
|
||||
Build the Docker image:
|
||||
|
||||
@@ -7,20 +7,20 @@ Code is Apache-2.0 and docs are CC-BY-4.0
|
||||
|
||||
# Command Line Interface (CLI)
|
||||
|
||||
The command-line command to interact with Planetmint Server is `bigchaindb`.
|
||||
The command-line command to interact with Planetmint Server is `planetmint`.
|
||||
|
||||
|
||||
## bigchaindb \-\-help
|
||||
## planetmint \-\-help
|
||||
|
||||
Show help for the `bigchaindb` command. `bigchaindb -h` does the same thing.
|
||||
Show help for the `planetmint` command. `planetmint -h` does the same thing.
|
||||
|
||||
|
||||
## bigchaindb \-\-version
|
||||
## planetmint \-\-version
|
||||
|
||||
Show the version number. `bigchaindb -v` does the same thing.
|
||||
Show the version number. `planetmint -v` does the same thing.
|
||||
|
||||
|
||||
## bigchaindb configure
|
||||
## planetmint configure
|
||||
|
||||
Generate a local configuration file (which can be used to set some or all [Planetmint node configuration settings](configuration)). It will ask you for the values of some configuration settings.
|
||||
If you press Enter for a value, it will use the default value.
|
||||
@@ -29,39 +29,39 @@ At this point, only one database backend is supported: `localmongodb`.
|
||||
|
||||
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 localmongodb
|
||||
planetmint -c path/to/new_config.json configure localmongodb
|
||||
```
|
||||
|
||||
If you don't use the `-c` command-line option, the file will be written to `$HOME/.bigchaindb` (the default location where Planetmint looks for a config file, if one isn't specified).
|
||||
If you don't use the `-c` command-line option, the file will be written to `$HOME/.planetmint` (the default location where Planetmint 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 use the default values for all the configuration settings.
|
||||
```text
|
||||
bigchaindb -y configure localmongodb
|
||||
planetmint -y configure localmongodb
|
||||
```
|
||||
|
||||
|
||||
## bigchaindb show-config
|
||||
## planetmint show-config
|
||||
|
||||
Show the values of the [Planetmint node configuration settings](configuration).
|
||||
|
||||
|
||||
## bigchaindb init
|
||||
## planetmint init
|
||||
|
||||
Create a backend database (local MongoDB), all database tables/collections,
|
||||
various backend database indexes, and the genesis block.
|
||||
|
||||
|
||||
## bigchaindb drop
|
||||
## planetmint drop
|
||||
|
||||
Drop (erase) the backend database (the local MongoDB database used by this node).
|
||||
You will be prompted to make sure.
|
||||
If you want to force-drop the database (i.e. skipping the yes/no prompt), then use `bigchaindb -y drop`
|
||||
If you want to force-drop the database (i.e. skipping the yes/no prompt), then use `planetmint -y drop`
|
||||
|
||||
|
||||
## bigchaindb start
|
||||
## planetmint start
|
||||
|
||||
Start Planetmint. It always begins by trying a `bigchaindb init` first. See the documentation for `bigchaindb init`.
|
||||
The database initialization step is optional and can be skipped by passing the `--no-init` flag, i.e. `bigchaindb start --no-init`.
|
||||
Start Planetmint. It always begins by trying a `planetmint init` first. See the documentation for `planetmint init`.
|
||||
The database initialization step is optional and can be skipped by passing the `--no-init` flag, i.e. `planetmint start --no-init`.
|
||||
|
||||
### Options
|
||||
|
||||
@@ -69,7 +69,7 @@ The log level for the console can be set via the option `--log-level` or its
|
||||
abbreviation `-l`. Example:
|
||||
|
||||
```bash
|
||||
$ bigchaindb --log-level INFO start
|
||||
$ planetmint --log-level INFO start
|
||||
```
|
||||
|
||||
The allowed levels are `DEBUG`, `INFO`, `WARNING`, `ERROR`, and `CRITICAL`.
|
||||
@@ -82,9 +82,9 @@ configuration file as documented under
|
||||
[Configuration Settings](configuration).
|
||||
|
||||
|
||||
## bigchaindb election
|
||||
## planetmint election
|
||||
|
||||
Manage elections to govern the Planetmint network. The specifics of the election process are defined in [BEP-18](https://github.com/bigchaindb/BEPs/tree/master/18).
|
||||
Manage elections to govern the Planetmint network. The specifics of the election process are defined in [BEP-18](https://github.com/planetmint/BEPs/tree/master/18).
|
||||
|
||||
Election management is broken into several subcommands. Below is the command line syntax for each of them.
|
||||
|
||||
@@ -106,7 +106,7 @@ Create an election to add, update, or remove a validator.
|
||||
|
||||
|
||||
```bash
|
||||
$ bigchaindb election new upsert-validator <public-key> <power> <node-id> --private-key <path-to-the-private-key>
|
||||
$ planetmint election new upsert-validator <public-key> <power> <node-id> --private-key <path-to-the-private-key>
|
||||
```
|
||||
|
||||
- `<public-key>` is the public key of the node to be added/updated/removed. The encoding and type of the key have to match those specified in `genesis.json` in the supported Tendermint version.
|
||||
@@ -117,7 +117,7 @@ $ bigchaindb election new upsert-validator <public-key> <power> <node-id> --priv
|
||||
Example:
|
||||
|
||||
```bash
|
||||
$ bigchaindb election new upsert-validator HHG0IQRybpT6nJMIWWFWhMczCLHt6xcm7eP52GnGuPY= 1 fb7140f03a4ffad899fabbbf655b97e0321add66 --private-key /home/user/.tendermint/config/priv_validator.json
|
||||
$ planetmint election new upsert-validator HHG0IQRybpT6nJMIWWFWhMczCLHt6xcm7eP52GnGuPY= 1 fb7140f03a4ffad899fabbbf655b97e0321add66 --private-key /home/user/.tendermint/config/priv_validator.json
|
||||
[SUCCESS] Submitted proposal with id: 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa
|
||||
```
|
||||
|
||||
@@ -126,7 +126,7 @@ Once `election_id` has been generated, the proposer should share it with other v
|
||||
|
||||
Note that election proposers do not automatically approve elections by proposing them.
|
||||
|
||||
For more details about how validator set changes work, refer to [BEP-21](https://github.com/bigchaindb/BEPs/tree/master/21).
|
||||
For more details about how validator set changes work, refer to [BEP-21](https://github.com/planetmint/BEPs/tree/master/21).
|
||||
|
||||
#### election new chain-migration
|
||||
|
||||
@@ -134,7 +134,7 @@ Create an election to halt block production, to coordinate on making a Tendermin
|
||||
|
||||
|
||||
```bash
|
||||
$ bigchaindb election new chain-migration --private-key <path-to-the-private-key>
|
||||
$ planetmint election new chain-migration --private-key <path-to-the-private-key>
|
||||
```
|
||||
|
||||
- `<path-to-the-private-key>` is the path to the private key of the validator who proposes the election. Tendermint places it at `.tendermint/config/priv_validator.json`.
|
||||
@@ -143,7 +143,7 @@ $ bigchaindb election new chain-migration --private-key <path-to-the-private-key
|
||||
Example:
|
||||
|
||||
```bash
|
||||
$ bigchaindb election new migration --private-key /home/user/.tendermint/config/priv_validator.json
|
||||
$ planetmint election new migration --private-key /home/user/.tendermint/config/priv_validator.json
|
||||
[SUCCESS] Submitted proposal with id: 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa
|
||||
```
|
||||
|
||||
@@ -151,7 +151,7 @@ Concluded chain migration elections halt block production at whichever block hei
|
||||
Afterwards, validators are supposed to upgrade Tendermint, set new `chain_id`, `app_hash`, and `validators` (to learn these values, use the [election show](#election-show) command) in `genesis.json`, make and save a MongoDB dump, and restart the system.
|
||||
|
||||
|
||||
For more details about how chain migrations work, refer to [Type 3 scenarios in BEP-42](https://github.com/bigchaindb/BEPs/tree/master/42).
|
||||
For more details about how chain migrations work, refer to [Type 3 scenarios in BEP-42](https://github.com/planetmint/BEPs/tree/master/42).
|
||||
|
||||
### election approve
|
||||
|
||||
@@ -159,7 +159,7 @@ Approve an election by voting for it. The command places a `VOTE` transaction, s
|
||||
|
||||
|
||||
```bash
|
||||
$ bigchaindb election approve <election-id> --private-key <path-to-the-private-key>
|
||||
$ planetmint election approve <election-id> --private-key <path-to-the-private-key>
|
||||
```
|
||||
|
||||
- `election-id` is the election identifier the approval is given for.
|
||||
@@ -167,7 +167,7 @@ $ bigchaindb election approve <election-id> --private-key <path-to-the-private-k
|
||||
|
||||
Example:
|
||||
```bash
|
||||
$ bigchaindb election approve 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa --private-key /home/user/.tendermint/config/priv_validator.json
|
||||
$ planetmint election approve 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa --private-key /home/user/.tendermint/config/priv_validator.json
|
||||
[SUCCESS] Your vote has been submitted
|
||||
```
|
||||
|
||||
@@ -179,7 +179,7 @@ Retrieves the information about elections.
|
||||
|
||||
|
||||
```bash
|
||||
$ bigchaindb election show <election-id>
|
||||
$ planetmint election show <election-id>
|
||||
|
||||
status=<status>
|
||||
```
|
||||
@@ -192,11 +192,11 @@ status=<status>
|
||||
|
||||
After a chain migration is concluded, the `show` command also outputs `chain_id`, `app_hash`, and `validators` for `genesis.json` of the new chain.
|
||||
|
||||
## bigchaindb tendermint-version
|
||||
## planetmint tendermint-version
|
||||
|
||||
Show the Tendermint versions supported by Planetmint server.
|
||||
```bash
|
||||
$ bigchaindb tendermint-version
|
||||
$ planetmint tendermint-version
|
||||
{
|
||||
"description": "Planetmint supports the following Tendermint version(s)",
|
||||
"tendermint": [
|
||||
|
||||
@@ -2,6 +2,6 @@
|
||||
|
||||
You can find one of the installation methods with Ansible on GitHub at:
|
||||
|
||||
[Ansible script](https://github.com/bigchaindb/bigchaindb-node-ansible)
|
||||
[Ansible script](https://github.com/planetmint/planetmint-node-ansible)
|
||||
|
||||
It allows to install Planetmint, MongoDB, Tendermint, and python, and then connect nodes into a network. Current tested machine is Ubuntu 18.04.
|
||||
@@ -21,13 +21,13 @@ The value of each setting is determined according to the following rules:
|
||||
* Otherwise, if it's set in a local config file, then use that value
|
||||
* Otherwise, use the default value
|
||||
|
||||
The local config file is `$HOME/.bigchaindb` by default (a file which might not even exist), but you can tell Planetmint to use a different file by using the `-c` command-line option, e.g. `bigchaindb -c path/to/config_file.json start`
|
||||
or using the `PLANETMINT_CONFIG_PATH` environment variable, e.g. `BIGHAINDB_CONFIG_PATH=.my_bigchaindb_config bigchaindb start`.
|
||||
The local config file is `$HOME/.planetmint` by default (a file which might not even exist), but you can tell Planetmint to use a different file by using the `-c` command-line option, e.g. `planetmint -c path/to/config_file.json start`
|
||||
or using the `PLANETMINT_CONFIG_PATH` environment variable, e.g. `BIGHAINDB_CONFIG_PATH=.my_planetmint_config planetmint start`.
|
||||
Note that the `-c` command line option will always take precedence if both the `PLANETMINT_CONFIG_PATH` and the `-c` command line option are used.
|
||||
|
||||
You can read the current default values in the file [bigchaindb/\_\_init\_\_.py](https://github.com/bigchaindb/bigchaindb/blob/master/bigchaindb/__init__.py). (The link is to the latest version.)
|
||||
You can read the current default values in the file [planetmint/\_\_init\_\_.py](https://github.com/planetmint/planetmint/blob/master/planetmint/__init__.py). (The link is to the latest version.)
|
||||
|
||||
Running `bigchaindb -y configure localmongodb` will generate a local config file in `$HOME/.bigchaindb` with all the default values.
|
||||
Running `planetmint -y configure localmongodb` will generate a local config file in `$HOME/.planetmint` with all the default values.
|
||||
|
||||
## database.*
|
||||
|
||||
@@ -84,7 +84,7 @@ export PLANETMINT_DATABASE_MAX_TRIES=3
|
||||
|
||||
**Default values**
|
||||
|
||||
If (no environment variables were set and there's no local config file), or you used `bigchaindb -y configure localmongodb` to create a default local config file for a `localmongodb` backend, then the defaults will be:
|
||||
If (no environment variables were set and there's no local config file), or you used `planetmint -y configure localmongodb` to create a default local config file for a `localmongodb` backend, then the defaults will be:
|
||||
|
||||
```js
|
||||
"database": {
|
||||
@@ -213,7 +213,7 @@ different from where Planetmint is running.
|
||||
|
||||
```text
|
||||
export PLANETMINT_WSSERVER_ADVERTISED_SCHEME=wss
|
||||
export PLANETMINT_WSSERVER_ADVERTISED_HOST=mybigchaindb.com
|
||||
export PLANETMINT_WSSERVER_ADVERTISED_HOST=myplanetmint.com
|
||||
export PLANETMINT_WSSERVER_ADVERTISED_PORT=443
|
||||
```
|
||||
|
||||
@@ -222,7 +222,7 @@ export PLANETMINT_WSSERVER_ADVERTISED_PORT=443
|
||||
```js
|
||||
"wsserver": {
|
||||
"advertised_scheme": "wss",
|
||||
"advertised_host": "mybigchaindb.com",
|
||||
"advertised_host": "myplanetmint.com",
|
||||
"advertised_port": 443
|
||||
}
|
||||
```
|
||||
@@ -246,8 +246,8 @@ The `log.*` settings are to configure logging.
|
||||
```js
|
||||
{
|
||||
"log": {
|
||||
"file": "/var/log/bigchaindb.log",
|
||||
"error_file": "/var/log/bigchaindb-errors.log",
|
||||
"file": "/var/log/planetmint.log",
|
||||
"error_file": "/var/log/planetmint-errors.log",
|
||||
"level_console": "info",
|
||||
"level_logfile": "info",
|
||||
"datefmt_console": "%Y-%m-%d %H:%M:%S",
|
||||
@@ -263,8 +263,8 @@ The `log.*` settings are to configure logging.
|
||||
```js
|
||||
{
|
||||
"log": {
|
||||
"file": "~/bigchaindb.log",
|
||||
"error_file": "~/bigchaindb-errors.log",
|
||||
"file": "~/planetmint.log",
|
||||
"error_file": "~/planetmint-errors.log",
|
||||
"level_console": "info",
|
||||
"level_logfile": "info",
|
||||
"datefmt_console": "%Y-%m-%d %H:%M:%S",
|
||||
@@ -278,7 +278,7 @@ The `log.*` settings are to configure logging.
|
||||
### log.file
|
||||
|
||||
The full path to the file where logs should be written.
|
||||
The user running `bigchaindb` must have write access to the
|
||||
The user running `planetmint` must have write access to the
|
||||
specified path.
|
||||
|
||||
**Log rotation:** Log files have a size limit of about 200 MB
|
||||
|
||||
@@ -14,12 +14,12 @@ You can use the all-in-one docker solution, or install Tendermint, MongoDB, and
|
||||
|
||||
deploy-a-machine
|
||||
aws-setup
|
||||
all-in-one-bigchaindb
|
||||
bigchaindb-node-ansible
|
||||
all-in-one-planetmint
|
||||
planetmint-node-ansible
|
||||
set-up-node-software
|
||||
set-up-nginx
|
||||
configuration
|
||||
bigchaindb-cli
|
||||
planetmint-cli
|
||||
troubleshooting
|
||||
production-node/index
|
||||
release-notes
|
||||
|
||||
@@ -9,7 +9,7 @@ Code is Apache-2.0 and docs are CC-BY-4.0
|
||||
|
||||
Be sure you know the key Planetmint terminology:
|
||||
|
||||
* [Planetmint node, Planetmint network and Planetmint consortium](https://docs.bigchaindb.com/en/latest/terminology.html)
|
||||
* [Planetmint node, Planetmint network and Planetmint consortium](https://docs.planetmint.com/en/latest/terminology.html)
|
||||
|
||||
Note that there are a few kinds of nodes:
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ Below, we note how a reverse proxy can be used
|
||||
to do some Planetmint-specific things.
|
||||
|
||||
You may also be interested in
|
||||
[our NGINX configuration file template](https://github.com/bigchaindb/nginx_3scale/blob/master/nginx.conf.template)
|
||||
[our NGINX configuration file template](https://github.com/planetmint/nginx_3scale/blob/master/nginx.conf.template)
|
||||
(open source, on GitHub).
|
||||
|
||||
|
||||
@@ -55,4 +55,4 @@ For more information, see
|
||||
[the NGINX docs about client_max_body_size](https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size).
|
||||
|
||||
Note: By enforcing a maximum transaction size, you
|
||||
[indirectly enforce a maximum crypto-conditions complexity](https://github.com/bigchaindb/bigchaindb/issues/356#issuecomment-288085251).
|
||||
[indirectly enforce a maximum crypto-conditions complexity](https://github.com/planetmint/planetmint/issues/356#issuecomment-288085251).
|
||||
|
||||
@@ -9,8 +9,8 @@ Code is Apache-2.0 and docs are CC-BY-4.0
|
||||
|
||||
You can find a list of all Planetmint Server releases and release notes on GitHub at:
|
||||
|
||||
[https://github.com/bigchaindb/bigchaindb/releases](https://github.com/bigchaindb/bigchaindb/releases)
|
||||
[https://github.com/planetmint/planetmint/releases](https://github.com/planetmint/planetmint/releases)
|
||||
|
||||
The [CHANGELOG.md file](https://github.com/bigchaindb/bigchaindb/blob/master/CHANGELOG.md) contains much the same information, but it also has notes about what to expect in the _next_ release.
|
||||
The [CHANGELOG.md file](https://github.com/planetmint/planetmint/blob/master/CHANGELOG.md) contains much the same information, but it also has notes about what to expect in the _next_ release.
|
||||
|
||||
We also have [a roadmap document in ROADMAP.md](https://github.com/bigchaindb/org/blob/master/ROADMAP.md).
|
||||
We also have [a roadmap document in ROADMAP.md](https://github.com/planetmint/org/blob/master/ROADMAP.md).
|
||||
|
||||
@@ -31,7 +31,7 @@ Get an SSL certificate for your node's subdomain (such as `bnode.example.com`).
|
||||
* Create a "PEM file" (text file) by concatenating your SSL certificate with all intermediate certificates (_in that order, with the intermediate certs last_).
|
||||
* Copy that PEM file into `/etc/nginx/ssl/cert.pem`
|
||||
* In the
|
||||
[bigchaindb/bigchaindb repository on GitHub](https://github.com/bigchaindb/bigchaindb),
|
||||
[planetmint/planetmint repository on GitHub](https://github.com/planetmint/planetmint),
|
||||
find the file `nginx/nginx.conf` and copy its contents to
|
||||
`/etc/nginx/nginx.conf` on your machine (i.e. replace the existing file there).
|
||||
* Edit that file (`/etc/nginx/nginx.conf`): replace the two instances of
|
||||
|
||||
@@ -36,17 +36,17 @@ For example, to install version 2.2.2, you would do:
|
||||
|
||||
```
|
||||
# Change 2.0.0 to the latest version as explained above:
|
||||
sudo pip3 install bigchaindb==2.2.2
|
||||
sudo pip3 install planetmint==2.2.2
|
||||
```
|
||||
|
||||
Check that you installed the correct version of Planetmint Server using `bigchaindb --version`.
|
||||
Check that you installed the correct version of Planetmint Server using `planetmint --version`.
|
||||
|
||||
## Configure Planetmint Server
|
||||
|
||||
To configure Planetmint Server, run:
|
||||
|
||||
```
|
||||
bigchaindb configure
|
||||
planetmint configure
|
||||
```
|
||||
|
||||
The first question is ``API Server bind? (default `localhost:9984`)``.
|
||||
@@ -58,7 +58,7 @@ The first question is ``API Server bind? (default `localhost:9984`)``.
|
||||
You can accept the default value for all other Planetmint config settings.
|
||||
|
||||
If you're using NGINX, then you should edit your Planetmint config file
|
||||
(in `$HOME/.bigchaindb` by default) and set the following values
|
||||
(in `$HOME/.planetmint` by default) and set the following values
|
||||
under `"wsserver"`:
|
||||
|
||||
```
|
||||
|
||||
@@ -36,7 +36,7 @@ addr_book_strict = false
|
||||
|
||||
If you want to refresh your node back to a fresh empty state, then your best bet is to terminate it and deploy a new machine, but if that's not an option, then you can:
|
||||
|
||||
* drop the `bigchain` database in MongoDB using `bigchaindb drop` (but that only works if MongoDB is running)
|
||||
* drop the `bigchain` database in MongoDB using `planetmint drop` (but that only works if MongoDB is running)
|
||||
* reset Tendermint using `tendermint unsafe_reset_all`
|
||||
* delete the directory `$HOME/.tendermint`
|
||||
|
||||
@@ -46,45 +46,45 @@ If you want to stop/kill Planetmint, you can do so by sending `SIGINT`, `SIGQUIT
|
||||
process(es). Depending on how you started Planetmint i.e. foreground or background. e.g. you started Planetmint in the background as mentioned above in the guide:
|
||||
|
||||
```bash
|
||||
$ nohup bigchaindb start 2>&1 > bigchaindb.log &
|
||||
$ nohup planetmint start 2>&1 > planetmint.log &
|
||||
|
||||
$ # Check the PID of the main Planetmint process
|
||||
$ ps -ef | grep bigchaindb
|
||||
<user> *<pid> <ppid> <C> <STIME> <tty> <time> bigchaindb
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> gunicorn: master [bigchaindb_gunicorn]
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> bigchaindb_ws
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> bigchaindb_ws_to_tendermint
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> bigchaindb_exchange
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [bigchaindb_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [bigchaindb_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [bigchaindb_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [bigchaindb_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [bigchaindb_gunicorn]
|
||||
$ ps -ef | grep planetmint
|
||||
<user> *<pid> <ppid> <C> <STIME> <tty> <time> planetmint
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> gunicorn: master [planetmint_gunicorn]
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> planetmint_ws
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> planetmint_ws_to_tendermint
|
||||
<user> <pid> <ppid>* <C> <STIME> <tty> <time> planetmint_exchange
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [planetmint_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [planetmint_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [planetmint_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [planetmint_gunicorn]
|
||||
<user> <pid> <ppid> <C> <STIME> <tty> <time> gunicorn: worker [planetmint_gunicorn]
|
||||
...
|
||||
|
||||
$ # Send any of the above mentioned signals to the parent/root process(marked with `*` for clarity)
|
||||
# Sending SIGINT
|
||||
$ kill -2 <bigchaindb_parent_pid>
|
||||
$ kill -2 <planetmint_parent_pid>
|
||||
|
||||
$ # OR
|
||||
|
||||
# Sending SIGTERM
|
||||
$ kill -15 <bigchaindb_parent_pid>
|
||||
$ kill -15 <planetmint_parent_pid>
|
||||
|
||||
$ # OR
|
||||
|
||||
# Sending SIGQUIT
|
||||
$ kill -3 <bigchaindb_parent_pid>
|
||||
$ kill -3 <planetmint_parent_pid>
|
||||
|
||||
# If you want to kill all the processes by name yourself
|
||||
$ pgrep bigchaindb | xargs kill -9
|
||||
$ pgrep planetmint | xargs kill -9
|
||||
```
|
||||
|
||||
If you started Planetmint in the foreground, a `Ctrl + C` or `Ctrl + Z` would shut down Planetmint.
|
||||
|
||||
## Member: Dynamically Add or Remove Validators
|
||||
|
||||
One member can make a proposal to call an election to add a validator, remove a validator, or change the voting power of a validator. They then share the election/proposal ID with all the other members. Once more than 2/3 of the voting power votes yes, the proposed change comes into effect. The commands to create a new election/proposal, to approve an election/proposal, and to get the current status of an election/proposal can be found in the documentation about the [bigchaindb election](../server-reference/bigchaindb-cli#bigchaindb-election) subcommands.
|
||||
One member can make a proposal to call an election to add a validator, remove a validator, or change the voting power of a validator. They then share the election/proposal ID with all the other members. Once more than 2/3 of the voting power votes yes, the proposed change comes into effect. The commands to create a new election/proposal, to approve an election/proposal, and to get the current status of an election/proposal can be found in the documentation about the [planetmint election](../server-reference/planetmint-cli#planetmint-election) subcommands.
|
||||
|
||||
## Logging
|
||||
|
||||
@@ -92,4 +92,4 @@ See the page in the Appendices about [logging and log rotation](../appendices/lo
|
||||
|
||||
## Other Problems
|
||||
|
||||
If you're stuck, maybe [file a new issue on GitHub](https://github.com/bigchaindb/bigchaindb/issues/new). If your problem occurs often enough, we'll write about it here.
|
||||
If you're stuck, maybe [file a new issue on GitHub](https://github.com/planetmint/planetmint/issues/new). If your problem occurs often enough, we'll write about it here.
|
||||
Reference in New Issue
Block a user