mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-17 15:35:09 +00:00
2663a07765
Test network Nano bash provides a set of minimal bash scripts to run a Fabric network on your local machine. The network is functionally equivalent to the docker-based Test Network, you can therefore run all the tutorials and samples that target the Test Network. The Fabric release binaries are utilized rather than using docker containers to avoid all unnecessary layers. Only the chaincode and chaincode builder runs in a docker container behind the scenes. Using the Fabric binaries also makes it simple for Fabric developers to iteratively and quickly modify Fabric code and test a Fabric network as a user. Signed-off-by: David Enyeart <enyeart@us.ibm.com>
35 lines
2.1 KiB
Bash
Executable file
35 lines
2.1 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
set -euo pipefail
|
|
|
|
# look for binaries in local dev environment /build/bin directory and then in local samples /bin directory
|
|
export PATH="${PWD}"/../../fabric/build/bin:"${PWD}"/../bin:"$PATH"
|
|
export FABRIC_CFG_PATH="${PWD}"/../config
|
|
|
|
export FABRIC_LOGGING_SPEC=debug:cauthdsl,policies,msp,grpc,peer.gossip.mcs,gossip,leveldbhelper=info
|
|
export CORE_PEER_TLS_ENABLED=true
|
|
export CORE_PEER_TLS_CERT_FILE="${PWD}"/crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.crt
|
|
export CORE_PEER_TLS_KEY_FILE="${PWD}"/crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.key
|
|
export CORE_PEER_TLS_ROOTCERT_FILE="${PWD}"/crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt
|
|
export CORE_PEER_ID=peer0.org2.example.com
|
|
export CORE_PEER_ADDRESS=127.0.0.1:7057
|
|
export CORE_PEER_LISTENADDRESS=127.0.0.1:7057
|
|
export CORE_PEER_CHAINCODEADDRESS=host.docker.internal:7058
|
|
export CORE_PEER_CHAINCODELISTENADDRESS=127.0.0.1:7058
|
|
# bootstrap peer is the other peer in the same org
|
|
export CORE_PEER_GOSSIP_BOOTSTRAP=127.0.0.1:7055
|
|
export CORE_PEER_GOSSIP_EXTERNALENDPOINT=127.0.0.1:7057
|
|
export CORE_PEER_LOCALMSPID=Org2MSP
|
|
export CORE_PEER_MSPCONFIGPATH="${PWD}"/crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/msp
|
|
export CORE_OPERATIONS_LISTENADDRESS=127.0.0.1:8449
|
|
export CORE_PEER_FILESYSTEMPATH="${PWD}"/data/peer1.org2.example.com
|
|
export CORE_LEDGER_SNAPSHOTS_ROOTDIR="${PWD}"/data/peer1.org2.example.com/snapshots
|
|
|
|
# uncomment the lines below to utilize couchdb state database, when done with the environment you can stop the couchdb container with "docker rm -f couchdb4"
|
|
# export CORE_LEDGER_STATE_STATEDATABASE=CouchDB
|
|
# export CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=127.0.0.1:5987
|
|
# export CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
|
|
# export CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=password
|
|
# docker run --publish 5987:5984 --detach -e COUCHDB_USER=admin -e COUCHDB_PASSWORD=password --name couchdb4 couchdb:3.1.1
|
|
|
|
# start peer
|
|
peer node start
|