You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by jo...@apache.org on 2024/03/18 16:54:54 UTC
(superset) branch master updated: fix: typo in configuring-superset.mdx (#27541)
This is an automated email from the ASF dual-hosted git repository.
johnbodley pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/superset.git
The following commit(s) were added to refs/heads/master by this push:
new d820c9c2ff fix: typo in configuring-superset.mdx (#27541)
d820c9c2ff is described below
commit d820c9c2ffa8ebe42278dff32f990728dff133b1
Author: Armando Fandango <ar...@users.noreply.github.com>
AuthorDate: Mon Mar 18 12:54:47 2024 -0400
fix: typo in configuring-superset.mdx (#27541)
---
docs/docs/installation/configuring-superset.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/docs/installation/configuring-superset.mdx b/docs/docs/installation/configuring-superset.mdx
index 30bc2f281c..ac80ef3bf0 100644
--- a/docs/docs/installation/configuring-superset.mdx
+++ b/docs/docs/installation/configuring-superset.mdx
@@ -39,7 +39,7 @@ ROW_LIMIT = 5000
# and encrypting sensitive information on the database
# Make sure you are changing this key for your deployment with a strong key.
# Alternatively you can set it with `SUPERSET_SECRET_KEY` environment variable.
-# You MUST set this for production environments or the server will not refuse
+# You MUST set this for production environments or the server will refuse
# to start and you will see an error in the logs accordingly.
SECRET_KEY = 'YOUR_OWN_RANDOM_GENERATED_SECRET_KEY'