You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to run on a "cloud" the session support should store sessions in some remote db, that each instance of the wiki can access. I don't see any code to do that today.
As an example, I might want to use something like this to store my session in mongo, prolly same db as my pages, different collection.
Thoughts?
The text was updated successfully, but these errors were encountered:
Found a reference to "cookie sessions", where the session data is stored in the cookie, as opposed to some store. Downside is that you can't store that much data in there - doesn't seem to be a problem with wiki. Upside is you don't need a store - the cookie IS the store.
This seems like potentially useful node package to handle these:
So far we've only had many wikis running on one server, not one wiki running on many servers, so we haven't really felt the pressure to figure out a good solution. The db was a non starter, with the overhead it adds to setup. I agree that now that we have support for pages in dbs that it would work to have a session store in the same db, but we are not well setup to do that.
The mozilla cookie session store looks to be quite slick, and should be a drop in replacement. I can't see any disadvantages for our limited usecase, unless anyone else can I'd love to see a pull request for it.
to run on a "cloud" the session support should store sessions in some remote db, that each instance of the wiki can access. I don't see any code to do that today.
As an example, I might want to use something like this to store my session in mongo, prolly same db as my pages, different collection.
Thoughts?
The text was updated successfully, but these errors were encountered: