Thanks for the tip on flash messages Ben, I'll check that out as part of process of elimination. I really like Devise as it eliminates a lot of boilerplate I'd have to write myself for forgotten email, rememberable, confirmation, etc.
I've never used memcache before, so that's only reason I didn't jump on it. I assume it will be v straightforward integrating it as with the rest of the Rails solutions. I got auth working with password_digest following railscasts wire it yourself, v flexible, easy but doesn't provide solution for email confirmation, forgotten email or password, etc. Is there any performance benefit or deficit using memcache for session store vs cookies? Right up till that overflow Devise flowed v nice, I generated views for the model to have more flexibility in display for customer login vs admin login, its a v solid solution and seems to be most popular for authentication in ruby world. On Sunday, April 6, 2014 4:52:24 PM UTC-7, Benjamin Wanicur wrote: > > I realized my previous post was a bit outdated in my assumptions. I think > Rails 4 is using the cookie storage as default for the session, so I > realize the 4k limit applies to the session. My multi-user login app > (Devise) was using memcache for session storage. So I believe just the > session id is stored in the cookie. I think if you like Devise, using the > memcache session storage is very easy to set up. I would probably go that > route if I was in your shoes. > > One other possible gotcha is that the flash content is stored in your > session storage, so mayhaps that is pushing you over your 4k limit ? I’m > really just guessing on that. Just one other thing you can check. > > On April 6, 2014 at 4:26:55 PM, Abiding Dude ([email protected]<javascript:>) > wrote: > > I posted this on the Devise group also, maybe there's a workaround to > avoid having to use the db as a store. At a later point I'll switch to > memcache, but right now I'm not there with time to get familiar with it. > Memcache def on the roadmap though. I tried Rails 3 about a year ago and am > just now returning to Rails as main dish, and am finding version 4 to be > really smooth, almost no surprises/gotchas. Quite a pleasurable workflow. > -- > -- > SD Ruby mailing list > [email protected] <javascript:> > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups > "SD Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
