It depends what type of use your authentication system will have and on what level you want to use it. If you only want auth for users accessing your rails app through your views then clearance is a great option. It is much simpler than devise as far as design goes since it basically just writes classic controllers that are then included in your Controller class. However if you want the auth to actually be in the rack middleware then devise is a good choice. Since it sits in the middleware it gives you the option of using the auth in front of any additional resources you want to put in the middleware. It really depends on your use case.
I have a project using devise because we have some custom rack code that handles serving large files and with devise we can have auth in front of those resources. I also have some another project that uses clearance because there is no need for middleware based auth and the simplicity and ease of setup for clearance was much appreciated. On Jan 14, 11:09 am, Rob Kaufman <[email protected]> wrote: > That's the one that I use (though I have a branch of it) > > Rob > > > > > > > > On Thu, Jan 13, 2011 at 21:30, John Lynch <[email protected]> wrote: > > Kevin, if you look on github there are loads of them, for example this > > one has the most watchers/forks... > > >https://github.com/dcrec1/rails3_template > > > - john > > > On Thu, Jan 13, 2011 at 7:22 PM, Kevin Baker <[email protected]> wrote: > > > Can I ask where you are finding the Rails 3 Templates you referred to? > > I'm > > > building one soon to bootstrap my app.... I'd like to build some sort of > > > base template/recipe's for the sort of applications we are creating. > > > > On Thu, Jan 13, 2011 at 1:12 PM, Rob Kaufman <[email protected]> > > wrote: > > > >> My current personal preferences: > > >> devise > authlogic # Less do it your self, but actually more > > customizable > > >> cancan > other options # Seems like the best for authorization > > >> minifb > facebooker # I haven't used facebookr2 or koala, but have had > > >> good luck with minifb > > > >> These are of coure preferences, not absolutes, but I will say that > > devise > > >> can use the same encryption as many other login gems which makes moving > > to > > >> it easy, and its a great replacement for apps that where merb and used > > >> merb-auth. Also it seems to be very very common in the various Rails 3 > > >> templates, which says a lot of good things about it. > > >> Best, > > >> Rob > > > >> On Thu, Jan 13, 2011 at 11:24, Rafael MVC <[email protected]> wrote: > > > >>> I would stir away from facebooker. The original facebooker uses the old > > >>> facebook API, and koala or facebooker2 uses graph. In my own opinion, > > >>> facebooker2 is more complex than Koala... > > > >>> On Thu, Jan 13, 2011 at 7:39 AM, Dan Simpson <[email protected]> > > >>> wrote: > > > >>>> For authorization I would look athttps://github.com/ryanb/cancan > > >>>> There is alsohttps://github.com/kristianmandrup/creamwhich combines > > >>>> devise, cancan, and roles to make a authentications/authorization > > suite. > > >>>> The rake tasks should generate some nice templates. > > > >>>> On Wed, Jan 12, 2011 at 10:28 PM, Kevin Baker <[email protected]> > > >>>> wrote: > > > >>>>> I'm starting a new project. Want to build in Rails 3. I thought it > > >>>>> might be a good time to look at devise. > > > >>>>> Is this *the* way to go these days? If not I'll stick with authlogic. > > > >>>>> Some details: > > >>>>> Anything special for devise in rails 3 I should know. > > > >>>>> I will need some sort of permissions/authorization gem. > > > >>>>> I'm thinking of adding openid, facebook etc integration. > > > >>>>> I'd love some tips on bootstrapping, app template? > > > >>>>> Thanks > > > >>>>> -- > > >>>>> SD Ruby mailing list > > >>>>> [email protected] > > >>>>>http://groups.google.com/group/sdruby > > > >>>> -- > > >>>> SD Ruby mailing list > > >>>> [email protected] > > >>>>http://groups.google.com/group/sdruby > > > >>> -- > > >>> SD Ruby mailing list > > >>> [email protected] > > >>>http://groups.google.com/group/sdruby > > > >> -- > > >> SD Ruby mailing list > > >> [email protected] > > >>http://groups.google.com/group/sdruby > > > > -- > > > SD Ruby mailing list > > > [email protected] > > >http://groups.google.com/group/sdruby > > > -- > > SD Ruby mailing list > > [email protected] > >http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
