Document secure_gateway for gRPC

This commit is contained in:
CJ Cobb
2021-02-08 20:53:36 -05:00
committed by manojsdoshi
parent 8defb4cd28
commit 5776c2ebe5

View File

@@ -939,6 +939,19 @@
# connection info is specified under the [ledger_tx_tables] config section;
# see the Database section for further documentation.
#
# Each ETL source specified must have gRPC enabled (by adding a [port_grpc]
# section to the config). It is recommended to add a secure_gateway entry to
# the gRPC section, in order to bypass the server's rate limiting.
# This section needs to be added to the config of the ETL source, not
# the config of the reporting node. In the example below, the
# reporting server is running at 127.0.0.1. Multiple IPs can be
# specified in secure_gateway via a comma separated list.
#
# [port_grpc]
# ip = 0.0.0.0
# port = 50051
# secure_gateway = 127.0.0.1
#
#
#-------------------------------------------------------------------------------
#
@@ -1567,6 +1580,7 @@ protocol = ws
#[port_grpc]
#port = 50051
#ip = 0.0.0.0
#secure_gateway = 127.0.0.1
#[port_ws_public]
#port = 6005
@@ -1670,4 +1684,3 @@ validators.txt
# source_grpc_port=50051
# source_ws_port=6005
# source_ip=127.0.0.1