i'm actually not sure now what was the effect of this. i assumed it wouldn't make us re-login after a re-deployment, but i didn't have to login again after changing the option to db🤔
https://forgejo.org/docs/latest/admin/config-cheat-sheet/#session-session
i'm actually not sure now what was the effect of this. i assumed it wouldn't make us re-login after a re-deployment, but i didn't have to login again after changing the option to `db` 🤔
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
https://forgejo.org/docs/latest/admin/config-cheat-sheet/#session-session
i'm actually not sure now what was the effect of this. i assumed it wouldn't make us re-login after a re-deployment, but i didn't have to login again after changing the option to
db🤔Nice 😍
@@ -38,6 +38,7 @@ GITEA_ENABLE_PUSH_CREATE_USER=falseGITEA_ENABLE_PUSH_CREATE_ORG=falseGITEA_LFS_START_SERVER=falseGITEA_MAX_CREATION_LIMIT=-1GITEA_SESSION_PROVIDER=memoryShould we set the default to db?
Yes please, think of the children! All those logins, all those moments in time. Lost, forever.
done!