From d5c5c7c772822b4605b65d6848cba54cdc2bc9fe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20B=C3=B6hmer?= Date: Fri, 29 Aug 2025 23:25:58 +0200 Subject: [PATCH] Added documentation about the censoring --- docs/configuration.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/configuration.md b/docs/configuration.md index 9cb5d1b3..d4b21781 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -43,7 +43,8 @@ options listed, see `.env` file for the full list of possible env variables. Environment variables allow to overwrite settings in the web interface. This is useful, if you want to enforce certain settings to be unchangable by users, or if you want to configure settings in a central place in a deployed environment. On the settings page, you can hover over a setting to see, which environment variable can be used to overwrite it, it -is shown as tooltip. +is shown as tooltip. API keys or similar sensitve data which is overwritten by env variables, are redacted on the web +interface, so that even administrators cannot see them (only the last 2 characters and the length). For technical and security reasons some settings can only be configured via environment variables and not via the web interface. These settings are marked with "(env only)" in the description below.