Add more session adapter about superlogin

[colinskow]

Merged #57 Closing

[micky2be]

Even for development purpose, saving the session in file might be slightly better then memory.
At least the session would be able to persist.

[colinskow]

Thank you for PR #57

[ichagas]

It sounds like expensive $1,450/mo for up to 5,000 connections on Heroku Redis. Any idea what does it means in the real world?

I am considering to use Superlogin for auth PouchDB <-> Cloudant since PouchDB Authentication is not Cloudant compatible.

But I see a risk to receive a large $$ bill to pay if the App get about 30K users or so. Of corse, I can run my own Redis Server but I prefer a Backendless approach this is why PouchDB/Cloudant approach.

[colinskow]

@ichagas you can use whatever Redis service you want with Heroku, including Amazon. Just plug in the access credentials to the correct environment variables. You can see superlogin-demo for an example.

Redis usage is extremely light, and I think you could expand quite a bit using the free version. One Heroku client only uses one connection. Each session is less than 500 bytes of info.

In my experience the Cloudant bill is what you have to worry about with lots of users.

[DimShadoWWW]

@ichagas I was adding etcd and firebase as backend (in my fork) .. but haven't test it yet

[ichagas]

@DimShadoWWW, let me know when you have time to test the Firebase version, sounds a good idea.

@colinskow, as I understood, superlogin will use only one Redis connection no matter what is the number of users?
Btw, 👍 thanks for your insides on the Cloudant. I am going to review this decision and prepare a plan B to implement as soon as the App launch. Perhaps use DigitalOcean for CouchDB+Redis could be cheaper solution. Anyhow, I am moving on now and review it later.

Thanks.

[DimShadoWWW]

@ichagas 👍