fabric-samples/test-network
Nao Nishijima 1ab2013c5c Fix unread .env file
Deploying chaincode failed due to missing .env file.
Previous commit moves .env file to docker directory from
test-network directory. Therefore, .env file doesn't exist
current working directory.
This PR adds --env-file option to docker-compose command to
read .env file.

Signed-off-by: Nao Nishijima <nao.nishijima.xt@hitachi.com>
2021-02-10 02:06:20 +00:00
..
addOrg3 Fix creating channel when ${PWD} contains space. (#402) 2021-01-20 16:32:38 +01:00
configtx Update Test Network to Use osadmin 2021-01-19 20:55:19 -05:00
docker try to fix CI error 2021-02-08 10:52: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 unread .env file 2021-02-10 02:06:20 +00: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.