diff options
| author | Tasos Katsoulas <12612986+tkatsoulas@users.noreply.github.com> | 2023-02-02 15:23:54 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-02 15:23:54 +0200 |
| commit | 9f1403de7d3ea2633768d34095afcf880c7c4e2d (patch) | |
| tree | 0c50a1f42b3e182f6cd5de4e92c609cc76fd3cb5 /registry | |
| parent | caf18920aac38eed782647957e82c0ab7f64ec17 (diff) | |
Covert our documentation links to GH absolute links (#14344)
Signed-off-by: Tasos Katsoulas <tasos@netdata.cloud>
Diffstat (limited to 'registry')
| -rw-r--r-- | registry/README.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/registry/README.md b/registry/README.md index e01af49530..827eea1399 100644 --- a/registry/README.md +++ b/registry/README.md @@ -71,8 +71,8 @@ in the Netdata registry regardless of whether you sign in or not. ## Who talks to the registry? -Your web browser **only**! If sending this information is against your policies, you can [run your own -registry](#run-your-own-registry) +Your web browser **only**! If sending this information is against your policies, you +can [run your own registry](#run-your-own-registry) Your Netdata servers do not talk to the registry. This is a UML diagram of its operation: @@ -137,7 +137,7 @@ Netdata v1.9+ support limiting access to the registry from given IPs, like this: allow from = * ``` -`allow from` settings are [Netdata simple patterns](/libnetdata/simple_pattern/README.md): string matches that use `*` +`allow from` settings are [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md): string matches that use `*` as wildcard (any number of times) and a `!` prefix for a negative match. So: `allow from = !10.1.2.3 10.*` will allow all IPs in `10.*` except `10.1.2.3`. The order is important: left to right, the first positive or negative match is used. @@ -184,7 +184,7 @@ Both files are machine readable text files. Beginning with `v1.30.0`, when the Netdata Agent's web server processes a request, it delivers the `SameSite=none` and `Secure` cookies. If you have problems accessing the local Agent dashboard or Netdata Cloud, disable these -cookies by [editing `netdata.conf`](/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files): +cookies by [editing `netdata.conf`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files): ```conf [registry] |