From a209f04157a05ce2d7ed0266e3463d2aa9aec6d5 Mon Sep 17 00:00:00 2001 From: Omar Sanseviero Date: Wed, 22 Nov 2023 15:14:42 +0100 Subject: [PATCH] Fix broken link (#1115) --- docs/hub/spaces-sdks-docker.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/hub/spaces-sdks-docker.md b/docs/hub/spaces-sdks-docker.md index f936f8e54..cd906efef 100644 --- a/docs/hub/spaces-sdks-docker.md +++ b/docs/hub/spaces-sdks-docker.md @@ -23,7 +23,7 @@ If you want to expose apps served on multiple ports to the outside world, a work ## Secrets and Variables Management -You can manage a Space's environment variables in the Space Settings. Read more [here](./spaces-overview.md#managing-the-environment). +You can manage a Space's environment variables in the Space Settings. Read more [here](./spaces-overview#managing-the-environment). ### Variables @@ -50,7 +50,7 @@ Variables are injected in the container's environment at runtime. #### Buildtime -In Docker Spaces, the secrets management is different for security reasons. Once you create a secret in the [Settings tab](./spaces-overview#managing-secrets-and-environment-variables), you can expose the secret by adding the following line in your Dockerfile: +In Docker Spaces, the secrets management is different for security reasons. Once you create a secret in the [Settings tab](./spaces-overview#managing-secrets), you can expose the secret by adding the following line in your Dockerfile: For example, if `SECRET_EXAMPLE` is the name of the secret you created in the Settings tab, you can read it at build time by mounting it to a file, then reading it with `$(cat /run/secrets/SECRET_EXAMPLE)`.