1

My question here is about the proper way to do the routing and controllers for my simple app. Honestly I got stuck with the User model and Post model.

I've got it routed like this:

match '/dashboard', to: 'dashboard#user'

In the controller it takes the session uid to find the user and his posts (the posts and user profile are completely private to the user). So far dashboard serves its purpose. The question is where do I go from here? Posts are shown in the same view as the posts list. For the editing/updating and creating I would like my routes to be /dashboard/posts/:id.

This would point me to using a resource. Finally: Is using scope '/dashboard' or path: '/dashboard/posts' a good approach, or is it against "the Rails Way"? Or do I have a completely wrong idea what's going on here?

I'm afraid of completely messing up the code and repeating myself over and over again (as in authentification, and keeping the routes clean).

Anton
  • 137
  • 8

2 Answers2

3

You could either use a namespace or nested resources, like this:

Namespace

#config/routes.rb
namespace :dashboard do
  root to: "users#index"
  resources :posts, :comments
end

#app/controllers/dashboard/users_controller.rb
Class UsersController < Dashboard::ApplicationController.rb
end

Nested

#config/routes.rb
resources :user, path: "dashboard", as: "dashboard" do
  resources :ads
end
Richard Peck
  • 76,116
  • 9
  • 93
  • 147
  • Thank you for your answer. I just wanted to ask: is it still a good approach when I'm using only the `#dashboard` method? I know this can be done by using `only: :index`, but I'm not really using the resource here. Would you recommend using the namespace then? – Anton Feb 18 '14 at 23:05
  • 1
    I'd totally recommend the namespace method, as it is extensible. Using a nested resource gets messy -- having a namespace means you have a totally separate section to you app. Here's where I leant how to do it: http://iain.nl/backends-in-rails-3-1 – Richard Peck Feb 19 '14 at 09:05
1

I'm a fan of explicitly naming all routes for security and clarity on what routes are out there. So for your case doing something like:

#Dashboard
get '/dashboard', to: 'dashboard#user', as: 'dashboard'
get '/dashboard/posts/:id', to: 'posts#show', as: 'post'

#Posts
get '/dashboard/posts/:id', to: 'posts#new', as: 'new_post'
post '/dashboard/posts/:id', to: 'posts#create', as: 'create_post'
put '/dashboard/posts/:id', to: 'posts#update', as: 'create_post'

More info at http://guides.rubyonrails.org/routing.html

Jake
  • 383
  • 6
  • 26
  • Thank you, I will surely consider this approach in my work. I also wanted to thank you for pointing out the `put` method, I was sticking to `match` so much I forgot there's actually a method for patch/put verb! – Anton Feb 18 '14 at 23:08