fabric-samples/test-network
Brett Logan e17574d28c
Add CA's to docker test network (#124)
The CA's are not part of the `test` docker network. So
applications written and hosted on the `test` network
cannot interact with the CA

Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
2020-03-20 14:24:56 +00:00
..
addOrg3 Remove reference to 2.0 beta (#111) 2020-02-23 07:18:29 +01:00
configtx [FAB-17145] Add test network to Fabric Samples 2019-12-11 10:28:39 -05:00
docker Add CA's to docker test network (#124) 2020-03-20 14:24:56 +00:00
organizations Remove reference to 2.0 beta (#111) 2020-02-23 07:18:29 +01:00
scripts Remove reference to 2.0 beta (#111) 2020-02-23 07:18:29 +01: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 Remove reference to 2.0 beta (#111) 2020-02-23 07:18:29 +01: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.