Question

Users can view and edit account information in my app using UsersController

This controller only ever shows information about the current user.

I want to adjust the routes so that:

• get /account accesses UsersController#show, user_id is retrieved from a current_user variable

• get /account/edit similarly accesses UsersController#edit

• put /account/ will hit UsersController#update, again using current_user instead of an ID

Basically I want to refer to UsersController as ‘account’ in my URLs and I don’t want to use IDs because I’m always just using the current user. I also don’t want URLs like /users/1 to function at all.

How can I achieve this?

Answer 1

I think that you are talking about singular resources.

http://guides.rubyonrails.org/routing.html#singular-resources

# Not sure if you need this
resource :users, :only => [:index, :create, :destroy]    

# This is what you are looking for
resource :user, :as => :account, :only => [:show, :edit, :update]

Update

Since you need “/account” instead of “/user”, you should do

resource :account, :controller => :users, :only => [:show, :edit, :update]