fabric-samples/test-network
Arnaud J Le Hors 613d269f15
Fix test-network chaincode packaging log (#383)
The chaincode packaging function wrongly implies that the packaging
operation is performed on a peer when it is in fact done locally.
This change fixes that.

Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
2020-12-01 08:30:46 -05:00
..
addOrg3 Update CouchDB to 3.1.1 2020-10-22 19:18:55 -04:00
configtx Fixed script bugs "SendTransaction failed: orderers is nil". (#326) 2020-09-16 10:48:39 -04:00
docker Revert "Mount configuration files (#376)" (#380) 2020-11-25 11:36:11 -05:00
organizations add utils.sh and colorize messages (#310) 2020-08-27 16:43:19 -04:00
scripts Fix test-network chaincode packaging log (#383) 2020-12-01 08:30:46 -05: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 Remove restart mode and add mode specific help text 2020-10-07 03:03:00 -04:00
README.md Allow install of a chaincode 2020-07-15 10:39:12 -04:00
scriptUtils.sh Remove restart mode and add mode specific help text 2020-10-07 03:03:00 -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.