From a5367ef9f8c497a826dac72dab01c93b8d792c61 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Fri, 21 Jan 2022 10:13:22 +0100 Subject: [PATCH] docs: improve proxy commands --- website/docs/sdks/unleash-proxy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/sdks/unleash-proxy.md b/website/docs/sdks/unleash-proxy.md index 4a30dd6181..bb624eae83 100644 --- a/website/docs/sdks/unleash-proxy.md +++ b/website/docs/sdks/unleash-proxy.md @@ -35,7 +35,7 @@ Regardless of how you choose to run the it, the proxy will need access to these The API token to connect to your Unleash project. For more information on how these work and how to create them, check out the [API token documentation](../user_guide/token.md). -- **`proxySecrets`** / **`UNLEASH_PROXY_SECRETS`** +- **`clientKeys`** / **`UNLEASH_PROXY_CLIENT_KEYS`** A list of client keys that the proxy will accept. For the proxy to accept an incoming request, the client must use one of these keys for authorization. In client SDKs, this is usually known as a `clientKey` or a `clientSecret`. If you query the proxy directly via HTTP, this is the `authorization` header. @@ -57,7 +57,7 @@ The easiest way to run Unleash is via Docker. We have published a [docker image ```bash docker run \ - -e UNLEASH_PROXY_SECRETS=some-secret \ + -e UNLEASH_PROXY_CLIENT_KEYS=some-public-key \ -e UNLEASH_URL='https://app.unleash-hosted.com/demo/api/' \ -e UNLEASH_API_TOKEN=56907a2fa53c1d16101d509a10b78e36190b0f918d9f122d \ -p 3000:3000 \