Answer the question
In order to leave comments, you need to log in
What is the best way to implement authorization for a large project?
Hello. What is the best way to implement authorization for a future scalable project? Write by hand or use some kind of gem? With devise already suffered when trying to customize.
Here's what you need:
1. Basic registration.
2. Authorization by email and password.
3. Password recovery by email.
4. Editable user profile.
Answer the question
In order to leave comments, you need to log in
Devise is very easy to customize. Never really had a problem with it. And it is displayed in a modal window, and Ajax authorization is easily done, and authorization through mobile applications is painless.
Maybe before reinventing the wheel you can say what exactly you can’t customize?
Write your own, I don’t see anything extraordinary, cut api right away.
If it is highly scalable, then it actually does not hurt to immediately put into it a semblance of a separate service for authorization in all components.
In general, the similarity of what we now have on Habré, etc. -TM.id
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question