Alpha Blue wrote in post #972991: > devise and that's it for me. With Rails 3, engines are the new thing > and everything I need to keep in an application, is now a part of my > engine. > > Devise is one of the best authentication systems I've found around. > Very clean and modular. > > For permissions/authorizations I developed my own system which is a > bitfields permission system. I used to use cancan, but it lacked what I > needed and that was a way to assign authorization to any object within > my application.
rails-authorization will do this, if I understand your use case correctly. I'd avoid bitfields myself. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] Sent from my iPhone -- Posted via http://www.ruby-forum.com/. -- 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.
