Deploying your applications to Heroku should never involve manually chaining shell commands together
Ruby
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
lib
LICENSE.md
README.md
init.rb

README.md

Heroku Deploy

Code Climate

Deploying your applications to Heroku should never involve manually chaining shell commands together.

Supported Ruby versions: 1.9.3 or higher

Licensed under the MIT license, see LICENSE for more information.

Heroku Deploy

Installation

This is a Heroku client plugin and as such requires the Heroku Toolbelt to be installed.

heroku plugins:install https://github.com/hyperoslo/heroku-deploy.git

Usage

By default, the master branch will be deployed to your Heroku app:

heroku deploy

A different branch may be provided:

heroku deploy feature/plus-ux

If you have multiple apps, you may specify either app or remote:

heroku deploy -a hyper-rocks-staging
heroku deploy -r staging

Features

  • Supports multiple languages and frameworks using deploy packs (see below)
  • Streams output from subcommands
  • Relies on UNIX exit statuses to abort deployment early in case of failure

Deploy Packs

A deploy pack represents a set of deployment instructions for a given language or framework. These instructions could range from turning on maintenance mode, scaling processes to scheduling backups.

At present, Ruby on Rails, Django and Symfony are supported. Deploying any other applications? Please open a pull request!

Ruby on Rails

  • Code deployment
  • Maintenance mode on
  • Database migrations
  • Restart dynos
    • Ensures all processes are in sync after potential database migrations
  • Maintenance mode off

Django

  • Code deployment
  • Maintenance mode on
  • Database migrations
  • Restart dynos
    • Ensures all processes are in sync after potential database migrations
  • Maintenance mode off

Symfony

  • Code deployment
  • Maintenance mode on
  • Database migrations
  • Restart dynos
    • Ensures all processes are in sync after potential database migrations
  • Maintenance mode off

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create pull request

Credits

Hyper made this. We're a digital communications agency with a passion for good code, and if you're using this plugin we probably want to hire you.