fabric-samples/test-network
Brett Logan 8b54e14ee4 Use Official CouchDB 3.1 Image
Fabric 2.2 removes official support for CouchDB 2.x.
The migration to 3.1 was to address fsync issues
in the underlying storage implementation in Couch.

This change moves to CouchDB 3.1 which requires the
user to now set an admin identity at startup.

Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
2020-07-02 09:56:30 -04:00
..
addOrg3 Use Official CouchDB 3.1 Image 2020-07-02 09:56:30 -04:00
configtx [FAB-17504] add Organizations.<Org>.OrdererEndpoints and remove Orderer.Addresses (#125) 2020-03-20 16:02:44 +01:00
docker Use Official CouchDB 3.1 Image 2020-07-02 09:56:30 -04:00
organizations [FAB-18020] Add config.yaml to msp folder for User1 in test-network 2020-06-23 22:45:37 -04:00
scripts Update deployCC.sh (#199) 2020-06-05 16:07:14 -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 [FAB-17145] Add test network to Fabric Samples 2019-12-11 10:28:39 -05:00
network.sh [FAB-17952] Fix test-network to use the latest version of fabric-ca (#195) 2020-06-03 13:34:26 -04:00
README.md FAB-17243 Add support for Fabric CA for Org3 on the (#91) 2020-01-16 22:32:12 +01: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 the fabcar 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.