0.35.2
A single fix, for sessions dropping when no SECRET_KEY is configured.
Fixed
- Running without
SECRET_KEYset no longer bounces you back to the login page on every page change. May generates a key on first start and saves it to.secret_keyin its data folder, so all of its worker processes sign sessions with the same key and logins survive a restart. SettingSECRET_KEYyourself still takes precedence and is never written to disk; if the key file cannot be written, May starts as before with a warning. (#317)
Other
- The README's configuration section now notes that the supplied
docker-compose.ymlpasses a placeholderSECRET_KEY, so Compose users get that rather than a generated key until they set one of their own or remove the line. .env.exampleshowsSECRET_KEYas optional and commented out.
Thanks to the reporter of #317 for the details that pinned this to gunicorn's separate worker processes.