Rails Routes and excluding default routes

Question

I have a home controller which I am planing to use just for pages such as aboutus, contactus, or landing page etc. What is the best way to include this in the routes file that I do not get the default routes at all but do get to access each of the actions as a /[action] from the root of the site.

eg:

xyz.com/aboutus should take me to home#aboutus
xyz.com/contactus should take me to home#contactus

etc.

Are you looking for something like this `get '/patients/:id', to: 'patients#show'`? — Pavan, Jun 13 '14 at 09:19
I do not think I worded my question right. I want to be able to have the xyz.com/aboutus to show the content of the aboutus action under the home controller. — Qaiser Wali, Jun 13 '14 at 09:33

score 5 · Accepted Answer · edited May 23 '17 at 12:32

5

#config/routes.rb
resources :home, path: "", only: [] do
   collection do
      get :aboutus
      get :contactus
   end
end

Loop removed by @Sanket

This will create domain.com/aboutus etc for all your pages

--

DRY

Although this is what you want, a much DRYer way to get it to work is to do the following:

#config/routes.rb
resources :home, path: "", only: :show #-> domain.com/:id

This means you can then use a gem such as friendly_id to create a series of slugs for your pages, like this:

#app/models/page.rb
class Page < ActiveRecord::Base
    extend FriendlyId
    friendly_id :title, use: [:slugged, :finders]

    #fields
    id | slug | title | body | created_at | updated_at
end

#app/controllers/home_controller.rb
def show
   @page = Page.find params[:id]
end

If you just want to render the pages without the model:

#app/controllers/home_controller.rb
def show
   render "pages##{params[:id]}"
end

This will allow you to use the likes of domain.com/home/aboutus in the most DRY way

--

Caveat

A big caveat to this is if you're going to be using app-wide slugs, you need to put them at the bottom of your routes.rb file (so they will not interfere with other routes)

edited May 23 '17 at 12:32

Community

1
1

answered Jun 13 '14 at 09:18

Richard Peck

76,116
9
93
147

1

This is correct but do you think that it has more time-complexity. – Sanket Jun 13 '14 at 09:27
Yep I'm writing a better way to do it now :) – Richard Peck Jun 13 '14 at 09:27
the issue is I do not want to get the `domain.com/home/about`. I want to be able to go to `domain.com/aboutus` which should show the content of aboutus action user the home controller. – Qaiser Wali Jun 13 '14 at 09:31
i may sound like a complete fool here but this looks like too much work for something which does not even have a model in the background. Should I not use the `match` and add the info that way? – Qaiser Wali Jun 13 '14 at 09:39
Ignore my last comment. This works like a charm. Thanks. – Qaiser Wali Jun 13 '14 at 09:42
1

I also updated to include a system if you just had static pages (I.E no model) – Richard Peck Jun 13 '14 at 09:42

score 0 · Answer 2 · answered Jun 13 '14 at 10:06

0

You can just use https://github.com/thoughtbot/high_voltage a good gem for static pages.

answered Jun 13 '14 at 10:06

BGuimberteau

249
1
8

1

This also looks promising but why add a gem if something can be achieved with very few lines of code. – Qaiser Wali Jun 13 '14 at 10:25
this gem is very useful and complete to achieve this task. Not necessary to rewrite code exist. – BGuimberteau Jun 14 '14 at 08:01

Rails Routes and excluding default routes

2 Answers2