On Apr 19, 2011, at 12:45 AM, Matt Harrison wrote:
To me, it seems that if I go in and fiddle with the controller
inside devise,
then I'll end up with my own fork essentially and have to maintain
that as well as my
application.
Does anyone have any insights or tips concerning this?
If you're in Rails 3, the Devise controllers may be extended in your
code, so you don't have to fork or unpack the gem into your
application. I haven't done this yet, but it's supposed to be one of
the big improvements over Rails 2.3 and its equivalent Devise. You
could also monkey-patch any part of Devise that wasn't actually being
handled inside Warden, if you needed to maintain a few changes. That
would require you to keep track of your changes along with upgrading
Devise, but it's probably less trouble than a full-on fork.
Walter
--
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
