fabric-samples/test-network
Brett Logan 1c500ba30e Use Busybox to Remove Files and Folders
We delete folders and files locally on the host system
today. If the user is not a super user the files can't
be deleted as they are created by a root user in the
containers. This change uses busybox to perform the
deletions instead so a root user can remove them.

Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
2020-07-27 23:55:20 -04:00
..
addOrg3 Revert "WIP (#253)" 2020-07-20 13:18:45 -04:00
configtx [FAB-17504] add Organizations.<Org>.OrdererEndpoints and remove Orderer.Addresses (#125) 2020-03-20 16:02:44 +01:00
docker Remove gossip leader election config from samples (#223) 2020-07-02 15:37:15 -04:00
organizations Revert "WIP (#253)" 2020-07-20 13:18:45 -04:00
scripts private data readme edits 2020-07-27 23:37:41 -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 Allow install of a chaincode 2020-07-15 10:39:12 -04:00
network.sh Use Busybox to Remove Files and Folders 2020-07-27 23:55:20 -04: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.