taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Multiple typo and bug fixes

Browse Source 
* Typos in prose
* Typo fix in copy/paste (dropped a letter)
* markup fix: keep list within quoted text
* Auto-corrupt cleanup: Jason to JSON
* gateway: multiple typos and language nits
* monitoring: add missing leafz, fix subsz spelling
This commit is contained in:
Phil Pennock
2019-12-18 12:37:02 -05:00
committed by Phil Pennock
parent 1adc0271aa
commit 28f7c2f1b4
6 changed files with 18 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
nats-server/configuration/gateways/gateway.md
View File

@@ -19,7 +19,7 @@ gateway {
}
```
One difference is that instead of `routes` you specify `gateways`. As expected _self-gateway_ connections are ignored, so you can share gateway configurations with minimal fuzz.
One difference is that instead of `routes` you specify `gateways`. As expected _self-gateway_ connections are ignored, so you can share gateway configurations with minimal fuss.
Starting a server:
@@ -60,15 +60,15 @@ Listening on [>]
| Property | Description |
| :--- | :--- |
| `advertise` | Hostport `<host>:<port>` to advertise to other gateways. |
| `authorization` | Authorization block \(same as other nats-server `authorization` configuration\). |
| `authorization` | Authorization block \(same as other nats-server `authorization` configurations\). |
| `connect_retries` | Number of times the server will try to connect to a discovered gateway. |
| `gateways` | List of Gateway entries - see below. |
| `host` | Interface where the gateway will listen for incomming gateway connections. |
| `host` | Interface where the gateway will listen for incoming gateway connections. |
| `listen` | Combines `host` and `port` as `<host>:<port>` |
| `name` | Name for this cluster, all gateways belonging to the same cluster, should specify the same name. |
| `port` | Port where the gateway will listen for incomming gateway connections. |
| `port` | Port where the gateway will listen for incoming gateway connections. |
| `reject_unknown` | If `true`, gateway will reject connections from gateways that are not configured in `gateways`. |
| `tls` | TLS configuration block \(same as other [nats-server `tls` configuration](../securing_nats/tls.md#tls-configuration)\). |
| `tls` | TLS configuration block \(same as other [nats-server `tls` configurations](../securing_nats/tls.md#tls-configuration)\). |
### `Gateway` Entry
@@ -78,7 +78,7 @@ The `gateways` configuration block is a list of gateway entries with the followi
| :--- | :--- |
| `name` | Gateway name. |
| `url` | Hostport `<host>:<port>` describing where the remote gateway can be reached. If multiple IPs are returned, one is randomly selected. |
| `urls` | A list of `url` |
| `urls` | A list of `url` strings. |
By using `urls` and an array, you can specify a list of endpoints that form part of a cluster as below. A NATS Server will pick one of those addresses randomly and only establish a single outbound gateway connection to one of the members from another cluster: