Convert Zed lake auth doc to page bundle

brimdata · Dec 13, 2024 · 235dc36 · 235dc36
1 parent 8676991
commit 235dc36
Show file tree

Hide file tree

Showing 14 changed files with 4 additions and 4 deletions.
diff --git a/docs/integrations/zed-lake-auth.md → docs/integrations/zed-lake-auth/_index.md b/docs/integrations/zed-lake-auth.md → docs/integrations/zed-lake-auth/_index.md
@@ -4,11 +4,11 @@ title: Authentication Configuration
 heading: Configuring Authentication for a Zed Lake Service
 ---
 
-A [SuperDB data lake service](../commands/super-db.md#serve) may be configured to require
+A [SuperDB data lake service](../../commands/super-db.md#serve) may be configured to require
 user authentication to be accessed from clients such as the
 [Zui](https://zui.brimdata.io/) application, the
-[`super db`](../commands/super.md) CLI commands, or the
-[SuperDB Python client](../libraries/python.md). This document describes a simple
+[`super db`](../../commands/super.md) CLI commands, or the
+[SuperDB Python client](../../libraries/python.md). This document describes a simple
 [Auth0](https://auth0.com) configuration with accompanying `super db serve` flags
 that can be used as a starting point for creating similar configurations in
 your own environment.
@@ -96,7 +96,7 @@ checkbox to enable the **Device Code** grant type.
 
 ## Zed Lake Service Configuration
 
-1. Login to our Linux VM and [install](../install.md#building-from-source)
+1. Login to our Linux VM and [install](../../install.md#building-from-source)
 the most recent Zed tools from source.
 
    ```

diff --git a/docs/integrations/allowed-callback-urls.png → ...s/zed-lake-auth/allowed-callback-urls.png b/docs/integrations/allowed-callback-urls.png → ...s/zed-lake-auth/allowed-callback-urls.png
diff --git a/...integrations/api-allow-offline-access.png → ...ed-lake-auth/api-allow-offline-access.png b/...integrations/api-allow-offline-access.png → ...ed-lake-auth/api-allow-offline-access.png
diff --git a/docs/integrations/api-name-identifier.png → ...ons/zed-lake-auth/api-name-identifier.png b/docs/integrations/api-name-identifier.png → ...ons/zed-lake-auth/api-name-identifier.png
diff --git a/docs/integrations/application-name.png → ...ations/zed-lake-auth/application-name.png b/docs/integrations/application-name.png → ...ations/zed-lake-auth/application-name.png
diff --git a/docs/integrations/click-api-settings.png → ...ions/zed-lake-auth/click-api-settings.png b/docs/integrations/click-api-settings.png → ...ions/zed-lake-auth/click-api-settings.png
diff --git a/...tegrations/click-application-settings.png → ...-lake-auth/click-application-settings.png b/...tegrations/click-application-settings.png → ...-lake-auth/click-application-settings.png
diff --git a/docs/integrations/click-grant-types.png → ...tions/zed-lake-auth/click-grant-types.png b/docs/integrations/click-grant-types.png → ...tions/zed-lake-auth/click-grant-types.png
diff --git a/docs/integrations/create-api.png → ...integrations/zed-lake-auth/create-api.png b/docs/integrations/create-api.png → ...integrations/zed-lake-auth/create-api.png
diff --git a/docs/integrations/create-application.png → ...ions/zed-lake-auth/create-application.png b/docs/integrations/create-application.png → ...ions/zed-lake-auth/create-application.png
diff --git a/docs/integrations/device-code-grant-type.png → .../zed-lake-auth/device-code-grant-type.png b/docs/integrations/device-code-grant-type.png → .../zed-lake-auth/device-code-grant-type.png
diff --git a/...integrations/expand-advanced-settings.png → ...ed-lake-auth/expand-advanced-settings.png b/...integrations/expand-advanced-settings.png → ...ed-lake-auth/expand-advanced-settings.png
diff --git a/docs/integrations/login-flow-thumbnail.png → ...ns/zed-lake-auth/login-flow-thumbnail.png b/docs/integrations/login-flow-thumbnail.png → ...ns/zed-lake-auth/login-flow-thumbnail.png
diff --git a/...ntegrations/save-application-settings.png → ...d-lake-auth/save-application-settings.png b/...ntegrations/save-application-settings.png → ...d-lake-auth/save-application-settings.png