This is an automated email from the ASF dual-hosted git repository. sfirke pushed a commit to branch docs-configuring-chores in repository https://gitbox.apache.org/repos/asf/superset.git
commit 090776617519c13f0cdb547fe145edc9ee5c24c2 Author: Sam Firke <[email protected]> AuthorDate: Fri Apr 26 09:12:39 2024 -0400 add closing ::: to caution tag --- docs/docs/configuration/configuring-superset.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docs/configuration/configuring-superset.mdx b/docs/docs/configuration/configuring-superset.mdx index 8247348fe1..b9b46c050b 100644 --- a/docs/docs/configuration/configuring-superset.mdx +++ b/docs/docs/configuration/configuring-superset.mdx @@ -99,9 +99,9 @@ SECRET_KEY = 'YOUR_OWN_RANDOM_GENERATED_SECRET_KEY' You can generate a strong secure key with `openssl rand -base64 42`. -:::caution Your secret key will be used for securely signing session cookies -and encrypting sensitive information stored in Superset's application metadata database. - Make sure you are changing this key for your deployment with a strong key. +:::caution Use a strong secret key +This key will be used for securely signing session cookies and encrypting sensitive information stored in Superset's application metadata database. +Make sure you are changing this key for your deployment with a strong key. ::: #### Rotating to a newer SECRET_KEY
