Hi Dave, Thanks for the quick reply. I'll give CanCan a go as from what I've read it should cover most everything I need for role auth.
Todd On Jan 12, 10:35 am, Dave Aronson <[email protected]> wrote: > On Thu, Jan 12, 2012 at 12:29, tmueller <[email protected]> wrote: > > I am new to Rails and wanted to ask some of the veterans here what > > they recommend for Role based permissions. > > It depends on a number of factors. If this is a "real thing" for > work, or that you intend to put out for public use, definitely just go > with CanCan. (Or possibly one of the alternatives. CanCan does seem > to be the most popular though.) > > On the other claw, if you're just playing, do it with CanCan (or, > again, some alternative) the *first* time. That way, you get the idea > how that sort of thing generally works. *After* that, though, it can > be quite a good learning experience to try to duplicate the > functionality yourself. Meanwhile, having learned CanCan can't hurt > either. :-) You could separate the authorization checks into some > wrapper class that would, under the hood, initially call CanCan, but > then you can remove CanCan (kick the CanCan?), and see what you have > to do to make the app work again. I suggest having particularly good > test coverage in that piece, so you know you've got it working right. > > -Dave > > -- > Dave Aronson, President, Dave Aronson Software Engineering and Training > Ruby on Rails Freelancing (Northern Virginia, Washington DC, or Remote) > DaveAronson.com, Codosaur.us, Dare2XL.com, & RecruitingRants.com (NEW!) > Specialization is for insects. (Heinlein) - Have Pun, Will Babble! (me) -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
