views:

35

answers:

1

So in Rails2 you could setup a route like this:

resources :users, :as => 'members'

This way you still have your users_path but it matches /members

Now, how do you go about doing this in Rails3? :as parameter here means totally different thing and I can't find what makes it work as before.

+1  A: 

I think what you're looking for is the :path option:

resources :users, :path => 'members'

Tested it on my app and the users_path still works, but matches /members as required. It doesn't match /users.

Matt