Open
Conversation
configure redis store for session storage clean lint debug debug debug
Member
|
yes, i would try to display something first. I'll review after we have something working in the front-end |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #135
Session storage should not be handled in-memory for production environments. It seems that using
connect-redisis a common solution. I've implemented it here. However, I'm not sure it's working correctly; the front end is still broken enough that it's hard to tell.Reference:
Take a look, see if it makes sense. I say we get the front-end up to a working condition, then merge in this PR to see if it still works.