Authlogic gotchas
I know, nobody uses Authlogic anymore. But for those few who do, here are two tips which can save you a massive headache.
Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!
I know, nobody uses Authlogic anymore. But for those few who do, here are two tips which can save you a massive headache.
Comments
What do they use instead?
I’ll 2nd that question. What else to use?
Devise
Devise is too opinionated and the controller actions in the engine just obfuscate things and more often than not need to be overridden. Authlogic still has a place.
Is there a link where the available options are discussed? Another thing i’ve seen but never used is Clearance.
Sorcery is a newcomer that’s worth a look. It was created to plug the gap that the lack of updates to Authlogic is causing but is otherwise similarish.. https://github.com/NoamB/sorcery
Sorry for not linking properly, stuck on iPad..
I’m a Devise user, myself, but this Railscast is also worth looking at.
Now I’m on a real computer, https://github.com/NoamB/sorcery:
From the page..
Sorcery aims to make your life easier by giving you an easy API to write your own user authentication flow with. It does this with a few goals in mind:
Less is more - less than 20 simple methods to remember for the entire feature-set make the lib easy to ‘get’.
No built-in or generated code - use the API inside your own MVC structures, and don’t fight to fix someone else’s.
Magic yes, Voodoo no - the lib should be easy to hack for most developers.
Configuration over Confusion - Simple & short configuration as possible, not drowning in syntactic sugar.
Keep MVC cleanly separated - DB is for models, sessions are for controllers. Models stay unaware of sessions.
..
Anyone tried it yet?
Post a comment