Last updated 02 August 2016
heroku help displays a usage summary:
$ heroku help Usage: heroku COMMAND [--app APP] [command-specific-options] Primary help topics, type "heroku help TOPIC" for more details: addons # manage add-on resources apps # manage apps (create, destroy) auth # authentication (login, logout) config # manage app config vars domains # manage domains logs # display logs for an app ps # manage dynos (dynos, workers) releases # manage app releases run # run one-off commands (console, rake) Additional topics: access # CLI to manage access in Heroku Applications buildpacks # manage the buildpack for an app certs # manage ssl endpoints for an app drains # list all log drains features # manage optional features git # manage local git repository for app help # list commands and display help keys # manage authentication keys labs # manage optional features local # run heroku app locally login # login with your Heroku credentials. maintenance # manage maintenance mode for an app members # manage membership in organization accounts notifications # display notifications orgs # manage organization accounts pg # manage heroku-postgresql databases pipelines # manage collections of apps in pipelines plugins # manage plugins to the heroku gem redis # manage heroku redis instances regions # list available regions spaces # manage heroku private spaces status # status of the Heroku platform update # update the heroku client version # display version
The commands are divided into two types: general commands and app commands.
General commands operate on your Heroku account as a whole, and are not specific to a particular app. For instance, to get a list of apps you created or are a collaborator on:
$ heroku apps example collabapp firstname.lastname@example.org example2
App commands are typically executed from within an app’s local git working copy.
The app name is automatically detected by scanning the git remotes for the
current working copy, so you don’t have to specify which app to operate on
explicitly. For example, the
heroku apps:info command can be executed without any
arguments inside the working copy:
$ cd example $ heroku apps:info === example Git Repo: email@example.com:example.git Owner: firstname.lastname@example.org Repo size: 960k Slug size: 512k Stack: cedar-14 Web URL: http://example.heroku.com/
If you have multiple heroku remotes or want to execute an app command outside of a local working copy, you can specify the remote name or an explicit app name as follows:
$ heroku apps:info --app example $ heroku apps:info --remote production
Alternatively, the app name can be specified by setting the
HEROKU_APP environment variable.
Using an HTTP proxy
If you’re behind a firewall that requires use of a proxy to connect with external HTTP/HTTPS services, you can set the
HTTPS_PROXY environment variables in your local developer environment, before running the
For example, on a Unix system you could do something like this:
$ export HTTP_PROXY=http://proxy.server.com:portnumber or $ export HTTPS_PROXY=https://proxy.server.com:portnumber $ heroku login
On a Windows machine, either set it in the System Properties/Environment Variables, or do it from the terminal:
> set HTTP_PROXY=http://proxy.server.com:portnumber or > set HTTPS_PROXY=https://proxy.server.com:portnumber > heroku login