Don't lose session data when upgrading GKE pods/containers #17

New Issue

2019-02-13T04:31:36Z

raucao commented

2019-02-13 04:31:36 +00:00

After upgrades to the GKE pods, one has to log in again, so it would seem that session data is stored in the pod's own storage instead of the persistent volume.

raucao added the enhancement label 2019-02-13 04:31:36 +00:00

greg commented

2019-04-02 09:38:08 +00:00

Fixed by adding this to the session section of the app.ini:

PROVIDER = file
PROVIDER_CONFIG = /data/gitea/sessions
COOKIE_SECURE = true

I also enabled only secure cookies while I was at it

The default is in memory so that's why we were losing sessions. The docs mention a mysql adapter, but it's not in 1.7.5, maybe they'll add it in 1.8?

Fixed by adding this to the session section of the `app.ini`: ``` PROVIDER = file PROVIDER_CONFIG = /data/gitea/sessions COOKIE_SECURE = true ``` I also enabled only secure cookies while I was at it The default is in memory so that's why we were losing sessions. The docs mention a mysql adapter, but it's not in 1.7.5, maybe they'll add it in 1.8?

greg closed this issue

2019-04-02 09:38:08 +00:00

raucao commented

2019-04-02 12:28:49 +00:00

Nice find. 👍

Nice find. :+1:

This repo is archived. You cannot comment on issues.

2 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/gitea.kosmos.org#17