Restful_authentication vs. Authlogic
ruby, ruby-on-rails
Solution
Actually I'd disagree with fig-gnuton. There are a couple of things that you could do. If you want a basic solution try restful auth but be aware that the generator based approach has significant shortcomings. The main shortcoming is that you are squirting a large gob of code into your application. So when there's an issue you have to patch the code manually or blow away any customisations you've made. Recent versions of restful auth are much better than earlier versions which spewed code left, right and centre but my advice would be where possible leave the user and session code generated by restful auth well alone. For example if you want properties on your User make another object like Person and link the two.
I prefer authlogic because:
- It feels like you're more in control.
- I appreciate the extent to which authlogic is documented and their example app is pretty useful as a guide too.
- Also I've had bother with testing restful_auth apps, not so with authlogic.
- Extensions like forgotten password resets, API keys and the like are much less custom code than restful_auth.
Problem
what do you recommend? Authlogic or restful_authentication? Is it hard, to build the email-activation-step into authlogic (as far as I know, Authlogic hasn't this feature included).