What should my Rails routes look like to work with pushState Ember.js routes?

Question

In short... When building an Ember.js app to persist to a Rails app, how should I handle Rails routing/views? I would think I just need Rails to render the application.html.erb layout so the Ember.js app initializes and handles the routing/view/templates. Details: Specifically if I visit localhost:3000, before my Ember.js app has a chance to initialize, Rails hits the "index" action on the projects controller. It will complain about a missing index template. I have no index.html.erb view as my Ember.js app has a view/template for it. Should I be creating blank views for the Rails app? Should my Rails controller actions be returning something to prevent it from rendering a view? Or am I expected to build normal Rails views to go alongside the Ember.js app views/templates? If I create a blank projects/index.html.erb and visit localhost:3000, Rails will render it, Ember.js will initialize and handle routing from then on. However, if I visit localhost:3000/projects/new directly Rails comp…

Accepted Answer

Another update: I've since started using DockYard's tutorial method for handling my Rails routes for a pushState Ember.js application. Here's an example Rails `routes.rb`:

```
EmberApp::Application.routes.draw do
    class FormatTest
      attr_accessor :mime_type

def initialize(format)
        @mime_type = Mime::Type.lookup_by_extension(format)
      end

def matches?(request)
        request.format == mime_type
      end
    end

get '*foo', :to => 'ember#index', :constraints => FormatTest.new(:html)
    get '/', :to => 'ember#index', :constraints => FormatTest.new(:html)
end
```

What should my Rails routes look like to work with pushState Ember.js routes?

Solution

Problem