Skip to content


Subversion checkout URL

You can clone with
Download ZIP
easy configuration / multi-environment setup with heroku with deployment hooks *NOTE* I no longer use Heroku. If anyone would like to take over this gem, just github msg me. Thanks!
Failed to load latest commit information.
.bundle fixed ::Rails namespace issue
autotest Adding HerokuConfig and specs
lib update and simplify authorization based on newer heroku
spec Refactoring gem
.gitignore Gemfile.lock shouldn't be checked in for gems
.rvmrc Adding shared_database as default addon
CHANGELOG bump to 0.4.4
Gemfile get rid of deprecation warnings in Rakefile
LICENSE Reorganizing gem to be heroku-rails Fixing BUNDLE_WITHOUT setting
TODO Bumping version to 0.2.0 and updating CHANGELOG
heroku-rails.gemspec bump to 0.4.4

Heroku Rails

Easier configuration and deployment of Rails apps on Heroku

Configure your Heroku environment via a YML file (config/heroku.yml) that defines all your environments, addons, and environment variables.

Heroku Rails also handles asset packaging (via jammit), deployment of assets to s3 (via jammit-s3).


Rails 3

Add this to your Gemfile:

group :development do
  gem 'heroku-rails'

Rails 2

To install add the following to config/environment.rb:

config.gem 'heroku-rails'

Rake tasks are not automatically loaded from gems, so you’ll need to add the following to your Rakefile:

  require 'heroku/rails/tasks'
rescue LoadError
  STDERR.puts "Run `rake gems:install` to install heroku-rails"


In config/heroku.yml you will need add the Heroku apps that you would like to attach to this project. You can generate this file and edit it by running:

rails generate heroku:config

Example Configuration File

  production: awesomeapp
  staging: awesomeapp-staging
  legacy: awesomeapp-legacy

  all: bamboo-mri-1.9.2
  legacy: bamboo-ree-1.8.7

    BUNDLE_WITHOUT: "test:development"
    MONGODB_URI: "mongodb://[username:password@]host1[:port1][/database]"
    MONGODB_URI: "mongodb://[username:password@]host1[:port1][/database]"

    - ""
    - ""

    - ""
    - ""

    - newrelic:bronze
    # add any other addons here

    - ssl:piggyback
    - cron:daily
    # list production env specific addons here

Setting up Heroku

To set heroku up (using your heroku.yml), just run.

rake all heroku:setup

This will create the heroku apps you have defined, and create the settings for each.

Run rake heroku:setup every time you edit the heroku.yml. It will only make incremental changes (based on what you've added/removed). If nothing has changed in the heroku.yml since the last heroku:setup, then no heroku changes will be sent.


After configuring your Heroku apps you can use rake tasks to control the apps.

rake production heroku:deploy

A rake task with the shorthand name of each app is now available and adds that server to the list that subsequent commands will execute on. Because this list is additive, you can easily select which servers to run a command on.

rake demo staging heroku:restart

A special rake task 'all' is created that causes any further commands to execute on all heroku apps.

Need to add remotes for each app?

rake all heroku:remotes

A full list of tasks provided:

rake all                        # Select all Heroku apps for later command
rake heroku:deploy              # Deploys, migrates and restarts latest code.
rake heroku:apps                # Lists configured apps
rake heroku:info                # Queries the heroku status info on each app
rake heroku:console             # Opens a remote console
rake heroku:capture             # Captures a bundle on Heroku
rake heroku:remotes             # Add git remotes for all apps in this project
rake heroku:migrate             # Migrates and restarts remote servers
rake heroku:restart             # Restarts remote servers

rake heroku:setup               # runs all heroku setup scripts
rake heroku:setup:addons        # sets up the heroku addons
rake heroku:setup:collaborators # sets up the heroku collaborators
rake heroku:setup:config        # sets up the heroku config env variables
rake heroku:setup:domains       # sets up the heroku domains
rake heroku:setup:stacks        # sets the correct stack for each heroku app

rake heroku:db:setup            # Migrates and restarts remote servers

You can easily alias frequently used tasks within your application's Rakefile:

task :deploy =>  ["heroku:deploy"]
task :console => ["heroku:console"]
task :capture => ["heroku:capture"]

With this in place, you can be a bit more terse:

rake staging console
rake all deploy

Deploy Hooks

You can easily hook into the deploy process by defining any of the following rake tasks.

When you ran rails generate heroku:config, it created a list of empty rake tasks within lib/tasks/heroku.rake. Edit these rake tasks to provide custom logic for before/after deployment.

namespace :heroku do
  # runs before all the deploys complete
  task :before_deploy do


  # runs before each push to a particular heroku deploy environment
  task :before_each_deploy do


  # runs after each push to a particular heroku deploy environment
  task :after_each_deploy do


  # runs after all the deploys complete
  task :after_deploy do


About Heroku Rails



Issue Tracker::


License:: Copyright (c) 2010 Jacques Crocker released under the MIT license.

Forked from Heroku Sans

Heroku Rails is a fork and rewrite/reorganiziation of the heroku_sans gem. Heroku Sans is a simple and elegant set of Rake tasks for managing Heroku environments. Check out that project here:

Heroku Sans Contributors

Heroku Sans License

License:: Copyright (c) 2009 Elijah Miller, released under the MIT license.

Something went wrong with that request. Please try again.