Recently I was going through some implementations of hyperledger fabric , and I came across with some confusing environment variables for fabric components(some of which listed below). Is there any documentation where I can read about all the environment variables of fabric components. Currently I am am confused about below environment variables of fabric peer:
All environment variables actually mirrored configuration parameters prefixed with CORE_PEER, most of them have descent documentation inside core.yaml. The intent behind setting these parameters in environmental variable is to been able to override them inside the docker containers.
So for example CORE_PEER_ADDRESS, CORE_PEER_NETWORKID, CORE_PEER_ID:
###############################################################################
#
# Peer section
#
###############################################################################
peer:
# The Peer id is used for identifying this Peer instance.
id: jdoe
# The networkId allows for logical seperation of networks
networkId: dev
# The endpoint this peer uses to listen for inbound chaincode connections.
# If this is commented-out, the listen address is selected to be
# the peer's address (see below) with port 7052
# chaincodeListenAddress: 0.0.0.0:7052
# The endpoint the chaincode for this peer uses to connect to the peer.
# If this is not specified, the chaincodeListenAddress address is selected.
# And if chaincodeListenAddress is not specified, address is selected from
# peer listenAddress.
# chaincodeAddress: 0.0.0.0:7052
# When used as peer config, this represents the endpoint to other peers
# in the same organization. For peers in other organization, see
# gossip.externalEndpoint for more info.
# When used as CLI config, this means the peer's endpoint to interact with
address: 0.0.0.0:7051
and you can find more here.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With