3 ms·
I recently started a rather large Rails project and am using Devise. Currently with authentication being pretty low on the list of things to do, it has helped g
by anonova 15y ago
I recently started a rather large Rails project and am using Devise. Currently with authentication being pretty low on the list of things to do, it has helped get something in place rather quickly. Can you expand on the disadvantages of using Devise over time (and maybe compare it to your experiences woth Sorcery)?
- Sapient 15y agoI haven't used sorcery, but I have just finished quite a large rails project in which I decided on Devise right at the start. It was great in the beginning, but as soon as I needed custom behavior, it became more of a liability than a help. Doing simple things like changing a redirect on sign up or sign in, and a few other customizations were chores, some of which required overriding core devise classes, and I am still not really happy with the fixes. If I were doing an app with standard model authentication, a Forum for example, I would use devise again in a heart-beat, but for any other project where I expect to have any slightly customized behavior at all, Ill be rolling my own. Devise is brilliant if you want something straight-forward, but it is big, complicated (internally), and not very flexible.