Awesome

Awesome Heroku Commands

-- A curated list of delightful Heroku Commands

Read Related Awesome Pages :

Heroku Command Line

The heroku command-line interface (CLI) is a tool that wraps the Heroku Platform API, providing support for things like creating/renaming apps, running one-off dynos, taking backups, configuring add-ons and managing your app’s state-all from the terminal. Install it by following the instructions in Heroku Command Line.

Download and install

OS X Homebrew

To install the Heroku CLI with homebrew:

$ brew install heroku

OS X Installer

Download and run the OS X Installer.

Windows

Download and run the Windows installer 32-bit 64-bit

Verify your installation

To verify your CLI installation use the heroku --version command.

$ heroku --version

You should see heroku-cli/x.y.z in the output. If you don’t, but have installed the Heroku CLI, it’s possible you have an old heroku gem on your system.

Getting started

You will be asked to enter your Heroku credentials the first time you run a command; after the first time, your email address and an API token will be saved to ~/.netrc for future use. Here at Intuitive Surgical, you will need to login via single sign on. heroku login --sso

List all Heroku apps

$ heroku apps

Create apps with a specific name

$ heroku create myapp

Create app with a specific name and within an organization

$ heroku create myapp --org intusurg

Deploying from your local branch to heroku and force build

$ git push heroku localbranch:master (mybranch: master)

Rename apps

$ heroku heroku apps:oldname newname

Add heroku remote to existing project

$ cd myapp
$ heroku git:remote -a heroku-remote-name
$ git remote -v

Open current heroku app in browser

$ heroku open

Open application config

$ heroku config

Show state of the app

$ heroku ps

Open application logs

$ heroku logs

Tail logs

$ heroku logs --ps web.1 --tail

Running applications on dynos

Know what dynos are running which process types

$ heroku ps

Scaling size of dyno

$ heroku ps:resize worker=standard-2x

Scale Dynos numbers

$ heroku ps:scale web=3 queue=2

Views messages from worker dyno type

$ heroku logs --ps worker

Heroku’s HTTP routers distribute incoming requests for your application across your running web dynos.So scaling an app’s capacity to handle web traffic involves scaling the number of web dynos

$ heroku ps:scale web+5

Build packs

Setting buildpacks for an existing applications

$ heroku buildpacks:set heroku/php

Setting buildpacks while create an application

$ heroku create myapp --buildpack heroku/python

You can change or remove a previously set buildpack again later

$ heroku buildpacks:set heroku/nodejs
$ heroku buildpacks:remove heroku/nodejs

Adding third-party buildpacks

$ heroku buildpacks:set https://github.com/heroku/heroku-buildpack-erlang

Configuration

Set enviornment variables

$ heroku config:set ENCRYPTION_KEY=my_secret_launch_codes

Releases

Audit trail of release deploys

$ heroku releases

Rollback and deploy a previous release

$ heroku releases:rollback v102    //v102 is your commmit/tag

Managing Dynos

Typically dynos are cycled at least once per day, or whenever the dyno manager detects a fault in the running application (such as out of memory exceptions) or problems with the underlying hardware that requires the dyno be moved to a new physical location.

$ heroku run bash

Addons

Create addons

$ heroku addons:create heroku-redis:hobby-dev

Create addons

$ heroku addons:create heroku-redis:hobby-dev

Push/pull database (proceed with caution)

$ heroku db:pull
$ heroku db:push

Scale web app or add new dynos

$ heroku ps:scale web=1 // 1 is number of dynos the app will use (web=2 for two dynos)

Clone heroku app to local machine

$ heroku git: clone -a myapp

Heroku Addons

$ heroku addons

Delete all heroku apps (be very careful)

for app in $(heroku apps); do heroku apps:destroy --app $app --confirm $app; done

Setting an application in the org

$ heroku config:set --app myapp --org=intusurg

Setting environment for the applications

$ heroku config:set NODE_ENV=production

Setting environment for application in the org

$ heroku config:set --app=myapp NODE_ENV=production

Deploy new release and rollback (be careful)

$ heroku releases
$ heroku releases:rollback v#### (rollback to #### version)

Postgres Commands

Postgres info

$ heroku pg:info

Continuously watch heroku

$ watch heroku pg:info

Establish session with remote database with psql

$ heroku pg:psql mydatabase  // my database is your remote database