Open jacek99 opened 9 years ago
Couldn't agree more!
I'll have a look at implementing this.
preferably the session handling should be pluggable to be in-memory if single server and then allow pluggable DB backends (e.g. Redis, Cassandra, etc) when dealing with a multi-server setup behing a load balancer.
We cannot always count on sticky sessions at the load balancer levels.
Thanks!
Any updates on implementing sessions into nickel?
Is this implemented yet?
@cydrobolt we have https://github.com/nickel-org/session and https://github.com/nickel-org/cookies and I'm using them in production.
One thing to note is that they are not on cargo so you have to do the following
[dependencies.nickel_cookies]
git = "https://github.com/nickel-org/cookies.git"
[dependencies.nickel_session]
git = "https://github.com/nickel-org/session.git"
We don't have something polished for Auth so yet.
Is Auth available now ?
Auth is still somewhat a roll your own situation yet. I have a crate, https://crates.io/crates/websession, which I use for authentication. The documentation for how to use it with nickel isn't really there yet, though. I am inclined to think Auth ought to be a separate crate from nickel.
It would be great if the default middleware included an out of the box solution for authentication and session handling.
That seems to be the most missing part in order to get an actual production grade app written in Nickel