4 ms·
I think the defacto standard is devise but they want you to be flexible enough to roll your own or whatever serves you. I would like to have it built in though.
by hit8run 7y ago
I think the defacto standard is devise but they want you to be flexible enough to roll your own or whatever serves you. I would like to have it built in though.
- petepete 7y agoThis sounds about right. And if you want something in between without rolling your own, Sorcery is excellent. https://github.com/Sorcery/sorcery https://github.com/Sorcery/sorcery
- jjgreen 7y agoLooks interesting, thanks
- ken 7y agoI'm not familiar with recent versions of Rails or its authentication situation, but whenever I hear this said about some mandatory functionality of a system, it sounds to me exactly like "We haven't yet figured out how to do ___ well". It reminds me of the old days when I'd get a library which would say "We want to be flexible, so just pass in any memory allocation function here!", or Linux distros that said "We want to be flexible, so just write any boot script here!" Then a year later, some competitor ships with a default, and everybody switches over to that because it's obviously better (and you can always customize it if you need to). Especially so with Rails, whose entire existence seems to be picking good-enough defaults.