fabric-samples/test-network
denyeart e496083c0b
Remove .env Files and Explicitly Name Network (#417) (#469)
There have been lots of changes and quirks with the
docker-compose .env file, this change removes the file
and explicitly creates and assigns the networks in the
compose yaml files.

Signed-off-by: Brett Logan <lindluni@github.com>
Signed-off-by: David Enyeart <enyeart@us.ibm.com>

Co-authored-by: Brett Logan <lindluni@github.com>
2021-08-30 11:59:19 -04:00
..
addOrg3 Remove .env Files and Explicitly Name Network (#417) (#469) 2021-08-30 11:59:19 -04:00
configtx Remove Org3cli and configtx.yaml anchor peers from test-network (#401) 2021-01-11 11:27:58 -05:00
docker Remove .env Files and Explicitly Name Network (#417) (#469) 2021-08-30 11:59:19 -04:00
organizations Cleanup of register/enroll script 2021-01-18 14:22:20 -05:00
scripts Stop using deprecated outputAnchorPeersUpdate in test-network (#394) 2021-01-07 13:22:03 -05:00
system-genesis-block [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 Stop using deprecated outputAnchorPeersUpdate in test-network (#394) 2021-01-07 13:22:03 -05:00
README.md Allow install of a chaincode 2020-07-15 10:39:12 -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.