I wrote a plugin for dealing with logins a few years ago at a company I worked for. One thing I had was the ability of an admin account to login as another user so you could see that users views and manage their accounts. Perhaps I should have used a standard rails plugin, but I wasn''t sure how to accomplish the same thing that way and would have had to figure out the inns and outs of the plugin. I had to write my own code, but if I needed to make changes to do various odd things in the future I was somewhat more familiar with the plugin. It also got me to get a feel for how to write a plugin so it seemed like a good thing for me in a way, yet I still suspect some people may think it''s not such a good thing to write your own authentication (although alot of rails books have examples of sessions and so on with login etc) I need to revisit this however as I am not sure if I mention it in a job interview if it would be considered a plus that I wrote a plugin or a negative that I didn''t use one of the standard ones. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Peter Vandenabeele
2012-Feb-16 08:44 UTC
Re: Rails authentication versus writing your own plugin
On Thu, Feb 16, 2012 at 9:31 AM, Jedrin <jrubiando-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > I wrote a plugin for dealing with logins a few years ago at a company > I worked for. One thing I had was the ability of an admin account to > login as another user so you could see that users views and manage > their accounts. Perhaps I should have used a standard rails plugin, > but I wasn''t sure how to accomplish the same thing that way and would > have had to figure out the inns and outs of the plugin. I had to write > my own code, but if I needed to make changes to do various odd things > in the future I was somewhat more familiar with the plugin. It also > got me to get a feel for how to write a plugin so it seemed like a > good thing for me in a way, yet I still suspect some people may think > it''s not such a good thing to write your own authentication (although > alot of rails books have examples of sessions and so on with login > etc) > > I need to revisit this however as I am not sure if I mention it in a > job interview if it would be considered a plus that I wrote a plugin > or a negative that I didn''t use one of the standard ones. > >As may be obvious from my tag line, I am there too. I see a lot of positions that require knowledge of Devise (and CanCan). So, I suggest you use Devise and fork it where you need additional features (and send Pull Requests if the feature could be generally useful). I think that is the strongest argument: use what is there and continue to build on top. Not the easiest solution, but surely the strongest one. HTH, Peter -- *** Available for a new project *** Peter Vandenabeele http://twitter.com/peter_v http://rails.vandenabeele.com http://coderwall.com/peter_v -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.