* Problem: it's difficult to run/test/compile docs
Solution: we already have a nice Makefile, but it's outdated. The idea
is to revamp it and make it easy to use.
* Problem: Makefile is not documented
Solution: Add basic instructions on how to use it in the main README.md
* Problem: can't connect to localhost:9984
Solution: make docker expose 9984 by default, so everyone can connect to
localhost:9984.
* Problem: make clean is TMI
Solution: add `@` to remove commands so we don't output all the details
about the cleaning
* Problem: make clean is too shy
Solution: print a message saying that cleaning went well.
* Update setup.py for BigchainDB 2.0
I took the license name from this list of valid PyPI licenses:
https://jlesquembre.github.io/autopilot/license_list.html
* Remove 'Programming Language :: Python :: 3.6'
from `setup.py` since we actually use features from Python 3.6.
* Changed dev status back to 3 - Alpha for now
- Standardize docker-compose workflow
- Change docker-compose version to 2.1
- why one might ask? because compose version
3.0 does not support depends on and inherits
like we want to and is more aimed towards migration to using
`docker stack`, for our current strategy `2.1` is a better choice.
- change `bdb` service `bigchaindb` service
- why? Introduced a new proxy service `bdb` which is just a dummy
`busybox` image.
- why? because this ensure via healthcheck of bigchaindb that BigchainDB
has started properly and makes a `curl` to ensure HTTP API server is up
and running.
- why? Because we have had scenarios where BigchainDB is not started
via docker compose and user has to check out the logs to find out what
the problem might be. This ensure that bigchaindb is up and running.
- Does this change deployment workflow? No.
- The only thing change is that if you want to run commands inside a bigchaindb
container e.g. `pytest` now you have to run the following command:
`docker-compose run --rm --no-deps bigchaindb pytest -v --cov=bigchaindb`
as opposed to `docker-compose run --rm --no-deps bdb pytest -v --cov=bigchaindb`
- Remove env variable `BIGCHAINDB_START_TENDERMINT`
- Remove TENDERMINT_INTEGRATION.rst and move to the new docs
- Change mdb -> mongodb because the other services were named with
full name.
- Add example to run specific tests or from a file
- Update config.toml for tendermint to use `bigchaindb` as proxy app
instead of `bdb`
- Remove `network` directory because it is deprecated
- Add comment about why PYTHONBUFFERED is used
* Problem: Docs for BEP#3 implementation not updated
Solutions: Update docs for #2070 and #2106
* Problem: 'Validator update' docs language not clear
Solution: Re-write the documentation which explains when validators are updated
* Problem: Typos and BEP reference missing
Solution: Fix typos and add BEP reference
* Fix for access token authorization for GET calls
- Naming inconsistency for cluster-fqdn causing issues
- Change cluster-frontend-port to node-frontend-port
* Change hardcoded 9984 to configurable
