Thanks, this is just what I was looking for.
On Fri, Aug 27, 2010 at 6:17 PM, Errol Siegel <[email protected]> wrote: > I just happened to be looking for the same information. I found it > here: > > http://www.michaelharrison.ws/weblog/?p=349 > > To quote the relevant part: > > The solution is to give devise_for an alternate path to use for user > authentication, e.g. accounts: > > devise_for :users, :path => 'accounts' > > resources :users do > resources :someresources > end > > > It doesn’t matter what path you use, since devise is going to use its > own controller to handle authentication requests. > -- > Posted via http://www.ruby-forum.com/. > > -- > 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]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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.
