it depends. the last project that I started that required facebook registration, I used devise because it's omniauth integration made that ridiculously easy...like I didn't really have to do anything.
since then, I've only started apps that needed local auth. in these cases I've used authlogic + the requisite rails 3 money patches (c/f railsplugins.org). expect lots of deprecation warnings. devise is fabulous, but it takes "convention over configuration" to a horrifying new level. IMO: use authlogic unless using devise will save you a ton of time upfront. On May 6, 2011, at 10:53 PM, Guyren Howe <[email protected]> wrote: > On May 6, 2011, at 10:17 PM, Neal Clark wrote: > >> that describes my experience with devise as well. it's great until you need >> to customize something, which is... always. my love for devise expires when >> there's a rails 3 compatible 'official' release of authlogic. >> >> On May 6, 2011, at 10:08 PM, Jason King <[email protected]> wrote: >> >>> >>> On May 6, 2011 8:12 PM, "Guyren Howe" <[email protected]> wrote: >>> > >>> > Everyone loves devise. But it’s killing me right now. >>> >>> I don't. After working with it for a few days I'd overridden so many >>> methods that I don't think there was actually any devise left. I'm using >>> straight warden now and loving it. >>> >>> Devise is a ghetto. There, I've said it ;) >>> > > So what is the best solution for authentication in Rails 3 now? > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
