1
1
mirror of https://github.com/openziti/zrok.git synced 2025-01-04 13:09:25 +01:00

doc structure lint ()

This commit is contained in:
Michael Quigley 2024-12-11 12:31:44 -05:00
parent eb042105e7
commit da8d954456
No known key found for this signature in database
GPG Key ID: 9B60314A9DD20A62
2 changed files with 4 additions and 4 deletions

View File

@ -1,5 +1,5 @@
---
sidebar_position: 23
sidebar_position: 21
sidebar_label: Organizations
---
@ -11,7 +11,7 @@ Future zrok releases will include additional organization features, including `-
## Configuring an Organization
The API endpoints used to manage organizations and their members require a site-level `ZROK_ADMIN_TOKEN` to access. See the [self-hosting guide](self-hosting/linux for details on configuring admin tokens.
The API endpoints used to manage organizations and their members require a site-level `ZROK_ADMIN_TOKEN` to access. See the [self-hosting guide](linux) for details on configuring admin tokens.
### Create an Organization

View File

@ -1,7 +1,7 @@
---
title: Personalized Frontend
sidebar_label: Personalized Frontend
sidebar_position: 19
sidebar_position: 22
---
This guide describes an approach that enables a zrok user to use a hosted, shared instance (zrok.io) and configure their own personalized frontend, which enables custom DNS and TLS for their shares.
@ -70,4 +70,4 @@ Your protected resources remain disconnected from the internet and are only reac
When you use a public frontend (with a simple `zrok share public`) at a hosted zrok instance (like zrok.io), the operators of that service have some amount of visibility into what traffic you're sending to your shares. The load balancers in front of the public frontend maintain logs describing all of the URLs that were accessed, as well as other information (headers, etc.) that contain information about the resource you're sharing.
If you create private shares using `zrok share private` and then run your own `zrok access private` from some other location, the operators of the zrok service instance only know that some amount of data moved between the environment running the `zrok share private` and the `zrok access private`. There is no other information available.
If you create private shares using `zrok share private` and then run your own `zrok access private` from some other location, the operators of the zrok service instance only know that some amount of data moved between the environment running the `zrok share private` and the `zrok access private`. There is no other information available.