From da8d954456ea3d141e6f2d118f96d19178cf00fa Mon Sep 17 00:00:00 2001 From: Michael Quigley Date: Wed, 11 Dec 2024 12:31:44 -0500 Subject: [PATCH] doc structure lint (#537) --- docs/guides/{ => self-hosting}/organizations.md | 4 ++-- docs/guides/self-hosting/personalized-frontend.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) rename docs/guides/{ => self-hosting}/organizations.md (97%) diff --git a/docs/guides/organizations.md b/docs/guides/self-hosting/organizations.md similarity index 97% rename from docs/guides/organizations.md rename to docs/guides/self-hosting/organizations.md index 420d5ffa..1ce9a067 100644 --- a/docs/guides/organizations.md +++ b/docs/guides/self-hosting/organizations.md @@ -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 diff --git a/docs/guides/self-hosting/personalized-frontend.md b/docs/guides/self-hosting/personalized-frontend.md index af836ec5..7dc20a2a 100644 --- a/docs/guides/self-hosting/personalized-frontend.md +++ b/docs/guides/self-hosting/personalized-frontend.md @@ -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. \ No newline at end of file +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.