From 3334a7f130833942eee05a54ee1150976ced0560 Mon Sep 17 00:00:00 2001 From: Baohua Yang Date: Wed, 3 May 2017 16:34:28 +0800 Subject: [PATCH] [FAB-3612] Update peer.address usage peer.address means differently when using as peer or cli config. This patchset add docs to explain more clearly. Change-Id: Ie9910f8cc27252d8b50619d7f5b8ddcf3d7bf76f Signed-off-by: Baohua Yang --- sampleconfig/core.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/sampleconfig/core.yaml b/sampleconfig/core.yaml index 0692f1e44db..d6e9ad84dbd 100644 --- a/sampleconfig/core.yaml +++ b/sampleconfig/core.yaml @@ -52,8 +52,9 @@ peer: # The Address this Peer will listen on listenAddress: 0.0.0.0:7051 - # Represents the peer's endpoint to peers in its organization - # for other peers, see externalEndpoint + # When used as peer config, represents the endpoint to other peers in the same organization + # for peers in other organization, see gossip.externalEndpoint + # When used as cli config, will mean the peer node's endpoint to interact with address: 0.0.0.0:7051 # Whether the Peer should programmatically determine its address # This case is useful for docker containers.