Create a network to jump start development of your decentralized application on Hyperledger Fabric platform.
The network is run by docker containers and can be deployed to one host for development or to multiple hosts for testing or production.
Scripts of this starter generate crypto material and config files, start the network and deploy your chaincodes. Developers can use REST API to invoke and query chaincodes, explore blocks and transactions.
The following sections describe Fabric Starter possibilites in more details:
docker-machine. Deployment to clouds.
To deploy network with a particular version of HL Fabric export desired version in the
FABRIC_VERSION environment variable. The
latest docker image tag is used by default.
See One Org Network
See Use REST Api
invite-based blockchain-networks (see next chapter) new organization can be added to the consortium by a member of this network.
The new organization need to obtain the BOOTSRAP_IP (currently it's the IP of the orderer node) and deploy its own node with this IP.
export BOOTSTRAP_IP=192.168.0.1 #ORG=... DOMAIN=... docker-compose up
Then the new organization passes the ip address of the newly deployed node to the network's member and this member adds the organization to Consortium by it's administration dashboard. After that the new organization can create own channels, add other organizations to the own channels and even invite more organizations to the network itself.
So now our network can be governed by itself (or to say it right by the network's members).
The first type of network-governance is
Invite-based. With this type of deployment
any organization ((and not a central system administrator)) - member of the blockchain network can add new organization to consortium.
To deploy such type of network export environment variable
WWW_PORT=81 WORK_DIR=./ docker-compose -f docker-compose-orderer.yaml -f docker-compose-orderer-multihost.yaml up -d
Then start an organization
MY_IP=192.168.99.yy BOOTSTRAP_IP=192.168.99.xx ORG=org1 MULTIHOST=true WORK_DIR=./ docker-compose -f docker-compose.yaml -f docker-compose-multihost.yaml -f docker-compose-api-port.yaml up -d
Majority type of governance is coming.
Consensus Types. RAFT consensus algorithm. By default Fabric Starter uses Solo type of consensus. To use RAFT consensus see instructions in Start Raft Ordering Service
As this project doesn't have a defined release cycle yet we create
when we see code is stable enough or before introducing major changes\new features.
Note, the Hyperledger Fabric version which the snapshot depends on is defined in the
Also this project uses olegabu/fabric-starter-rest docker image which has the same versioning approach but even updated docker image with the same label (e.g. latest) won't be pulled automatically if it exists in the local docker registry.
You have to remove the old image manually (by
docker rmi -f olegabu/fabric-starter-rest).
master branch as well as potentially
feature branches are used for development.
Master is assigned to the
latest version of Fabric.