Update settings/admin UI and misc fixes
This commit is contained in:
17
README.md
17
README.md
@@ -56,6 +56,15 @@ The player keeps itself up-to-date automatically:
|
||||
|
||||
This project includes a simple **forgot password** flow. SMTP configuration is read from environment variables.
|
||||
|
||||
You can also configure SMTP settings from the UI: **Admin → Settings**.
|
||||
Environment variables still take precedence over the database settings.
|
||||
|
||||
### Public domain for emails
|
||||
|
||||
If your app runs behind a reverse proxy (or the internal hostname differs from the public hostname),
|
||||
set **Admin → Settings → Public domain** to e.g. `signage.example.com` so links in password reset
|
||||
emails point to the correct address.
|
||||
|
||||
Recommended: put these in a local `.env` file in the repo root. Flask (via `python-dotenv`) will auto-load it on startup. `.env` is already gitignored.
|
||||
|
||||
You can start from `.env.example`:
|
||||
@@ -81,6 +90,11 @@ REM Option B: put the same keys/values in a .env file instead
|
||||
|
||||
Security note: do **not** commit SMTP passwords to the repo. Prefer secrets management and rotate leaked credentials.
|
||||
|
||||
Note on the "From" address: some SMTP providers enforce that the authenticated mailbox
|
||||
(`SMTP_USERNAME`) is used as the actual sender (envelope-from), even if a different
|
||||
`SMTP_FROM` is provided. In that case the app sets a `Reply-To` header so replies still
|
||||
go to `SMTP_FROM`, but the provider may still show the username address as the sender.
|
||||
|
||||
### Troubleshooting mail delivery
|
||||
|
||||
If the reset email is not received:
|
||||
@@ -104,3 +118,6 @@ If the reset email is not received:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user