In this post, I want to share my experiences in using Devise as an authentication solution for my company’s Web app.
While building Motonow, the team had to make a couple of though decisions and choosing the right authentication solution was one of them. To be honest, most of the projects I’ve joined had already overcome this phase so I’ve never participated in such conversations until Motonow.
After doing some prototypes, we’ve decided to use Devise because:
- It has most of the features we want to implement already in place;
- It’s really straightforward to start with;
- It’s well documented;
- It’s widely adopted in the Rails community;
Everything was going well until the domain model started to grow in the sense that Devise’s basic configuration was not enough for us. At that point, we needed to extend Devise, more specifically the RegistrationsController.
At the beginning we only had a User model so integrating with devise was pretty easy…
View original post 522 more words