💾 feat: Production-ready Memory Store for express-session
#5212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
express-session
library comes with a session storage meant for testing by default. That is why you get a message like this when you start up LibreChat with OIDC enabled:LibreChat can already use Redis as a session storage, although Redis support is still marked as experimental. It also makes the set-up more complex, since you will need to configure and run yet another service.
This pull request provides a simple alternative by using a in-memory session store marked as a production-ready alternative by the guys from
express-session
¹. You can still configure Redis, but this provides a simple, good default for everyone else.See also #1014
¹⁾ https://github.com/expressjs/session?tab=readme-ov-file#compatible-session-stores
Change Type
Please delete any irrelevant options.
Testing