From 901e9a1fac4f737f2668e03a0ab0201f1642df99 Mon Sep 17 00:00:00 2001 From: catborise Date: Fri, 6 Nov 2026 15:20:45 +0300 Subject: [PATCH] docs(readme): an update from an old installer moves the secret key into a new data/ Installers up to September 2026 wrote SECRET_KEY into settings.py and made no data/ directory. Step 2 said that leaving the key out signs every user out; in fact the template then has no key at all: migrate in step 3 stops with "The SECRET_KEY setting must not be empty" and every page answers 500. The step now says to create data/ first and what happens without the key. Checked on an installation of the upstream release of September 2026 upgraded to this version, with data/secret_key moved away and back. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 34daae0b..1832a9e9 100644 --- a/README.md +++ b/README.md @@ -635,7 +635,7 @@ Move the `environment=` values of that config into `/etc/default/webvirtcloud` ( ``` Typical ones are `TIME_ZONE`, `WS_*`, `ALLOWED_HOSTS`, `CSRF_TRUSTED_ORIGINS` and LDAP. Two need care: - - a literal `SECRET_KEY = "..."` (older installers wrote it there): put the value into `data/secret_key` instead, or every user is signed out; + - a literal `SECRET_KEY = "..."` (older installers wrote it there): put the value into `data/secret_key` instead (`mkdir -p data` first if there is no `data/`). With no key, `migrate` in step 3 stops with "The SECRET_KEY setting must not be empty" and every page fails; with another key, every user is signed out; - `SHOW_PROFILE_EDIT_PASSWORD`: keep it for this one `migrate` if you have it (migration `accounts.0008` reads it), then delete it. 3. Install, migrate, and fix ownership and modes (`nginx:nginx` instead of `www-data:www-data` on RHEL / openSUSE). With LDAP, also run `venv/bin/pip3 install -U -r conf/requirements-ldap.txt` (headers: [LDAP](#ldap)):