fabric-samples/test-network
nikhil550 aaaf1ba59b
Replace waiting period (#331)
Signed-off-by: NIKHIL E GUPTA <negupta@us.ibm.com>

Co-authored-by: NIKHIL E GUPTA <negupta@us.ibm.com>
2020-09-15 15:35:38 +02:00
..
addOrg3 hide set +x from output 2020-08-21 13:03:30 -04:00
configtx [FAB-17504] add Organizations.<Org>.OrdererEndpoints and remove Orderer.Addresses (#125) 2020-03-20 16:02:44 +01:00
docker Remove gossip leader election config from samples (#223) 2020-07-02 15:37:15 -04:00
organizations add utils.sh and colorize messages (#310) 2020-08-27 16:43:19 -04:00
scripts add utils.sh and colorize messages (#310) 2020-08-27 16:43:19 -04:00
system-genesis-block [FAB-17145] Add test network to Fabric Samples 2019-12-11 10:28:39 -05:00
.env [FAB-17145] Add test network to Fabric Samples 2019-12-11 10:28:39 -05:00
.gitignore Allow install of a chaincode 2020-07-15 10:39:12 -04:00
network.sh Replace waiting period (#331) 2020-09-15 15:35:38 +02:00
README.md Allow install of a chaincode 2020-07-15 10:39:12 -04:00
scriptUtils.sh add utils.sh and colorize messages (#310) 2020-08-27 16:43:19 -04:00

Running the test network

You can use the ./network.sh script to stand up a simple Fabric test network. The test network has two peer organizations with one peer each and a single node raft ordering service. You can also use the ./network.sh script to create channels and deploy chaincode. For more information, see Using the Fabric test network. The test network is being introduced in Fabric v2.0 as the long term replacement for the first-network sample.

Before you can deploy the test network, you need to follow the instructions to Install the Samples, Binaries and Docker Images in the Hyperledger Fabric documentation.