v0.35.2

0.35.2

A single fix, for sessions dropping when no SECRET_KEY is configured.

Fixed

• Running without SECRET_KEY set 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_key in its data folder, so all of its worker processes sign sessions with the same key and logins survive a restart. Setting SECRET_KEY yourself 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.yml passes a placeholder SECRET_KEY, so Compose users get that rather than a generated key until they set one of their own or remove the line.
• .env.example shows SECRET_KEY as optional and commented out.

Thanks to the reporter of #317 for the details that pinned this to gunicorn's separate worker processes.