cducrest
commented
4 years ago I initially had it that the user could set up a port via flag but it's a pain to make it work with docker, because then I need to use environment variables in the docker-override.yml. If the user for example gives invalid inputs (ports already taken, same ports twice, ports lower than 80, no ports for WS, etc ...) the container will not start/the docker-compose file will be invalid and it is hard to debug for the user.
I'll add some docs
close: https://github.com/trustlines-network/project/issues/881
It is a slight pain to test.
The quickstart script does not work on master, since it pulls the latest released docker image for the home node, and that image does not use Openethereum, while the docker-compose file expects the version with Openethereum. This is to keep the repository coherent over functional.
To test this, you thus need to build the home node image you want to test (laika or tlbc) on master and tagging it the way the docker-compose file expects it. e.g.
cd chain && docker build -f tlbc/Dockerfile -t trustlines/tlbc-node:release ..You then need to prevent the quickstart script to pull the image and replace it by commenting lines 233-239 of
quickstart/src/quickstart/docker.py.After that you are free to test whatever you want, for example
quickstart tlbc --expose-portsand test that the home node is reachable withcurl --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545.