Create quorum based consortium chain painless, deploy it to Docker-compose & Kubernetes
dockerkubectlminikube
git clone https://github.com/ATNIO/quorum-deploy.git
cd quorum-deploy
docker build -t quorum -f quorum.Dockerfile .
docker tag quorum asia.gcr.io/consortiumchain/quorum
docker build -t explorer-ui -f ui.Dockerfile .
docker tag explorer-ui asia.gcr.io/consortiumchain/explorer-ui
docker build -t explorer-backend -f backend.Dockerfile .
docker tag explorer-backend asia.gcr.io/consortiumchain/explorer-backendEdit ip.cfg, enable the config for docker and disable the others, then run
./setup.sh && docker-compose up -dNow you have a consortium chain and it's explorer running inside docker, you can test them by
geth --exec 'loadScript("examples/contract_pub.js") attach http://0.0.0.0:22001
open http://localhost:5000If the explorer doesn't sync block data correctly, you should restart it by
docker-compose restart explorer_backendEdit ip.cfg, enable the config for minikube and disable the other ones, then run
eval $(minikube docker-env)
docker build -t quorum -f quorum.Dockerfile .
docker tag quorum asia.gcr.io/consortiumchain/quorum
docker build -t explorer-ui -f ui.Dockerfile .
docker tag explorer-ui asia.gcr.io/consortiumchain/explorer-ui
docker build -t explorer-backend -f backend.Dockerfile .
docker tag explorer-backend asia.gcr.io/consortiumchain/explorer-backend
./setup.sh
minikube start
kubectl config use-context minikube
kubectl create -f consortium.yaml,explorer.yamlNow you have a local consortium chain cluster and it's explorer running inside minikube, have a try by
geth --exec 'loadScript("examples/contract_pub.js")' attach http://$(minikube ip):31710
open http://$(minikube ip):31710If the explorer doesn't sync block data correctly, you should restart it by
cd scripts && ./recreate explorerSimilar to minikube, one important additional thing is that you must have a static ip address for explorer_ip in ip.cfg. For GCP, follow this
In addition, there are several scripts in the scripts/ directory may help you. To use them, you must cd scripts
./attach node-1 # geth attach to node-1
./inspect node-1 # get into container of node-1
./inspect expl mongodb # get into container of mongodb of explore
./pubkey node-1 # get constellation public key of node-1For other scripts, just run it and it will do the thing as it's name says.
Our consortium chain is now living on the GCP Kubernetes Engine, named consortiumchain.
- Consortium chain explorer url:
http://35.229.221.95:5000/- Consortium node rpc urls:
# node-1
http://35.229.229.248:8545
# node-2
http://35.201.215.219:8545
# node-3
http://35.189.163.25:8545- Loadbalanced nodes' rpc url:
http://35.194.196.250:8545- Consortium node public keys:
# node-1
fsOD/f81FUBcO84u4EGkoHx1ymvPhPcUc7qTuiJX6VY=
# node-2
JEpO9gLgPcQM3II8MP4Hzf0mHrS1vcGIao+AWrK1qCA=
# node-3
RHoXgVLqX9KwMvBfi3os6xylk1+XhPslDW4rLge+Hj4=You may play with them in this way
- Public contract creation
# deploy a public contract to node-1
geth --exec 'loadScript("examples/contract_pub.js")' attach http://35.229.229.248:8545- Private contract creation
# deploy a private contract to node-1, private for node-2
geth --exec 'loadScript("examples/contract_pri.js")' attach http://35.229.229.248:8545Now open http://35.229.221.95:5000/ on your web explorer to explorer blocks & transactions.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent