Don't lose session data when upgrading GKE pods/containers #17
Labels
No Label
bug
dev environment
docs
duplicate
enhancement
feature
idea
invalid
kredits-1
kredits-2
kredits-3
ops
question
security
ui/ux
wontfix
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/gitea.kosmos.org#17
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Fixed by adding this to the session section of the
app.ini
: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?
Nice find. 👍