There are a number of ways to deploy an Ember app to a production environment. This video by Luke Melia at EmberConf 2015 includes a great explanation of how to use ember-cli-deploy, Ember’s current best practice method for deploying frontend apps. In additon to ember-cli-deploy, there’s also a Gem called ember-cli-rails, which is super helpful for getting started with deploying Ember along with Rails. However, I ran into some annoying fingerprinting issues when using ember-cli-rails and have subsequently stopped using the Gem.

Perhaps you don’t want to go the best practice route anyway. Perhaps you simply want to create an Ember app associated with a controller on your already existing Rails application without having to handle any weirdness with CSRF, versioning, and hosting that can arise from the ember-cli-deploy strategy. In that case, it may be easiest to upload your Ember app’s assets (js, css, images) to your production Rails server via Capistrano during the deploy process of your Rails app. Certainly, this sort of deploy can be limiting (e.g. to deploy the front end, you must also deploy the back end), but the upside is that the deploy process is simpler in that there is only one asset server in the mix and one deploy process to manage.

The easiest way to deploy an Ember app to your production Rails server is to precompile the Rails and Ember assets locally and rsync them to the remote server via Capistrano. For reference, I’ve posted a demo project on GitHub that implements this process.


The steps are as follows:

  1. Move Your Ember App into Your Rails Git Repo
  2. Symlink Your Ember “dist” Directory into the Rails “assets” Directory
  3. Create a New Layout for the Controller That Will Load Your Ember App
  4. Add Your Ember App’s Assets to Rails’ Asset Precompile Assets Array
  5. Disable Ember’s ‘storeConfigInMeta’ Property
  6. Update Capistrano’s Deploy Task
  7. Develop and Deploy

1. Move Your Ember App into Your Rails Git Repo

The first step is simple: make sure your Ember app lives inside your Rails git repo. For example, my demo Rails project is located in ~/workspace/deploy-ember-with-rails/. I’ve therefore moved my Ember app to ~/workspace/deploy-ember-with-rails/ember-app.

The next step is to symlink your Ember app’s “dist” directory into the Rails “assets” directory. The point of this step is to place the compiled Ember assets into a location that the Rails asset pipeline will pick up.

To create this symlink, go into your Rails app’s root directory and use the following commands (where “ember-app” is the location of the Ember app from the previous step):

mkdir app/assets/ember-app
cd app/assets/ember-app
ln -s ../../../ember-app/dist/assets ember-app

You’ll now have a semi-unseemly directory name at rails-app/app/assets/ember-app/ember-app that will house your Ember assets.

3. Create a New Layout for the Controller That Will Load Your Ember App

Now that your Ember app’s assets are symlinked into a place where the Rails asset pipeline can pick them up, you’ll need to insert a reference to the Ember assets into the Rails view. You can insert this reference by creating a separate layout called something like ember_application.html.erb and adding layout 'ember_application' to the top of the controller that will run the Ember app. For example:

class EmberAppController < ApplicationController
  layout 'ember_application'
  def show

Here are the contents of ember_application.html.erb:

<!DOCTYPE html>
  <%= stylesheet_link_tag    'application', media: 'all' %>
  <%= javascript_include_tag 'application' %>

  <%= javascript_include_tag 'ember-app/vendor' %>
  <%= stylesheet_link_tag 'ember-app/vendor' %>

  <%= javascript_include_tag 'ember-app/ember-app' %>
  <%= stylesheet_link_tag 'ember-app/ember-app' %>

  <%= csrf_meta_tags %>
  <div id="#ember-app">
  <%= yield %>

The Javascript and stylesheet include tags insert your Ember app’s assets into the page, and the <div id="#ember-app"> tag provides the <div> into which Ember can insert your app.

4. Add Your Ember App’s Assets to Rails’ Asset Precompile Assets Array

Add the following line to your config/initializers/assets.rb file to let Rails know that it should precompile your Ember app’s assets in production:

Rails.application.config.assets.precompile += %w(ember-app/ember-app.js ember-app/ember-app.css ember-app/vendor.js ember-app/vendor.css)

5. Disable Ember’s ‘storeConfigInMeta’ Property

By default, Ember stores configuration info about your application’s environment in a <meta> tag within an Ember-generated index.html page. However, since you are loading the Ember app from a view generated by Rails rather than one generated by Ember, this <meta> tag won’t exist. Fortunately, Ember has a property called storeConfigInMeta that can be set to false, which forces Ember to stroe this environment information in a Javascript file instead of a <meta> tag. The storeConfigInMeta property can be set from within the ember-cli-build.js file like so:

module.exports = function(defaults) {
  var app = new EmberApp(defaults, {
    storeConfigInMeta: false
  return app.toTree();

6. Update Capistrano’s Deploy Task

Finally, update Capistrano’s deploy task so that it precompiles both your Ember and Rails assets locally and rsyncs them to your remote server. The deploy task I use is based off this useful gist created by GitHub user twetzel.

Create a file in the lib/capistrano/tasks/ directory called deploy.rb and paste in the following code:

namespace :deploy do

  desc 'Compile assets'
  task :compile_assets => [:set_rails_env] do
    # invoke 'deploy:assets:precompile'
    invoke 'deploy:assets:precompile_local'
    invoke 'deploy:assets:backup_manifest'

  namespace :assets do
    desc "Precompile assets locally and then rsync to web servers"

    ember_app_name = "ember-app"
    local_ember_assets_dir = "./public/assets/"

    task :precompile_local do
      # compile assets locally
      run_locally do
        execute "cd #{ember_app_name} && ember build --environment=production"
        execute "RAILS_ENV=#{fetch(:stage)} bundle exec rake assets:precompile"

      # rsync to each server
      on roles( fetch(:assets_roles, [:web]) ) do
        # this needs to be done outside run_locally in order for host to exist
        remote_assets_dir = "#{host.user}@#{host.hostname}:#{release_path}/public/assets/"

        run_locally { execute "rsync -av --delete #{local_ember_assets_dir} #{remote_assets_dir}" }

      # clean up
      run_locally { execute "rm -rf #{local_ember_assets_dir}" }

Now, add load 'lib/capistrano/tasks/deploy.rb' into your Capfile.

7. Develop and Deploy

At this point, you should be able to develop locally and deploy to your remote server. To develop locally, you run your Rails server (bin/rails s) in one terminal and build your Ember app in another (ember build --watch --environment=development). When you visit the Rails app at http://localhost:3000, your Ember app will be available at the location you configured to point to your Ember app’s controller in your routes.rb file.

When deploying (cap produciton deploy), your assets will compile locally and be rsync’d up to the server. And then your Ember app is live. Hooray!