fabric-samples/test-network
Brett Logan 49bf79909d
Remove .env Files and Explicitly Name Network (#417)
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>
2021-02-10 21:38:35 -05:00
..
addOrg3 Remove .env Files and Explicitly Name Network (#417) 2021-02-10 21:38:35 -05:00
configtx Update Test Network to Use osadmin 2021-01-19 20:55:19 -05:00
docker Remove .env Files and Explicitly Name Network (#417) 2021-02-10 21:38:35 -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 Fix creating channel when ${PWD} contains space. (#402) 2021-01-20 16:32:38 +01: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.