* Dependencies update
Signed-off-by: David Dashyan <mail@davie.li>
* Dockerfile-dev: update python version + remove system pynacl
Signed-off-by: David Dashyan <mail@davie.li>
* Set dummy_transaction fixture scope to "session"
Signed-off-by: David Dashyan <mail@davie.li>
* Add 3.7 and 3.8 python tests
* setup.py: fix version typo
* Problem: Need a method to initiate a new upsert-validator election
Solution: Added subcommand `new` to `upsert_validator`
* Problem: Changes to upsert-validator needed to be reflected in the docs
Solution: Wrote a section for `upsert-validator new`
* Problem: we don't have any tests for malicious strings
Solution: Use a parameterized test that fuzzes over a library of potentially hazardous strings
* Needed to update the Dockerfile to install blns
* Removed unnecessary import from Dockerfile-dev
* Made the conditions under which the test expects an error more explicit
* Improved reporting in case of a bad status code
* Removed some over-zealous assertions.
* Removed `sent_transaction` from assertation error response
* *Problem: blns was removed as a dependency while fixing a merge conflict
Solution: added it back to the Dockerfile
* *Problem: made a typo when adding blns to the Dockerfile
Solution: fixed the typo
- 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
* Basing BigchainDB docker image from `python:3.6` in `Dockerfile` and `Dockerfile-dev`.
* Added ENV var for websocket interface
* Optimization to Dockerfile-dev to save build time during dev/test.
Pre-installing the `pynacl` dependeny in separate command so that devs
do not need to wait while testing. The trade-off is that devs will
need to clear (`rmi`) the image to start from scratch.
* Include configuration step in Dockerfile
* Document dev setup with docker-compose
* Add server API env vars and port
* Parameterize SERVER_BIND and API_ENDPOINT env vars
* Give a bit more detailed information on GET /
zzappie
Nikita Chernyi
Troy McConaghy
Zachary Bowen
Vanshdeep Singh
codegeschrei
Ahmed Muawia Khan
Krish
Sylvain Bellemare
tim
Brett Sun
Sylvain Bellemare