You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/events/eventsclient/README.md
+17-12Lines changed: 17 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -34,21 +34,21 @@ Next, to start receiving block events from a peer with TLS enabled, run the
34
34
following command:
35
35
36
36
```sh
37
-
CORE_PEER_LOCALMSPID=<msp-id> CORE_PEER_MSPCONFIGPATH=<path to MSP folder> ./eventsclient -channelID=<channel-id> -filtered=<true or false> -tls=true -clientKey=<path to the client key> -clientCert=<path to the client TLS certificate> -rootCert=<path to the server root CA certificate>
37
+
FABRIC_CFG_PATH=<path to config>CORE_PEER_LOCALMSPID=<msp-id> CORE_PEER_MSPCONFIGPATH=<path to MSP folder> ./eventsclient -channelID=<channel-id> -filtered=<true or false> -tls=true -clientKey=<path to the client key> -clientCert=<path to the client TLS certificate> -rootCert=<path to the server root CA certificate>
38
38
```
39
39
40
40
If the peer is not using TLS you can run:
41
41
42
42
```bash
43
-
CORE_PEER_LOCALMSPID=<msp-id> CORE_PEER_MSPCONFIGPATH=<path to MSP folder> ./eventsclient -channelID=<channel-id> -filtered=<true or false> -tls=false
43
+
FABRIC_CFG_PATH=<path to config>CORE_PEER_LOCALMSPID=<msp-id> CORE_PEER_MSPCONFIGPATH=<path to MSP folder> ./eventsclient -channelID=<channel-id> -filtered=<true or false> -tls=false
44
44
```
45
45
46
46
The peer will begin delivering block events and print the output to the console.
47
47
48
-
# Example with the e2e_cli example
48
+
# Example with BYFN
49
49
The events client sample can be used with TLS enabled or disabled. By default,
50
-
the e2e_cli example will have TLS enabled. In order to allow the events client
51
-
to connect to peers created by the e2e_cli example with TLS enabled, the easiest
50
+
the BYFN sample will have TLS enabled. In order to allow the events client
51
+
to connect to peers created by the BYFN sample with TLS enabled, the easiest
52
52
way would be to map `127.0.0.1` to the hostname of the peer that you are
53
53
connecting to, such as `peer0.org1.example.com`. For example on \*nix based
54
54
systems this would be an entry in `/etc/hosts` file.
@@ -58,35 +58,40 @@ CORE_PEER_TLS_ENABLED=***false*** in ``docker-compose-cli.yaml`` and
<arel="license"href="http://creativecommons.org/licenses/by/4.0/"><imgalt="Creative Commons License"style="border-width:0"src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <arel="license"href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.
0 commit comments