3 ms·
Configuration is usually very minimal. It might be as little as nothing to editing 2 lines in a single config file. It depends on what you want to do of course
by rartichoke 13y ago
Configuration is usually very minimal. It might be as little as nothing to editing 2 lines in a single config file.
It depends on what you want to do of course. A lot of the following behind devise is due to how well it deals with all of the ceremony involved with standard authentication.
Everything from sending out e-mails, password resetting, failed login constraints and all of that stuff. It's nice to be able to hook in a gem and perform minor configuration to get all of that with no fuss.
In your example of only having to auth with github then yeah, I wouldn't use devise either because it's so basic. Omniauth is what I would use in that case. I would see that as a toy example too because more often than not you'll want much more than just auth'ing through a third party site.
- davedx 13y agoI must have been doing something very wrong then. I was using Device and Omniauth in a Rails 3 project, and sure enough, it was very straightforward to get it working. Then I upgraded to Rails 4, and all hell broke loose. I'm sure that, given enough time and patience, I could have figured out which methods, controllers and models I needed to write, and what to put in the config files, but it felt like a major regression convention-over-configuration. Compared to meteor (type 'meteor add accounts-github' and add {{loginButtons}}) it was really painful.