From e1462c915c454dee49f526011acc14e09dfa630b Mon Sep 17 00:00:00 2001 From: liss-bot Date: Sun, 2 Jun 2024 01:30:20 +0000 Subject: [PATCH] Auto Publish new pages --- authentication.md | 2 +- credits.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/authentication.md b/authentication.md index d7189b3..7cf49a2 100644 --- a/authentication.md +++ b/authentication.md @@ -152,7 +152,7 @@ With basic auth, all logic is happening on the client-side, which could mean a s If you'd like to protect all your config files from direct access, you can set the `BASIC_AUTH_USERNAME` and `BASIC_AUTH_PASSWORD` environmental variables. You'll then be prompted to enter these credentials when visiting Dashy. -Then, if you'd like your frontend to automatically log you in, without prompting you for credentials, then also specify `VUE_APP_BASIC_AUTH_USERNAME` and `VUE_APP_BASIC_AUTH_PASSWORD`. This is useful for when you're hosting Dashy on a private server, and you want to prevent unauthorized access to your config files, while still allowing the frontend to access them. Note that a rebuild is required for these changes to take effect. +Then, if you'd like your frontend to automatically log you in, without prompting you for credentials (insecure, so only use on a trusted environment), then also specify `VUE_APP_BASIC_AUTH_USERNAME` and `VUE_APP_BASIC_AUTH_PASSWORD`. This is useful for when you're hosting Dashy on a private server, and just want to use auth for user management and to prevent direct access to your config files, while still allowing the frontend to access them. Note that a rebuild is required for these changes to take effect. **[⬆️ Back to Top](#authentication)** diff --git a/credits.md b/credits.md index 52248ce..9494951 100644 --- a/credits.md +++ b/credits.md @@ -91,10 +91,10 @@ - - vlad-timofeev + + vlad-tim
- Vlad Timofeev + Vlad