fabric-samples/test-network
Brett Logan 37513c3c2b Add Service Labels and Cleanup Using Standard Tools
Add a service label to all containers launch by compose.
This allows us to filter on the label for removing running
containers.

Use filtering for querying running containers and
images to make sure we only target the containers
and images we want to remove.

Signed-off-by: Brett Logan <lindluni@github.com>
2021-02-11 17:34:49 -05:00
..
addOrg3 Add Service Labels and Cleanup Using Standard Tools 2021-02-11 17:34:49 -05:00
configtx Update Test Network to Use osadmin 2021-01-19 20:55:19 -05:00
docker Add Service Labels and Cleanup Using Standard Tools 2021-02-11 17:34:49 -05:00
organizations Fix creating channel when ${PWD} contains space. (#402) 2021-01-20 16:32:38 +01:00
scripts Rename --channel-id to --channelID in osadmin 2021-02-03 13:33:19 -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 Add Service Labels and Cleanup Using Standard Tools 2021-02-11 17:34:49 -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.