e5a62d8f10
New [user.retention] TOML sub-block with auto_close_days and auto_delete_days. Both default to 0, which disables the respective sweep — a conservative default that preserves current behaviour for existing deployments and lets admins test auto-close in isolation. Only parsing + the test User literals are touched here; the actual lazy sweep consuming these values lands in the next commit.
24 lines
771 B
TOML
24 lines
771 B
TOML
# Generate a bcrypt hash for `web_password` e.g. via:
|
|
# python3 -c "import bcrypt; print(bcrypt.hashpw(b'your-password', bcrypt.gensalt()).decode())"
|
|
# or:
|
|
# htpasswd -bnBC 12 '' your-password | tr -d ':\n'
|
|
|
|
[[user]]
|
|
slug = "dr_mueller"
|
|
api_key = "change-me-to-a-secure-key"
|
|
web_password = "$2b$12$..."
|
|
role = "doctor"
|
|
# Optional per-user retention. Both fields default to 0 (feature
|
|
# disabled). auto_close_days = 7 + auto_delete_days = 30 means cases
|
|
# without new recordings auto-close after 7 days and are irreversibly
|
|
# removed 30 days later. Changes require a server restart.
|
|
[user.retention]
|
|
auto_close_days = 7
|
|
auto_delete_days = 30
|
|
|
|
[[user]]
|
|
slug = "dr_schmidt"
|
|
api_key = "change-me-to-a-secure-key"
|
|
web_password = "$2b$12$..."
|
|
role = "doctor"
|