Heroku CLI コマンド
この記事の英語版に更新があります。ご覧の翻訳には含まれていない変更点があるかもしれません。
最終更新日 2023年03月13日(月)
heroku access
アプリにアクセスできるユーザーを一覧表示します。
list who has access to an app
USAGE
$ heroku access
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json output in json format
heroku access:add EMAIL
アプリに新しいユーザーを追加します。
add new users to your app
USAGE
$ heroku access:add EMAIL
OPTIONS
-a, --app=app (required) app to run command against
-p, --permissions=permissions list of permissions comma separated
-r, --remote=remote git remote of app to use
EXAMPLES
$ heroku access:add user@email.com --app APP # add a collaborator to your app
$ heroku access:add user@email.com --app APP --permissions deploy,manage,operate # permissions must be comma separated
heroku access:remove EMAIL
チームアプリからユーザーを削除します。
remove users from a team app
USAGE
$ heroku access:remove EMAIL
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
EXAMPLES
$ heroku access:remove user@email.com --app APP
heroku access:update EMAIL
チームアプリの既存の共同作業者を更新します。
update existing collaborators on an team app
USAGE
$ heroku access:update EMAIL
OPTIONS
-a, --app=app (required) app to run command against
-p, --permissions=permissions comma-delimited list of permissions to update (deploy,manage,operate)
-r, --remote=remote git remote of app to use
EXAMPLES
$ heroku access:update user@email.com --app APP --permissions deploy,manage,operate
heroku addons [--all|--app APP]
アドオンとアタッチメントを一覧表示します。
lists your add-ons and attachments
The default filter applied depends on whether you are in a Heroku app
directory. If so, the --app flag is implied. If not, the default of --all
is implied. Explicitly providing either flag overrides the default
behavior.
USAGE
$ heroku addons [--all|--app APP]
OPTIONS
-A, --all show add-ons and attachments for all accessible apps
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--json return add-ons in json format
DESCRIPTION
The default filter applied depends on whether you are in a Heroku app
directory. If so, the --app flag is implied. If not, the default of --all
is implied. Explicitly providing either flag overrides the default
behavior.
EXAMPLES
$ heroku addons --all
$ heroku addons --app acme-inc-www
heroku addons:attach ADDON_NAME
アプリに既存のアドオンリソースをアタッチします。
attach an existing add-on resource to an app
USAGE
$ heroku addons:attach ADDON_NAME
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--as=as name for add-on attachment
--confirm=confirm overwrite existing add-on attachment with same name
--credential=credential credential name for scoped access to Heroku Postgres
heroku addons:create SERVICE:PLAN
新しいアドオンリソースを作成します。
create a new add-on resource
USAGE
$ heroku addons:create SERVICE:PLAN
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--as=as name for the initial add-on attachment
--confirm=confirm overwrite existing config vars or existing add-on attachments
--name=name name for the add-on resource
--wait watch add-on creation status and exit when complete
heroku addons:destroy [ADDON]... [flags]
アドオンリソースを永続的に破棄します。
permanently destroy an add-on resource
USAGE
$ heroku addons:destroy [ADDON]... [flags]
OPTIONS
-a, --app=app app to run command against
-c, --confirm=confirm
-f, --force allow destruction even if connected to other apps
-r, --remote=remote git remote of app to use
heroku addons:detach ATTACHMENT_NAME
アプリから既存のアドオンリソースをデタッチします。
detach an existing add-on resource from an app
USAGE
$ heroku addons:detach ATTACHMENT_NAME
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku addons:docs ADDON
ブラウザでアドオンの Dev Center ドキュメントを開きます。
open an add-on's Dev Center documentation in your browser
USAGE
$ heroku addons:docs ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--show-url show URL, do not open browser
heroku addons:downgrade ADDON [PLAN]
アドオンプランを変更します。
change add-on plan
See available plans with `heroku addons:plans SERVICE`.
Note that `heroku addons:upgrade` and `heroku addons:downgrade` are the same.
Either one can be used to change an add-on plan up or down.
https://devcenter.heroku.com/articles/managing-add-ons
USAGE
$ heroku addons:downgrade ADDON [PLAN]
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
See available plans with `heroku addons:plans SERVICE`.
Note that `heroku addons:upgrade` and `heroku addons:downgrade` are the same.
Either one can be used to change an add-on plan up or down.
https://devcenter.heroku.com/articles/managing-add-ons
EXAMPLE
Upgrade an add-on by service name:
$ heroku addons:upgrade heroku-redis:premium-2
Upgrade a specific add-on:
$ heroku addons:upgrade swimming-briskly-123 heroku-redis:premium-2
heroku addons:info ADDON
詳細なアドオンリソースとアタッチメントの情報を表示します。
show detailed add-on resource and attachment information
USAGE
$ heroku addons:info ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
heroku addons:open ADDON
ブラウザでアドオンのダッシュボードを開きます。
open an add-on's dashboard in your browser
USAGE
$ heroku addons:open ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--show-url show URL, do not open browser
heroku addons:plans SERVICE
アドオンサービスの使用可能なすべてのプランを一覧表示します。
list all available plans for an add-on services
USAGE
$ heroku addons:plans SERVICE
OPTIONS
--json output in json format
heroku addons:rename ADDON NEW_NAME
アドオンの名前を変更します。
rename an add-on
USAGE
$ heroku addons:rename ADDON NEW_NAME
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
heroku addons:services
使用可能なすべてのアドオンサービスを一覧表示します。
list all available add-on services
USAGE
$ heroku addons:services
OPTIONS
--json output in json format
heroku addons:upgrade ADDON [PLAN]
アドオンプランを変更します。
change add-on plan
See available plans with `heroku addons:plans SERVICE`.
Note that `heroku addons:upgrade` and `heroku addons:downgrade` are the same.
Either one can be used to change an add-on plan up or down.
https://devcenter.heroku.com/articles/managing-add-ons
USAGE
$ heroku addons:upgrade ADDON [PLAN]
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
See available plans with `heroku addons:plans SERVICE`.
Note that `heroku addons:upgrade` and `heroku addons:downgrade` are the same.
Either one can be used to change an add-on plan up or down.
https://devcenter.heroku.com/articles/managing-add-ons
EXAMPLE
Upgrade an add-on by service name:
$ heroku addons:upgrade heroku-redis:premium-2
Upgrade a specific add-on:
$ heroku addons:upgrade swimming-briskly-123 heroku-redis:premium-2
heroku addons:wait ADDON
アプリ上のアドオンのプロビジョニングステータスを表示します。
show provisioning status of the add-ons on the app
USAGE
$ heroku addons:wait ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--wait-interval=wait-interval how frequently to poll in seconds
heroku apps
アプリを一覧表示します。
list your apps
USAGE
$ heroku apps
OPTIONS
-A, --all include apps in all teams
-p, --personal list apps in personal account when a default team is set
-s, --space=space filter by space
-t, --team=team team to use
--json output in json format
EXAMPLES
$ heroku apps
=== My Apps
example
example2
=== Collaborated Apps
theirapp other@owner.name
heroku apps:create [APP]
新しいアプリを作成します。
creates a new app
USAGE
$ heroku apps:create [APP]
ARGUMENTS
APP name of app to create
OPTIONS
-b, --buildpack=buildpack buildpack url to use for this app
-n, --no-remote do not create a git remote
-r, --remote=remote the git remote to create, default "heroku"
-s, --stack=stack the stack to create the app on
-t, --team=team team to use
--addons=addons comma-delimited list of addons to install
--json output in json format
--region=region specify region for the app to run in
--space=space the private space to create the app in
EXAMPLES
$ heroku apps:create
Creating app... done, stack is heroku-22
https://floating-dragon-42.heroku.com/ | https://git.heroku.com/floating-dragon-42.git
# or just
$ heroku create
# use a heroku.yml manifest file
$ heroku apps:create --manifest
# specify a buildpack
$ heroku apps:create --buildpack https://github.com/some/buildpack.git
# specify a name
$ heroku apps:create example
# create a staging app
$ heroku apps:create example-staging --remote staging
# create an app in the eu region
$ heroku apps:create --region eu
heroku apps:destroy
アプリを永続的に破棄します。
permanently destroy an app
This will also destroy all add-ons on the app.
USAGE
$ heroku apps:destroy
OPTIONS
-a, --app=app app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
DESCRIPTION
This will also destroy all add-ons on the app.
heroku apps:errors
アプリのエラーを表示します。
view app errors
USAGE
$ heroku apps:errors
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--dyno show only dyno errors
--hours=hours number of hours to look back (default 24)
--json output in json format
--router show only router errors
heroku apps:favorites
お気に入りのアプリを一覧表示します。
list favorited apps
USAGE
$ heroku apps:favorites
OPTIONS
--json output in json format
heroku apps:favorites:add
アプリをお気に入りにします。
favorites an app
USAGE
$ heroku apps:favorites:add
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku apps:favorites:remove
アプリをお気に入りから削除します。
unfavorites an app
USAGE
$ heroku apps:favorites:remove
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku apps:info
詳細なアプリ情報を表示します。
show detailed app information
$ heroku apps:info
=== example
Git URL: https://git.heroku.com/example.git
Repo Size: 5M
...
$ heroku apps:info --shell
git_url=https://git.heroku.com/example.git
repo_size=5000000
...
USAGE
$ heroku apps:info
OPTIONS
-a, --app=app app to run command against
-j, --json
-r, --remote=remote git remote of app to use
-s, --shell output more shell friendly key/value pairs
DESCRIPTION
$ heroku apps:info
=== example
Git URL: https://git.heroku.com/example.git
Repo Size: 5M
...
$ heroku apps:info --shell
git_url=https://git.heroku.com/example.git
repo_size=5000000
...
heroku apps:join
チームアプリに自分自身を追加します。
add yourself to a team app
USAGE
$ heroku apps:join
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku apps:leave
チームアプリから自分自身を削除します。
remove yourself from a team app
USAGE
$ heroku apps:leave
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku apps:lock
チームメンバーがアプリに参加できないようにします。
prevent team members from joining an app
USAGE
$ heroku apps:lock
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku apps:open [PATH]
Web ブラウザでアプリを開きます。
open the app in a web browser
USAGE
$ heroku apps:open [PATH]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
EXAMPLES
$ heroku open -a myapp
# opens https://myapp.herokuapp.com
$ heroku open -a myapp /foo
# opens https://myapp.herokuapp.com/foo
heroku apps:rename NEWNAME
アプリの名前を変更します。
rename an app
This will locally update the git remote if it is set to the old app.
USAGE
$ heroku apps:rename NEWNAME
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
This will locally update the git remote if it is set to the old app.
EXAMPLES
$ heroku apps:rename --app oldname newname
https://newname.herokuapp.com/ | https://git.heroku.com/newname.git
Git remote heroku updated
heroku apps:stacks
使用可能なスタックの一覧を表示します。
show the list of available stacks
USAGE
$ heroku apps:stacks
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku apps:stacks:set STACK
アプリのスタックを設定します。
set the stack of an app
USAGE
$ heroku apps:stacks:set STACK
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
EXAMPLES
$ heroku stack:set heroku-22 -a myapp
Setting stack to heroku-22... done
You will need to redeploy myapp for the change to take effect.
Run git push heroku main to trigger a new build on myapp.
heroku apps:transfer RECIPIENT
アプリケーションを別のユーザーまたはチームに移動します。
transfer applications to another user or team
USAGE
$ heroku apps:transfer RECIPIENT
ARGUMENTS
RECIPIENT user or team to transfer applications to
OPTIONS
-a, --app=app app to run command against
-l, --locked lock the app upon transfer
-r, --remote=remote git remote of app to use
--bulk transfer applications in bulk
EXAMPLES
$ heroku apps:transfer collaborator@example.com
Transferring example to collaborator@example.com... done
$ heroku apps:transfer acme-widgets
Transferring example to acme-widgets... done
$ heroku apps:transfer --bulk acme-widgets
...
heroku apps:unlock
任意のチームメンバーが参加できるように、アプリのロックを解除します。
unlock an app so any team member can join
USAGE
$ heroku apps:unlock
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku auth:2fa
2FA ステータスを確認します。
check 2fa status
USAGE
$ heroku auth:2fa
ALIASES
$ heroku 2fa
$ heroku twofactor
コードを参照: @heroku-cli/plugin-auth
heroku auth:2fa:disable
アカウントの 2FA を無効にします。
disables 2fa on account
USAGE
$ heroku auth:2fa:disable
ALIASES
$ heroku twofactor:disable
$ heroku 2fa:disable
EXAMPLES
$ heroku auth:2fa:disable
コードを参照: @heroku-cli/plugin-auth
heroku auth:login
Heroku 資格情報でログインします。
login with your Heroku credentials
USAGE
$ heroku auth:login
OPTIONS
-e, --expires-in=expires-in duration of token in seconds (default 30 days)
-i, --interactive login with username/password
--browser=browser browser to open SSO with (example: "firefox", "safari")
ALIASES
$ heroku login
コードを参照: @heroku-cli/plugin-auth
heroku auth:logout
ローカルログイン資格情報を消去し、API セッションを無効にします。
clears local login credentials and invalidates API session
USAGE
$ heroku auth:logout
ALIASES
$ heroku logout
コードを参照: @heroku-cli/plugin-auth
heroku auth:token
現在の CLI 認証トークンを出力します。
outputs current CLI authentication token.
By default, the CLI auth token is only valid for 1 year. To generate a long-lived token, use heroku authorizations:create
USAGE
$ heroku auth:token
OPTIONS
-h, --help show CLI help
DESCRIPTION
By default, the CLI auth token is only valid for 1 year. To generate a long-lived token, use heroku
authorizations:create
コードを参照: @heroku-cli/plugin-auth
heroku auth:whoami
現在のログインしているユーザーを表示します。
display the current logged in user
USAGE
$ heroku auth:whoami
ALIASES
$ heroku whoami
コードを参照: @heroku-cli/plugin-auth
heroku authorizations
OAuth 認証を一覧表示します。
list OAuth authorizations
USAGE
$ heroku authorizations
OPTIONS
-j, --json output in json format
コードを参照: @heroku-cli/plugin-oauth-v5
heroku authorizations:create
新しい OAuth 認証を作成します。
create a new OAuth authorization
This creates an authorization with access to your Heroku account.
USAGE
$ heroku authorizations:create
OPTIONS
-S, --short only output token
-d, --description=description set a custom authorization description
-e, --expires-in=expires-in set expiration in seconds (default no expiration)
-j, --json output in json format
-s, --scope=scope set custom OAuth scopes
DESCRIPTION
This creates an authorization with access to your Heroku account.
コードを参照: @heroku-cli/plugin-oauth-v5
heroku authorizations:info ID
既存の OAuth 認証を表示します。
show an existing OAuth authorization
USAGE
$ heroku authorizations:info ID
OPTIONS
-j, --json output in json format
コードを参照: @heroku-cli/plugin-oauth-v5
heroku authorizations:revoke ID
OAuth 認証を取り消します。
revoke OAuth authorization
USAGE
$ heroku authorizations:revoke ID
ALIASES
$ heroku authorizations:destroy
コードを参照: @heroku-cli/plugin-oauth-v5
heroku authorizations:rotate ID
OAuth 認証トークンを更新します。
updates an OAuth authorization token
USAGE
$ heroku authorizations:rotate ID
コードを参照: @heroku-cli/plugin-oauth-v5
heroku authorizations:update ID
OAuth 認証を更新します。
updates an OAuth authorization
USAGE
$ heroku authorizations:update ID
OPTIONS
-d, --description=description set a custom authorization description
--client-id=client-id identifier of OAuth client to set
--client-secret=client-secret secret of OAuth client to set
コードを参照: @heroku-cli/plugin-oauth-v5
heroku autocomplete [SHELL]
オートコンプリートのインストール手順を表示します。
display autocomplete installation instructions
USAGE
$ heroku autocomplete [SHELL]
ARGUMENTS
SHELL shell type
OPTIONS
-r, --refresh-cache refresh cache only (ignores displaying instructions)
EXAMPLES
$ heroku autocomplete
$ heroku autocomplete bash
$ heroku autocomplete zsh
$ heroku autocomplete --refresh-cache
コードを参照: @heroku-cli/plugin-autocomplete
heroku buildpacks
アプリの buildpack を表示します。
display the buildpacks for an app
USAGE
$ heroku buildpacks
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-buildpacks
heroku buildpacks:add BUILDPACK
新しいアプリの buildpack を追加し、必要に応じて buildpack の一覧に挿入します。
add new app buildpack, inserting into list of buildpacks if necessary
USAGE
$ heroku buildpacks:add BUILDPACK
ARGUMENTS
BUILDPACK namespace/name of the buildpack
OPTIONS
-a, --app=app (required) app to run command against
-i, --index=index the 1-based index of the URL in the list of URLs
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-buildpacks
heroku buildpacks:clear
アプリで設定されているすべての buildpack を消去します。
clear all buildpacks set on the app
USAGE
$ heroku buildpacks:clear
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-buildpacks
heroku buildpacks:info BUILDPACK
buildpack に関する情報をフェッチします。
fetch info about a buildpack
USAGE
$ heroku buildpacks:info BUILDPACK
ARGUMENTS
BUILDPACK namespace/name of the buildpack
コードを参照: @heroku-cli/plugin-buildpacks
heroku buildpacks:remove [BUILDPACK]
アプリで設定されている buildpack を削除します。
remove a buildpack set on the app
USAGE
$ heroku buildpacks:remove [BUILDPACK]
ARGUMENTS
BUILDPACK namespace/name of the buildpack
OPTIONS
-a, --app=app (required) app to run command against
-i, --index=index the 1-based index of the URL to remove from the list of URLs
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-buildpacks
heroku buildpacks:search [TERM]
buildpack を検索します。
search for buildpacks
USAGE
$ heroku buildpacks:search [TERM]
ARGUMENTS
TERM search term that searches across name, namespace, and description
OPTIONS
--description=description buildpack description to filter on
--name=name buildpack names to filter on using a comma separated list
--namespace=namespace buildpack namespaces to filter on using a comma separated list
コードを参照: @heroku-cli/plugin-buildpacks
heroku buildpacks:set BUILDPACK
undefined
USAGE
$ heroku buildpacks:set BUILDPACK
ARGUMENTS
BUILDPACK namespace/name of the buildpack
OPTIONS
-a, --app=app (required) app to run command against
-i, --index=index the 1-based index of the URL in the list of URLs
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-buildpacks
heroku buildpacks:versions BUILDPACK
buildpack のバージョンを一覧表示します。
list versions of a buildpack
USAGE
$ heroku buildpacks:versions BUILDPACK
ARGUMENTS
BUILDPACK namespace/name of the buildpack
コードを参照: @heroku-cli/plugin-buildpacks
heroku certs
アプリの SSL 証明書を一覧表示します。
list SSL certificates for an app
USAGE
$ heroku certs
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:add CRT KEY
アプリに SSL 証明書を追加します。
add an SSL certificate to an app
Note: certificates with PEM encoding are also valid
USAGE
$ heroku certs:add CRT KEY
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--bypass bypass the trust chain completion step
DESCRIPTION
Note: certificates with PEM encoding are also valid
EXAMPLES
$ heroku certs:add example.com.crt example.com.key
If you require intermediate certificates, refer to this article on merging certificates to get a complete chain:
https://help.salesforce.com/s/articleView?id=000333504&type=1
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:auto
アプリの ACM ステータスを表示します。
show ACM status for an app
USAGE
$ heroku certs:auto
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--wait watch ACM status and display the status when complete
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:auto:disable
アプリの ACM を無効にします。
disable ACM for an app
USAGE
$ heroku certs:auto:disable
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:auto:enable
アプリの ACM ステータスを有効にします。
enable ACM status for an app
USAGE
$ heroku certs:auto:enable
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--wait watch ACM status and exit when complete
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:auto:refresh
アプリの ACM を更新します。
refresh ACM for an app
USAGE
$ heroku certs:auto:refresh
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:chain
証明書の順序付けられた完全なチェーンを出力します。
print an ordered & complete chain for a certificate
USAGE
$ heroku certs:chain
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:generate DOMAIN
鍵と CSR または自己署名証明書を生成します。
generate a key and a CSR or self-signed certificate
Generate a key and certificate signing request (or self-signed certificate)
for an app. Prompts for information to put in the certificate unless --now
is used, or at least one of the --subject, --owner, --country, --area, or
--city options is specified.
USAGE
$ heroku certs:generate DOMAIN
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--area=area sub-country area (state, province, etc.) of owner
--city=city city of owner
--country=country country of owner, as a two-letter ISO country code
--keysize=keysize RSA key size in bits (default: 2048)
--now do not prompt for any owner information
--owner=owner name of organization certificate belongs to
--selfsigned generate a self-signed certificate instead of a CSR
--subject=subject specify entire certificate subject
DESCRIPTION
Generate a key and certificate signing request (or self-signed certificate)
for an app. Prompts for information to put in the certificate unless --now
is used, or at least one of the --subject, --owner, --country, --area, or
--city options is specified.
EXAMPLES
$ heroku certs:generate example.com
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:info
SSL 証明書の証明書情報を表示します。
show certificate information for an SSL certificate
USAGE
$ heroku certs:info
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--endpoint=endpoint endpoint to check info on
--name=name name to check info on
--show-domains show associated domains
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:key
指定された証明書の正しい鍵を出力します。
print the correct key for the given certificate
You must pass one single certificate, and one or more keys.
The first key that signs the certificate will be printed back.
USAGE
$ heroku certs:key
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
You must pass one single certificate, and one or more keys.
The first key that signs the certificate will be printed back.
EXAMPLES
$ heroku certs:key example.com.crt example.com.key
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:remove
アプリから SSL 証明書を削除します。
remove an SSL certificate from an app
USAGE
$ heroku certs:remove
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--endpoint=endpoint endpoint to remove
--name=name name to remove
コードを参照: @heroku-cli/plugin-certs-v5
heroku certs:update CRT KEY
アプリの SSL 証明書を更新します。
update an SSL certificate on an app
Note: certificates with PEM encoding are also valid
USAGE
$ heroku certs:update CRT KEY
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--bypass bypass the trust chain completion step
--endpoint=endpoint endpoint to update
--name=name name to update
DESCRIPTION
Note: certificates with PEM encoding are also valid
EXAMPLES
$ heroku certs:update example.com.crt example.com.key
If you require intermediate certificates, refer to this article on merging certificates to get a complete chain:
https://help.salesforce.com/s/articleView?id=000333504&type=1
コードを参照: @heroku-cli/plugin-certs-v5
heroku ci
指定されたパイプラインの最新の CI 実行を表示します。
display the most recent CI runs for the given pipeline
USAGE
$ heroku ci
OPTIONS
-a, --app=app app name
-p, --pipeline=pipeline name of pipeline
--json output in json format
--watch keep running and watch for new and update tests
EXAMPLE
$ heroku ci --app murmuring-headland-14719
コードを参照: @heroku-cli/plugin-ci
heroku ci:config
CI の環境設定を表示します。
display CI config vars
Example:
$ heroku ci:config --app murmuring-headland-14719 --json
USAGE
$ heroku ci:config
OPTIONS
-a, --app=app app to run command against
-p, --pipeline=pipeline pipeline
-r, --remote=remote git remote of app to use
-s, --shell output config vars in shell format
--json output config vars in json format
DESCRIPTION
Example:
$ heroku ci:config --app murmuring-headland-14719 --json
heroku ci:config:get KEY
CI の環境設定を取得します。
get a CI config var
Examples:
$ heroku ci:config:get RAILS_ENV
test
USAGE
$ heroku ci:config:get KEY
OPTIONS
-a, --app=app app to run command against
-p, --pipeline=pipeline pipeline
-r, --remote=remote git remote of app to use
-s, --shell output config var in shell format
DESCRIPTION
Examples:
$ heroku ci:config:get RAILS_ENV
test
heroku ci:config:set
CI の環境設定を設定します。
set CI config vars
Examples:
$ heroku ci:config:set RAILS_ENV=test
Setting test config vars... done
RAILS_ENV: test
USAGE
$ heroku ci:config:set
OPTIONS
-a, --app=app app to run command against
-p, --pipeline=pipeline pipeline
-r, --remote=remote git remote of app to use
DESCRIPTION
Examples:
$ heroku ci:config:set RAILS_ENV=test
Setting test config vars... done
RAILS_ENV: test
heroku ci:config:unset
CI の環境設定を設定解除します。
unset CI config vars
Examples:
$ heroku ci:config:uset RAILS_ENV
Unsetting RAILS_ENV... done
USAGE
$ heroku ci:config:unset
OPTIONS
-a, --app=app app to run command against
-p, --pipeline=pipeline pipeline
-r, --remote=remote git remote of app to use
DESCRIPTION
Examples:
$ heroku ci:config:uset RAILS_ENV
Unsetting RAILS_ENV... done
heroku ci:debug
現在のディレクトリの内容を使用して対話型テストデバッグセッションを開きます。
opens an interactive test debugging session with the contents of the current directory
Example:
$ heroku ci:debug
Preparing source... done
Creating test run... done
Running setup and attaching to test dyno...
~ $
USAGE
$ heroku ci:debug
OPTIONS
-a, --app=app app to run command against
-p, --pipeline=pipeline pipeline
-r, --remote=remote git remote of app to use
--no-cache start test run with an empty cache
--no-setup start test dyno without running test-setup
DESCRIPTION
Example:
$ heroku ci:debug
Preparing source... done
Creating test run... done
Running setup and attaching to test dyno...
~ $
heroku ci:info TEST-RUN
特定のテスト実行のステータスを表示します。
show the status of a specific test run
USAGE
$ heroku ci:info TEST-RUN
OPTIONS
-a, --app=app app name
-p, --pipeline=pipeline name of pipeline
--node=node the node number to show its setup and output
EXAMPLE
$ heroku ci:info 1288 --app murmuring-headland-14719
コードを参照: @heroku-cli/plugin-ci
heroku ci:last
最新の実行を検索し、その実行の出力を返します。
looks for the most recent run and returns the output of that run
USAGE
$ heroku ci:last
OPTIONS
-a, --app=app app name
-p, --pipeline=pipeline name of pipeline
--node=node the node number to show its setup and output
EXAMPLE
$ heroku ci:last --pipeline=my-pipeline --node 100
コードを参照: @heroku-cli/plugin-ci
heroku ci:migrate-manifest
app-ci.json は非推奨になっています。環境キーを使用して app.json に移行するには、このコマンドを実行します。
app-ci.json is deprecated. Run this command to migrate to app.json with an environments key.
Example:
$ heroku ci:migrate-manifest
Writing app.json file... done
Deleting app-ci.json file... done
Please check the contents of your app.json before committing to your repo
You're all set! 🎉.
USAGE
$ heroku ci:migrate-manifest
DESCRIPTION
Example:
$ heroku ci:migrate-manifest
Writing app.json file... done
Deleting app-ci.json file... done
Please check the contents of your app.json before committing to your repo
You're all set! 🎉.
heroku ci:open
Heroku CI の Dashboard バージョンを開きます。
open the Dashboard version of Heroku CI
opens a browser to view the Dashboard version of Heroku CI
Example:
$ heroku ci:open --app murmuring-headland-14719
USAGE
$ heroku ci:open
OPTIONS
-a, --app=app app to run command against
-p, --pipeline=pipeline pipeline
-r, --remote=remote git remote of app to use
DESCRIPTION
opens a browser to view the Dashboard version of Heroku CI
Example:
$ heroku ci:open --app murmuring-headland-14719
heroku ci:rerun [NUMBER]
現在のディレクトリに対してテストを再実行します。
rerun tests against current directory
USAGE
$ heroku ci:rerun [NUMBER]
OPTIONS
-a, --app=app app name
-p, --pipeline=pipeline name of pipeline
EXAMPLE
$ heroku ci:rerun 985 --app murmuring-headland-14719
コードを参照: @heroku-cli/plugin-ci
heroku ci:run
現在のディレクトリに対してテストを実行します。
run tests against current directory
USAGE
$ heroku ci:run
OPTIONS
-a, --app=app app name
-p, --pipeline=pipeline name of pipeline
EXAMPLE
$ heroku ci:run --app murmuring-headland-14719
コードを参照: @heroku-cli/plugin-ci
heroku clients
OAuth クライアントを一覧表示します。
list your OAuth clients
USAGE
$ heroku clients
OPTIONS
-j, --json output in json format
コードを参照: @heroku-cli/plugin-oauth-v5
heroku clients:create NAME REDIRECT_URI
新しい OAuth クライアントを作成します。
create a new OAuth client
USAGE
$ heroku clients:create NAME REDIRECT_URI
OPTIONS
-j, --json output in json format
-s, --shell output in shell format
コードを参照: @heroku-cli/plugin-oauth-v5
heroku clients:destroy ID
ID でクライアントを削除します。
delete client by ID
USAGE
$ heroku clients:destroy ID
コードを参照: @heroku-cli/plugin-oauth-v5
heroku clients:info ID
OAuth クライアントの詳細を表示します。
show details of an oauth client
USAGE
$ heroku clients:info ID
OPTIONS
-j, --json output in json format
-s, --shell output in shell format
コードを参照: @heroku-cli/plugin-oauth-v5
heroku clients:rotate ID
OAuth クライアントの秘密鍵を定期的に変更します。
rotate OAuth client secret
USAGE
$ heroku clients:rotate ID
OPTIONS
-j, --json output in json format
-s, --shell output in shell format
コードを参照: @heroku-cli/plugin-oauth-v5
heroku clients:update ID
OAuth クライアントを更新します。
update OAuth client
USAGE
$ heroku clients:update ID
OPTIONS
-n, --name=name change the client name
--url=url change the client redirect URL
コードを参照: @heroku-cli/plugin-oauth-v5
heroku commands
すべてのコマンドを一覧表示します。
list all the commands
USAGE
$ heroku commands
OPTIONS
-h, --help show CLI help
-j, --json display unfiltered api data in json format
-x, --extended show extra columns
--columns=columns only show provided columns (comma-separated)
--csv output is csv format [alias: --output=csv]
--filter=filter filter property by partial string matching, ex: name=foo
--hidden show hidden commands
--no-header hide table header from output
--no-truncate do not truncate output to fit screen
--output=csv|json|yaml output in a more machine friendly format
--sort=sort property to sort by (prepend '-' for descending)
コードを参照: @oclif/plugin-commands
heroku config
アプリの環境設定を表示します。
display the config vars for an app
USAGE
$ heroku config
OPTIONS
-a, --app=app (required) app to run command against
-j, --json output config vars in json format
-r, --remote=remote git remote of app to use
-s, --shell output config vars in shell format
コードを参照: @heroku-cli/plugin-config
heroku config:edit [KEY]
環境設定を対話的に編集します。
interactively edit config vars
This command opens the app config in a text editor set by $VISUAL or $EDITOR.
Any variables added/removed/changed will be updated on the app after saving and closing the file.
USAGE
$ heroku config:edit [KEY]
ARGUMENTS
KEY edit a single key
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
This command opens the app config in a text editor set by $VISUAL or $EDITOR.
Any variables added/removed/changed will be updated on the app after saving and closing the file.
EXAMPLES
# edit with vim
$ EDITOR="vim" heroku config:edit
# edit with emacs
$ EDITOR="emacs" heroku config:edit
# edit with pico
$ EDITOR="pico" heroku config:edit
# edit with atom editor
$ VISUAL="atom --wait" heroku config:edit
コードを参照: @heroku-cli/plugin-config
heroku config:get KEY...
アプリの 1 つの設定値を表示します。
display a single config value for an app
USAGE
$ heroku config:get KEY...
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-s, --shell output config vars in shell format
EXAMPLES
$ heroku config:get RAILS_ENV
production
コードを参照: @heroku-cli/plugin-config
heroku config:set
1 つ以上の環境設定を設定します。
set one or more config vars
USAGE
$ heroku config:set
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
EXAMPLES
$ heroku config:set RAILS_ENV=staging
Setting config vars and restarting example... done, v10
RAILS_ENV: staging
$ heroku config:set RAILS_ENV=staging RACK_ENV=staging
Setting config vars and restarting example... done, v11
RAILS_ENV: staging
RACK_ENV: staging
heroku config:unset
1 つ以上の環境設定を設定解除します。
unset one or more config vars
USAGE
$ heroku config:unset
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
ALIASES
$ heroku config:remove
EXAMPLES
$ heroku config:unset RAILS_ENV
Unsetting RAILS_ENV and restarting example... done, v10
$ heroku config:unset RAILS_ENV RACK_ENV
Unsetting RAILS_ENV, RACK_ENV and restarting example... done, v10
コードを参照: @heroku-cli/plugin-config
heroku container
コンテナを使用して Heroku アプリをビルドしてデプロイします。
Use containers to build and deploy Heroku apps
USAGE
$ heroku container
heroku container:login
Heroku Container Registry にログインします。
log in to Heroku Container Registry
Usage:
heroku container:login
USAGE
$ heroku container:login
OPTIONS
-v, --verbose
DESCRIPTION
Usage:
heroku container:login
heroku container:logout
Heroku Container Registry からログアウトします。
log out from Heroku Container Registry
USAGE
$ heroku container:logout
OPTIONS
-v, --verbose
heroku container:pull
アプリのプロセスタイプからイメージをプルします。
pulls an image from an app's process type
Usage:
heroku container:pull web # Pulls the web image from the app
heroku container:pull web worker # Pulls both the web and worker images from the app
heroku container:pull web:latest # Pulls the latest tag from the web image
USAGE
$ heroku container:pull
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-v, --verbose
DESCRIPTION
Usage:
heroku container:pull web # Pulls the web image from the app
heroku container:pull web worker # Pulls both the web and worker images from the app
heroku container:pull web:latest # Pulls the latest tag from the web image
heroku container:push
Docker イメージをビルドした後、プッシュして Heroku アプリにデプロイします。
builds, then pushes Docker images to deploy your Heroku app
USAGE
$ heroku container:push
OPTIONS
-R, --recursive pushes Dockerfile.<process> found in current and subdirectories
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-v, --verbose
--arg=arg set build-time variables
--context-path=context-path path to use as build context (defaults to Dockerfile dir)
EXAMPLES
heroku container:push web # Pushes Dockerfile to web process type
heroku container:push worker # Pushes Dockerfile to worker process type
heroku container:push web worker --recursive # Pushes Dockerfile.web and Dockerfile.worker
heroku container:push --recursive # Pushes Dockerfile.*
heroku container:push web --arg ENV=live,HTTPS=on # Build-time variables
heroku container:push --recursive --context-path . # Pushes Dockerfile.* using current dir as build context
heroku container:release
以前にプッシュされた Docker イメージを Heroku アプリにリリースします。
Releases previously pushed Docker images to your Heroku app
Usage:
heroku container:release web # Releases the previously pushed web process type
heroku container:release web worker # Releases the previously pushed web and worker process types
USAGE
$ heroku container:release
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-v, --verbose
DESCRIPTION
Usage:
heroku container:release web # Releases the previously pushed web process type
heroku container:release web worker # Releases the previously pushed web and worker process types
heroku container:rm
アプリのプロセスタイプを削除します。
remove the process type from your app
Usage:
heroku container:rm web # Destroys the web container
heroku container:rm web worker # Destroys the web and worker containers
USAGE
$ heroku container:rm
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Usage:
heroku container:rm web # Destroys the web container
heroku container:rm web worker # Destroys the web and worker containers
heroku container:run
Docker イメージをビルドした後、ローカルで実行します。
builds, then runs the docker image locally
Usage:
heroku container:run web bash # Runs bash on the local web docker container
heroku container:run worker # Runs the container CMD on the local worker container
USAGE
$ heroku container:run
OPTIONS
-a, --app=app (required) app to run command against
-p, --port=port port the app will run on
-r, --remote=remote git remote of app to use
-v, --verbose
DESCRIPTION
Usage:
heroku container:run web bash # Runs bash on the local web docker container
heroku container:run worker # Runs the container CMD on the local worker container
heroku domains
アプリのドメインを一覧表示します。
list domains for an app
USAGE
$ heroku domains
OPTIONS
-a, --app=app (required) app to run command against
-h, --help show CLI help
-j, --json output in json format
-r, --remote=remote git remote of app to use
-x, --extended show extra columns
--columns=columns only show provided columns (comma-separated)
--csv output is csv format
--filter=filter filter property by partial string matching, ex: name=foo
--no-header hide table header from output
--sort=sort property to sort by (prepend '-' for descending)
EXAMPLES
$ heroku domains
=== example Heroku Domain
example.herokuapp.com
=== example Custom Domains
Domain Name DNS Record Type DNS Target
www.example.com CNAME www.example.herokudns.com
$ heroku domains --filter 'Domain Name=www.example.com'
コードを参照: @heroku-cli/plugin-apps
heroku domains:add HOSTNAME
アプリにドメインを追加します。
add a domain to an app
USAGE
$ heroku domains:add HOSTNAME
OPTIONS
-a, --app=app (required) app to run command against
-c, --cert=cert the name of the SSL cert you want to use for this domain
-h, --help show CLI help
-j, --json output in json format
-r, --remote=remote git remote of app to use
--wait
EXAMPLE
heroku domains:add www.example.com
コードを参照: @heroku-cli/plugin-apps
heroku domains:clear
アプリからすべてのドメインを削除します。
remove all domains from an app
USAGE
$ heroku domains:clear
OPTIONS
-a, --app=app (required) app to run command against
-h, --help show CLI help
-r, --remote=remote git remote of app to use
EXAMPLE
heroku domains:clear
コードを参照: @heroku-cli/plugin-apps
heroku domains:info HOSTNAME
アプリのドメインに関する詳細情報を表示します。
show detailed information for a domain on an app
USAGE
$ heroku domains:info HOSTNAME
OPTIONS
-a, --app=app (required) app to run command against
-h, --help show CLI help
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku domains:info www.example.com
コードを参照: @heroku-cli/plugin-apps
heroku domains:remove HOSTNAME
アプリからドメインを削除します。
remove a domain from an app
USAGE
$ heroku domains:remove HOSTNAME
OPTIONS
-a, --app=app (required) app to run command against
-h, --help show CLI help
-r, --remote=remote git remote of app to use
EXAMPLE
heroku domains:remove www.example.com
コードを参照: @heroku-cli/plugin-apps
heroku domains:update [HOSTNAME]
異なる SSL 証明書をアプリで使用するようにドメインを更新します。
update a domain to use a different SSL certificate on an app
USAGE
$ heroku domains:update [HOSTNAME]
OPTIONS
-a, --app=app (required) app to run command against
-h, --help show CLI help
-r, --remote=remote git remote of app to use
--cert=cert (required) the name or id of the certificate you want to use for this domain
EXAMPLE
heroku domains:update www.example.com --cert mycert
コードを参照: @heroku-cli/plugin-apps
heroku domains:wait [HOSTNAME]
アプリのドメインがアクティブになるまで待ちます。
wait for domain to be active for an app
USAGE
$ heroku domains:wait [HOSTNAME]
OPTIONS
-a, --app=app (required) app to run command against
-h, --help show CLI help
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-apps
heroku drains
アプリのログドレインを表示します。
display the log drains of an app
USAGE
$ heroku drains
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json output in json format
heroku drains:add URL
アプリにログドレインを追加します。
adds a log drain to an app
USAGE
$ heroku drains:add URL
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku drains:remove [URL|TOKEN]
アプリからログドレインを削除します。
removes a log drain from an app
USAGE
$ heroku drains:remove [URL|TOKEN]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku dyno:kill DYNO
アプリの dyno を停止します。
stop app dyno
stop app dyno or dyno type
USAGE
$ heroku dyno:kill DYNO
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
stop app dyno or dyno type
EXAMPLES
$ heroku ps:stop run.1828
Stopping run.1828 dyno... done
$ heroku ps:stop run
Stopping run dynos... done
heroku dyno:resize
dyno サイズを管理します。
manage dyno sizes
Called with no arguments shows the current dyno size.
Called with one argument sets the size.
Where SIZE is one of eco|basic|standard-1x|standard-2x|performance
Called with 1..n TYPE=SIZE arguments sets the quantity per type.
USAGE
$ heroku dyno:resize
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Called with no arguments shows the current dyno size.
Called with one argument sets the size.
Where SIZE is one of eco|basic|standard-1x|standard-2x|performance
Called with 1..n TYPE=SIZE arguments sets the quantity per type.
heroku dyno:restart [DYNO]
アプリの dyno を再起動します。
restart app dynos
if DYNO is not specified, restarts all dynos on app
USAGE
$ heroku dyno:restart [DYNO]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
if DYNO is not specified, restarts all dynos on app
EXAMPLES
$ heroku ps:restart web.1
Restarting web.1 dyno... done
$ heroku ps:restart web
Restarting web dynos... done
$ heroku ps:restart
Restarting dynos... done
heroku dyno:scale
dyno の数量をスケールアップまたはスケールダウンします。
scale dyno quantity up or down
Appending a size (eg. web=2:Standard-2X) allows simultaneous scaling and resizing.
Omitting any arguments will display the app's current dyno formation, in a
format suitable for passing back into ps:scale.
USAGE
$ heroku dyno:scale
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Appending a size (eg. web=2:Standard-2X) allows simultaneous scaling and resizing.
Omitting any arguments will display the app's current dyno formation, in a
format suitable for passing back into ps:scale.
EXAMPLES
$ heroku ps:scale web=3:Standard-2X worker+1
Scaling dynos... done, now running web at 3:Standard-2X, worker at 1:Standard-1X.
$ heroku ps:scale
web=3:Standard-2X worker=1:Standard-1X
heroku dyno:stop DYNO
アプリの dyno を停止します。
stop app dyno
stop app dyno or dyno type
USAGE
$ heroku dyno:stop DYNO
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
stop app dyno or dyno type
EXAMPLES
$ heroku ps:stop run.1828
Stopping run.1828 dyno... done
$ heroku ps:stop run
Stopping run dynos... done
heroku features
使用可能なアプリ機能を一覧表示します。
list available app features
USAGE
$ heroku features
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json output in json format
heroku features:disable FEATURE
アプリ機能を無効にします。
disables an app feature
USAGE
$ heroku features:disable FEATURE
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku features:enable FEATURE
アプリ機能を有効にします。
enables an app feature
USAGE
$ heroku features:enable FEATURE
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku features:info FEATURE
機能に関する情報を表示します。
display information about a feature
USAGE
$ heroku features:info FEATURE
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json output in json format
heroku git:clone [DIRECTORY]
Heroku アプリをローカルマシンの DIRECTORY (デフォルトではアプリ名) に複製します。
clones a heroku app to your local machine at DIRECTORY (defaults to app name)
USAGE
$ heroku git:clone [DIRECTORY]
ARGUMENTS
DIRECTORY where to clone the app
OPTIONS
-a, --app=app (required) the Heroku app to use
-r, --remote=remote the git remote to create, default "heroku"
EXAMPLES
$ heroku git:clone -a example
Cloning into 'example'...
remote: Counting objects: 42, done.
...
コードを参照: @heroku-cli/plugin-git
heroku git:remote
アプリリポジトリに Git リモートを追加します。
adds a git remote to an app repo
extra arguments will be passed to git remote add
USAGE
$ heroku git:remote
OPTIONS
-a, --app=app the Heroku app to use
-r, --remote=remote the git remote to create
DESCRIPTION
extra arguments will be passed to git remote add
EXAMPLES
# set git remote heroku to https://git.heroku.com/example.git
$ heroku git:remote -a example
# set git remote heroku-staging to https://git.heroku.com/example.git
$ heroku git:remote --remote heroku-staging -a example
コードを参照: @heroku-cli/plugin-git
heroku help [COMMAND]
Heroku のヘルプを表示します。
display help for <%= config.bin %>
USAGE
$ heroku help [COMMAND]
ARGUMENTS
COMMAND command to show help for
OPTIONS
--all see all commands in CLI
コードを参照: @oclif/plugin-help
heroku join
チームアプリに自分自身を追加します。
add yourself to a team app
USAGE
$ heroku join
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku keys
SSH キーを表示します。
display your SSH keys
USAGE
$ heroku keys
OPTIONS
-l, --long display full SSH keys
--json output in json format
heroku keys:add [KEY]
ユーザーの SSH キーを追加します。
add an SSH key for a user
if no KEY is specified, will try to find ~/.ssh/id_rsa.pub
USAGE
$ heroku keys:add [KEY]
OPTIONS
-y, --yes automatically answer yes for all prompts
DESCRIPTION
if no KEY is specified, will try to find ~/.ssh/id_rsa.pub
EXAMPLES
$ heroku keys:add
Could not find an existing public key.
Would you like to generate one? [Yn] y
Generating new SSH public key.
Uploading SSH public key /.ssh/id_rsa.pub... done
$ heroku keys:add /my/key.pub
Uploading SSH public key /my/key.pub... done
heroku keys:clear
現在のユーザーのすべての SSH キーを削除します。
remove all SSH keys for current user
USAGE
$ heroku keys:clear
heroku keys:remove KEY
ユーザーの SSH キーを削除します。
remove an SSH key from the user
USAGE
$ heroku keys:remove KEY
EXAMPLES
$ heroku keys:remove email@example.com
Removing email@example.com SSH key... done
heroku labs
試験的な機能を一覧表示します。
list experimental features
USAGE
$ heroku labs
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--json display as json
heroku labs:disable [FEATURE]
試験的な機能を無効にします。
disables an experimental feature
USAGE
$ heroku labs:disable [FEATURE]
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--confirm=confirm
コードを参照: @heroku-cli/plugin-auth
heroku labs:enable FEATURE
試験的な機能を有効にします。
enables an experimental feature
USAGE
$ heroku labs:enable FEATURE
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
heroku labs:info FEATURE
機能情報を表示します。
show feature info
USAGE
$ heroku labs:info FEATURE
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--json display as json
heroku leave
チームアプリから自分自身を削除します。
remove yourself from a team app
USAGE
$ heroku leave
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku local [PROCESSNAME]
Heroku アプリをローカルで実行します。
run heroku app locally
Start the application specified by a Procfile (defaults to ./Procfile)
USAGE
$ heroku local [PROCESSNAME]
OPTIONS
-e, --env=env location of env file (defaults to .env)
-f, --procfile=procfile use a different Procfile
-p, --port=port port to listen on
DESCRIPTION
Start the application specified by a Procfile (defaults to ./Procfile)
ALIASES
$ heroku local:start
EXAMPLE
$ heroku local
$ heroku local web
$ heroku local web=2
$ heroku local web=1,worker=2
コードを参照: @heroku-cli/plugin-local
heroku local:run
単発コマンドを実行します。
run a one-off command
USAGE
$ heroku local:run
OPTIONS
-e, --env=env
-p, --port=port
EXAMPLE
$ heroku local:run bin/migrate
コードを参照: @heroku-cli/plugin-local
heroku local:version
node-foreman バージョンを表示します。
display node-foreman version
USAGE
$ heroku local:version
コードを参照: @heroku-cli/plugin-local
heroku lock
チームメンバーがアプリに参加できないようにします。
prevent team members from joining an app
USAGE
$ heroku lock
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku logs
最新のログ出力を表示します。
display recent log output
disable colors with --no-color, HEROKU_LOGS_COLOR=0, or HEROKU_COLOR=0
USAGE
$ heroku logs
OPTIONS
-a, --app=app (required) app to run command against
-d, --dyno=dyno only show output from this dyno type (such as "web" or "worker")
-n, --num=num number of lines to display
-r, --remote=remote git remote of app to use
-s, --source=source only show output from this source (such as "app" or "heroku")
-t, --tail continually stream logs
--force-colors force use of colors (even on non-tty output)
DESCRIPTION
disable colors with --no-color, HEROKU_LOGS_COLOR=0, or HEROKU_COLOR=0
EXAMPLES
$ heroku logs --app=my-app
$ heroku logs --num=50
$ heroku logs --dyno=web --app=my-app
$ heroku logs --app=my-app --tail
コードを参照: @heroku-cli/plugin-run
heroku maintenance
アプリの現在のメンテナンスステータスを表示します。
display the current maintenance status of app
USAGE
$ heroku maintenance
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku maintenance:off
アプリをメンテナンスモードから移行します。
take the app out of maintenance mode
USAGE
$ heroku maintenance:off
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku maintenance:on
アプリをメンテナンスモードにします。
put the app into maintenance mode
USAGE
$ heroku maintenance:on
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku members
チームのメンバーを一覧表示します。
list members of a team
USAGE
$ heroku members
OPTIONS
-r, --role=role filter by role
-t, --team=team team to use
--json output in json format
--pending filter by pending team invitations
heroku members:add EMAIL
チームにユーザーを追加します。
adds a user to a team
USAGE
$ heroku members:add EMAIL
OPTIONS
-r, --role=role (required) member role (admin, collaborator, member, owner)
-t, --team=team team to use
heroku members:remove EMAIL
チームからユーザーを削除します。
removes a user from a team
USAGE
$ heroku members:remove EMAIL
OPTIONS
-t, --team=team team to use
heroku members:set EMAIL
チーム内のメンバーロールを設定します。
sets a members role in a team
USAGE
$ heroku members:set EMAIL
OPTIONS
-r, --role=role (required) member role (admin, collaborator, member, owner)
-t, --team=team team to use
heroku notifications
通知を表示します。
display notifications
USAGE
$ heroku notifications
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--all view all notifications (not just the ones for the current app)
--json output in json format
--read show notifications already read
heroku orgs
自分がメンバーになっているチームを一覧表示します。
list the teams that you are a member of
USAGE
$ heroku orgs
OPTIONS
--enterprise filter by enterprise teams
--json output in json format
heroku orgs:open
ブラウザウィンドウでチームインターフェースを開きます。
open the team interface in a browser window
USAGE
$ heroku orgs:open
OPTIONS
-t, --team=team team to use
heroku pg [DATABASE]
データベース情報を表示します。
show database information
USAGE
$ heroku pg [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:backups
データベースバックアップを一覧表示します。
list database backups
USAGE
$ heroku pg:backups
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:backups:cancel [BACKUP_ID]
進行中のバックアップまたは復元 (デフォルトでは最新) をキャンセルします。
cancel an in-progress backup or restore (default newest)
USAGE
$ heroku pg:backups:cancel [BACKUP_ID]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:backups:capture [DATABASE]
新しいバックアップを取得します。
capture a new backup
USAGE
$ heroku pg:backups:capture [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-v, --verbose
--wait-interval=wait-interval
heroku pg:backups:delete BACKUP_ID
バックアップを削除します。
delete a backup
USAGE
$ heroku pg:backups:delete BACKUP_ID
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
heroku pg:backups:download [BACKUP_ID]
データベースバックアップをダウンロードします。
downloads database backup
USAGE
$ heroku pg:backups:download [BACKUP_ID]
OPTIONS
-a, --app=app (required) app to run command against
-o, --output=output location to download to. Defaults to latest.dump
-r, --remote=remote git remote of app to use
heroku pg:backups:info [BACKUP_ID]
特定のバックアップに関する情報を取得します。
get information about a specific backup
USAGE
$ heroku pg:backups:info [BACKUP_ID]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:backups:restore [BACKUP] [DATABASE]
バックアップ (デフォルトでは最新) をデータベースに復元します。
restore a backup (default latest) to a database
defaults to saving the latest database to DATABASE_URL
USAGE
$ heroku pg:backups:restore [BACKUP] [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-e, --extensions=extensions comma-separated list of extensions to pre-install in the public schema
-r, --remote=remote git remote of app to use
-v, --verbose
--wait-interval=wait-interval
DESCRIPTION
defaults to saving the latest database to DATABASE_URL
heroku pg:backups:schedule [DATABASE]
指定されたデータベースの日次バックアップをスケジュールします。
schedule daily backups for given database
USAGE
$ heroku pg:backups:schedule [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--at=at (required) at a specific (24h) hour in the given timezone. Defaults to UTC. --at '[HOUR]:00
[TIMEZONE]'
heroku pg:backups:schedules
バックアップスケジュールを一覧表示します。
list backup schedule
USAGE
$ heroku pg:backups:schedules
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:backups:unschedule [DATABASE]
日次バックアップを停止します。
stop daily backups
USAGE
$ heroku pg:backups:unschedule [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:backups:url [BACKUP_ID]
秘密のバックアップ URL (ただしインターネットからアクセス可能) を取得します。
get secret but publicly accessible URL of a backup
USAGE
$ heroku pg:backups:url [BACKUP_ID]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:bloat [DATABASE]
無駄の多さで順序付けられたデータベース内のテーブルとインデックスの肥大化を表示します。
show table and index bloat in your database ordered by most wasteful
USAGE
$ heroku pg:bloat [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:blocking [DATABASE]
他のクエリが解放されるのを待っているロックを保持しているクエリを表示します。
display queries holding locks other queries are waiting to be released
USAGE
$ heroku pg:blocking [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:connection-pooling:attach [DATABASE]
接続プールを使用してデータベースにアタッチメントを追加します。
add an attachment to a database using connection pooling
Example:
heroku pg:connection-pooling:attach postgresql-something-12345
USAGE
$ heroku pg:connection-pooling:attach [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--as=as name for add-on attachment
DESCRIPTION
Example:
heroku pg:connection-pooling:attach postgresql-something-12345
heroku pg:copy SOURCE TARGET
ソース DB からターゲットにすべてのデータをコピーします。
copy all data from source db to target
at least one of the databases must be a Heroku PostgreSQL DB
USAGE
$ heroku pg:copy SOURCE TARGET
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--confirm=confirm
--verbose
--wait-interval=wait-interval
DESCRIPTION
at least one of the databases must be a Heroku PostgreSQL DB
heroku pg:credentials [DATABASE]
データベース内の資格情報に関する情報を表示します。
show information on credentials in the database
USAGE
$ heroku pg:credentials [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:credentials:create [DATABASE]
データベース内に資格情報を作成します。
create credential within database
Example:
heroku pg:credentials:create postgresql-something-12345 --name new-cred-name
USAGE
$ heroku pg:credentials:create [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-n, --name=name (required) name of the new credential within the database
-r, --remote=remote git remote of app to use
DESCRIPTION
Example:
heroku pg:credentials:create postgresql-something-12345 --name new-cred-name
heroku pg:credentials:destroy [DATABASE]
データベース内の資格情報を破棄します。
destroy credential within database
Example:
heroku pg:credentials:destroy postgresql-transparent-56874 --name cred-name -a woodstock-production
USAGE
$ heroku pg:credentials:destroy [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-n, --name=name (required) unique identifier for the credential
-r, --remote=remote git remote of app to use
DESCRIPTION
Example:
heroku pg:credentials:destroy postgresql-transparent-56874 --name cred-name -a woodstock-production
heroku pg:credentials:repair-default [DATABASE]
データベース内のデフォルトの資格情報のアクセス許可を修復します。
repair the permissions of the default credential within database
Example:
heroku pg:credentials:repair-default postgresql-something-12345
USAGE
$ heroku pg:credentials:repair-default [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
DESCRIPTION
Example:
heroku pg:credentials:repair-default postgresql-something-12345
heroku pg:credentials:rotate [DATABASE]
データベースの資格情報を定期的に変更します。
rotate the database credentials
USAGE
$ heroku pg:credentials:rotate [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-n, --name=name which credential to rotate (default credentials if not specified)
-r, --remote=remote git remote of app to use
--all rotate all credentials
--force forces rotating the targeted credentials
heroku pg:credentials:url [DATABASE]
データベースの資格情報に関する情報を表示します。
show information on a database credential
USAGE
$ heroku pg:credentials:url [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-n, --name=name which credential to show (default credentials if not specified)
-r, --remote=remote git remote of app to use
heroku pg:diagnose [DATABASE|REPORT_ID]
診断レポートを実行または表示します。
run or view diagnostics report
defaults to DATABASE_URL database if no DATABASE is specified
if REPORT_ID is specified instead, a previous report is displayed
USAGE
$ heroku pg:diagnose [DATABASE|REPORT_ID]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json format output as JSON
DESCRIPTION
defaults to DATABASE_URL database if no DATABASE is specified
if REPORT_ID is specified instead, a previous report is displayed
heroku pg:info [DATABASE]
データベース情報を表示します。
show database information
USAGE
$ heroku pg:info [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:kill PID [DATABASE]
クエリを強制終了します。
kill a query
USAGE
$ heroku pg:kill PID [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-f, --force
-r, --remote=remote git remote of app to use
heroku pg:killall [DATABASE]
すべての資格情報のすべての接続を終了します。
terminates all connections for all credentials
USAGE
$ heroku pg:killall [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:links [DATABASE]
すべてのデータベースとリンクに関する情報を一覧表示します。
lists all databases and information on link
USAGE
$ heroku pg:links [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:links:create REMOTE DATABASE
データストア間のリンクを作成します。
create a link between data stores
Example:
heroku pg:links:create HEROKU_REDIS_RED HEROKU_POSTGRESQL_CERULEAN
USAGE
$ heroku pg:links:create REMOTE DATABASE
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--as=as name of link to create
DESCRIPTION
Example:
heroku pg:links:create HEROKU_REDIS_RED HEROKU_POSTGRESQL_CERULEAN
heroku pg:links:destroy DATABASE LINK
データストア間のリンクを破棄します。
destroys a link between data stores
Example:
heroku pg:links:destroy HEROKU_POSTGRESQL_CERULEAN redis-symmetrical-100
USAGE
$ heroku pg:links:destroy DATABASE LINK
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
DESCRIPTION
Example:
heroku pg:links:destroy HEROKU_POSTGRESQL_CERULEAN redis-symmetrical-100
heroku pg:locks [DATABASE]
アクティブなロックを持つクエリを表示します。
display queries with active locks
USAGE
$ heroku pg:locks [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-t, --truncate truncates queries to 40 charaters
heroku pg:maintenance [DATABASE]
現在のメンテナンス情報を表示します。
show current maintenance information
USAGE
$ heroku pg:maintenance [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:maintenance:run [DATABASE]
メンテナンスを開始します。
start maintenance
USAGE
$ heroku pg:maintenance:run [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-f, --force
-r, --remote=remote git remote of app to use
heroku pg:maintenance:window DATABASE WINDOW
週次メンテナンスウィンドウを設定します。
set weekly maintenance window
All times are in UTC.
Example:
heroku pg:maintenance:window postgres-slippery-100 "Sunday 06:00"
USAGE
$ heroku pg:maintenance:window DATABASE WINDOW
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
All times are in UTC.
Example:
heroku pg:maintenance:window postgres-slippery-100 "Sunday 06:00"
heroku pg:outliers [DATABASE]
全体として最長の実行時間を持つ 10 個のクエリを表示します。
show 10 queries that have longest execution time in aggregate
USAGE
$ heroku pg:outliers [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-n, --num=num the number of queries to display (default: 10)
-r, --remote=remote git remote of app to use
-t, --truncate truncate queries to 40 characters
--reset resets statistics gathered by pg_stat_statements
heroku pg:promote DATABASE
sets DATABASE as your DATABASE_URL
sets DATABASE as your DATABASE_URL
USAGE
$ heroku pg:promote DATABASE
OPTIONS
-a, --app=app (required) app to run command against
-f, --force
-r, --remote=remote git remote of app to use
heroku pg:ps [DATABASE]
アクティブなクエリを実行時間と共に表示します。
view active queries with execution time
USAGE
$ heroku pg:ps [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-v, --verbose
heroku pg:psql [DATABASE]
データベースへの psql シェルを開きます。
open a psql shell to the database
USAGE
$ heroku pg:psql [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --command=command SQL command to run
-f, --file=file SQL file to run
-r, --remote=remote git remote of app to use
--credential=credential credential to use
heroku pg:pull SOURCE TARGET
Heroku データベースをローカルまたはリモートデータベースにプルします。
pull Heroku database into local or remote database
Pull from SOURCE into TARGET.
TARGET must be one of:
* a database name (i.e. on a local PostgreSQL server) => TARGET must not exist and will be created
* a fully qualified URL to a local PostgreSQL server => TARGET must not exist and will be created
* a fully qualified URL to a remote PostgreSQL server => TARGET must exist and be empty
To delete a local database run `dropdb TARGET`
To create an empty remote database, run `createdb` with connection command-line options (run `createdb --help` for details).
Examples:
# pull Heroku DB named postgresql-swimmingly-100 into local DB mylocaldb that must not exist
$ heroku pg:pull postgresql-swimmingly-100 mylocaldb --app sushi
# pull Heroku DB named postgresql-swimmingly-100 into empty remote DB at postgres://myhost/mydb
$ heroku pg:pull postgresql-swimmingly-100 postgres://myhost/mydb --app sushi
USAGE
$ heroku pg:pull SOURCE TARGET
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--exclude-table-data=exclude-table-data tables for which data should be excluded (use ';' to split multiple names)
DESCRIPTION
Pull from SOURCE into TARGET.
TARGET must be one of:
* a database name (i.e. on a local PostgreSQL server) => TARGET must not exist and will be created
* a fully qualified URL to a local PostgreSQL server => TARGET must not exist and will be created
* a fully qualified URL to a remote PostgreSQL server => TARGET must exist and be empty
To delete a local database run `dropdb TARGET`
To create an empty remote database, run `createdb` with connection command-line options (run `createdb --help` for
details).
Examples:
# pull Heroku DB named postgresql-swimmingly-100 into local DB mylocaldb that must not exist
$ heroku pg:pull postgresql-swimmingly-100 mylocaldb --app sushi
# pull Heroku DB named postgresql-swimmingly-100 into empty remote DB at postgres://myhost/mydb
$ heroku pg:pull postgresql-swimmingly-100 postgres://myhost/mydb --app sushi
heroku pg:push SOURCE TARGET
ローカルまたはリモートを Heroku データベースにプッシュします。
push local or remote into Heroku database
Push from SOURCE into TARGET. TARGET must be empty.
To empty a Heroku database for push run `heroku pg:reset`
SOURCE must be either the name of a database existing on your localhost or the
fully qualified URL of a remote database.
Examples:
# push mylocaldb into a Heroku DB named postgresql-swimmingly-100
$ heroku pg:push mylocaldb postgresql-swimmingly-100
# push remote DB at postgres://myhost/mydb into a Heroku DB named postgresql-swimmingly-100
$ heroku pg:push postgres://myhost/mydb postgresql-swimmingly-100
USAGE
$ heroku pg:push SOURCE TARGET
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--exclude-table-data=exclude-table-data tables for which data should be excluded (use ';' to split multiple names)
DESCRIPTION
Push from SOURCE into TARGET. TARGET must be empty.
To empty a Heroku database for push run `heroku pg:reset`
SOURCE must be either the name of a database existing on your localhost or the
fully qualified URL of a remote database.
Examples:
# push mylocaldb into a Heroku DB named postgresql-swimmingly-100
$ heroku pg:push mylocaldb postgresql-swimmingly-100
# push remote DB at postgres://myhost/mydb into a Heroku DB named postgresql-swimmingly-100
$ heroku pg:push postgres://myhost/mydb postgresql-swimmingly-100
heroku pg:reset [DATABASE]
データベース内のすべてのデータを削除します。
delete all data in DATABASE
USAGE
$ heroku pg:reset [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-e, --extensions=extensions comma-separated list of extensions to pre-install in the public schema
-r, --remote=remote git remote of app to use
heroku pg:settings [DATABASE]
現在のデータベース設定を表示します。
show your current database settings
USAGE
$ heroku pg:settings [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:settings:log-lock-waits [VALUE] [DATABASE]
セッションがロックを取得するために deadlock_timeout より長い時間待ったときにログメッセージを生成するかどうかを制御します。deadlock_timeout は 1 秒に設定されています。
Controls whether a log message is produced when a session waits longer than the deadlock_timeout to acquire a lock. deadlock_timeout is set to 1 second
Delays due to lock contention occur when multiple transactions are trying to access the same resource at the same time.
Applications and their query patterns should try to avoid changes to many different tables within the same transaction.
USAGE
$ heroku pg:settings:log-lock-waits [VALUE] [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Delays due to lock contention occur when multiple transactions are trying to access the same resource at the same
time.
Applications and their query patterns should try to avoid changes to many different tables within the same
transaction.
heroku pg:settings:log-min-duration-statement [VALUE] [DATABASE]
ステートメントが VALUE で指定された時間の後に完了した場合は、完了した各ステートメントの期間がログに記録されます。
The duration of each completed statement will be logged if the statement completes after the time specified by VALUE.
VALUE needs to specified as a whole number, in milliseconds.
Setting log_min_duration_statement to zero prints all statement durations and -1 will disable logging statement durations.
USAGE
$ heroku pg:settings:log-min-duration-statement [VALUE] [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
VALUE needs to specified as a whole number, in milliseconds.
Setting log_min_duration_statement to zero prints all statement durations and -1 will disable logging statement
durations.
heroku pg:settings:log-statement [VALUE] [DATABASE]
log_statement は、どの SQL ステートメントをログに記録するかを制御します。
log_statement controls which SQL statements are logged.
Valid values for VALUE:
none - No statements are logged
ddl - All data definition statements, such as CREATE, ALTER and DROP will be logged
mod - Includes all statements from ddl as well as data-modifying statements such as INSERT, UPDATE, DELETE, TRUNCATE, COPY
all - All statements are logged
USAGE
$ heroku pg:settings:log-statement [VALUE] [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Valid values for VALUE:
none - No statements are logged
ddl - All data definition statements, such as CREATE, ALTER and DROP will be logged
mod - Includes all statements from ddl as well as data-modifying statements such as INSERT, UPDATE, DELETE, TRUNCATE,
COPY
all - All statements are logged
heroku pg:settings:track-functions [VALUE] [DATABASE]
track_functions は、関数呼び出しカウントと使用された時間の追跡を制御します。デフォルトは none (なし) です。
track_functions controls tracking of function call counts and time used. Default is none.
Valid values for VALUE:
none - No functions are tracked
pl - Only procedural language functions are tracked
all - All functions, including SQL and C language functions, are tracked. Simple SQL-language that are inlined are not tracked
USAGE
$ heroku pg:settings:track-functions [VALUE] [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Valid values for VALUE:
none - No functions are tracked
pl - Only procedural language functions are tracked
all - All functions, including SQL and C language functions, are tracked. Simple SQL-language that are inlined are
not tracked
heroku pg:unfollow DATABASE
レプリカのフォローを停止し、それを書き込み可能なデータベースにします。
stop a replica from following and make it a writeable database
USAGE
$ heroku pg:unfollow DATABASE
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
heroku pg:upgrade [DATABASE]
データベースをフォロー解除し、それを最新の安定した PostgreSQL バージョンにアップグレードします。
unfollow a database and upgrade it to the latest stable PostgreSQL version
to upgrade to another PostgreSQL version, use pg:copy instead
USAGE
$ heroku pg:upgrade [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
-v, --version=version PostgreSQL version to upgrade to
DESCRIPTION
to upgrade to another PostgreSQL version, use pg:copy instead
heroku pg:vacuum-stats [DATABASE]
使用されなくなった行と、自動バキュームのトリガーが予測されるかどうかを表示します。
show dead rows and whether an automatic vacuum is expected to be triggered
USAGE
$ heroku pg:vacuum-stats [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku pg:wait [DATABASE]
データベースが使用可能になるまでブロックします。
blocks until database is available
USAGE
$ heroku pg:wait [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--no-notify do not show OS notification
--wait-interval=wait-interval how frequently to poll in seconds (to avoid rate limiting)
heroku pipelines
アクセスできるパイプラインを一覧表示します。
list pipelines you have access to
USAGE
$ heroku pipelines
OPTIONS
--json output in json format
EXAMPLE
$ heroku pipelines
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:add PIPELINE
このアプリをパイプラインに追加します。
add this app to a pipeline
The app and pipeline names must be specified.
The stage of the app will be guessed based on its name if not specified.
USAGE
$ heroku pipelines:add PIPELINE
ARGUMENTS
PIPELINE name of pipeline
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-s, --stage=stage stage of first app in pipeline
DESCRIPTION
The app and pipeline names must be specified.
The stage of the app will be guessed based on its name if not specified.
EXAMPLE
$ heroku pipelines:add my-pipeline -a my-app -s production
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:connect NAME
github リポジトリを既存のパイプラインに接続します。
connect a github repo to an existing pipeline
USAGE
$ heroku pipelines:connect NAME
ARGUMENTS
NAME name of pipeline
OPTIONS
-r, --repo=repo (required) the GitHub repository to connect to
EXAMPLE
$ heroku pipelines:connect my-pipeline -r githuborg/reponame
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:create [NAME]
新しいパイプラインを作成します。
create a new pipeline
An existing app must be specified as the first app in the pipeline.
The pipeline name will be inferred from the app name if not specified.
The stage of the app will be guessed based on its name if not specified.
The pipeline owner will be the user creating the pipeline if not specified with -t for teams or -o for orgs.
USAGE
$ heroku pipelines:create [NAME]
ARGUMENTS
NAME name of pipeline (defaults to basename of the app)
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-s, --stage=stage stage of first app in pipeline
-t, --team=team the team which will own the apps
DESCRIPTION
An existing app must be specified as the first app in the pipeline.
The pipeline name will be inferred from the app name if not specified.
The stage of the app will be guessed based on its name if not specified.
The pipeline owner will be the user creating the pipeline if not specified with -t for teams or -o for orgs.
EXAMPLES
$ heroku pipelines:create -a my-app-staging
$ heroku pipelines:create my-pipeline -a my-app-staging
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:destroy PIPELINE
パイプラインを破棄します。
destroy a pipeline
USAGE
$ heroku pipelines:destroy PIPELINE
ARGUMENTS
PIPELINE name of pipeline
EXAMPLE
$ heroku pipelines:destroy my-pipeline
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:diff
このアプリの最新のリリースをそのダウンストリームアプリと比較します。
compares the latest release of this app to its downstream app(s)
USAGE
$ heroku pipelines:diff
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku pipelines:diff -a my-app-staging
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:info PIPELINE
パイプライン内のアプリの一覧を表示します。
show list of apps in a pipeline
USAGE
$ heroku pipelines:info PIPELINE
ARGUMENTS
PIPELINE pipeline to show list of apps for
OPTIONS
--json output in json format
EXAMPLE
$ heroku pipelines:info my-pipeline
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:open PIPELINE
ダッシュボードでパイプラインを開きます。
open a pipeline in dashboard
USAGE
$ heroku pipelines:open PIPELINE
ARGUMENTS
PIPELINE name of pipeline
EXAMPLE
$ heroku pipelines:open my-pipeline
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:promote
このアプリの最新のリリースをそのダウンストリームアプリにプロモートします。
promote the latest release of this app to its downstream app(s)
USAGE
$ heroku pipelines:promote
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-t, --to=to comma separated list of apps to promote to
EXAMPLE
$ heroku pipelines:promote -a my-app-staging
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:remove
このアプリをそのパイプラインから削除します。
remove this app from its pipeline
USAGE
$ heroku pipelines:remove
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku pipelines:remove -a my-app
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:rename PIPELINE NAME
パイプラインの名前を変更します。
rename a pipeline
USAGE
$ heroku pipelines:rename PIPELINE NAME
ARGUMENTS
PIPELINE current name of pipeline
NAME new name of pipeline
EXAMPLE
$ heroku pipelines:rename my-pipeline new-pipeline-name
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:setup [NAME] [REPO]
新しいパイプラインを一般的な設定で立ち上げ、本番アプリとステージングアプリを作成します (完全に形成された app.json がリポジトリ内に必要)。
bootstrap a new pipeline with common settings and create a production and staging app (requires a fully formed app.json in the repo)
USAGE
$ heroku pipelines:setup [NAME] [REPO]
ARGUMENTS
NAME name of pipeline
REPO a GitHub repository to connect the pipeline to
OPTIONS
-t, --team=team the team to assign pipeline ownership to (defaults to current user)
-y, --yes accept all default settings without prompting
EXAMPLE
$ heroku pipelines:setup my-pipeline githuborg/reponame -t my-team
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:transfer OWNER
パイプラインの所有権を移動します。
transfer ownership of a pipeline
USAGE
$ heroku pipelines:transfer OWNER
ARGUMENTS
OWNER the owner to transfer the pipeline to
OPTIONS
-c, --confirm=confirm
-p, --pipeline=pipeline (required) name of pipeline
EXAMPLES
$ heroku pipelines:transfer admin@example.com -p my-pipeline
$ heroku pipelines:transfer admin-team -p my-pipeline
コードを参照: @heroku-cli/plugin-pipelines
heroku pipelines:update
パイプライン内のアプリのステージを更新します。
update the app's stage in a pipeline
USAGE
$ heroku pipelines:update
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-s, --stage=stage (required) new stage of app
EXAMPLE
$ heroku pipelines:update -s staging -a my-app
コードを参照: @heroku-cli/plugin-pipelines
heroku plugins
インストールされているプラグインを一覧表示します。
list installed plugins
USAGE
$ heroku plugins
OPTIONS
--core show core plugins
EXAMPLE
$ heroku plugins
コードを参照: @oclif/plugin-plugins
heroku plugins:inspect PLUGIN...
プラグインのインストールプロパティを表示します。
displays installation properties of a plugin
USAGE
$ heroku plugins:inspect PLUGIN...
ARGUMENTS
PLUGIN [default: .] plugin to inspect
OPTIONS
-h, --help show CLI help
-v, --verbose
EXAMPLE
$ heroku plugins:inspect myplugin
コードを参照: @oclif/plugin-plugins
heroku plugins:install PLUGIN...
プラグインを CLI にインストールします。
installs a plugin into the CLI
Can be installed from npm or a git url.
Installation of a user-installed plugin will override a core plugin.
e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in the CLI without the need to patch and update the whole CLI.
USAGE
$ heroku plugins:install PLUGIN...
ARGUMENTS
PLUGIN plugin to install
OPTIONS
-f, --force yarn install with force flag
-h, --help show CLI help
-v, --verbose
DESCRIPTION
Can be installed from npm or a git url.
Installation of a user-installed plugin will override a core plugin.
e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
the CLI without the need to patch and update the whole CLI.
ALIASES
$ heroku plugins:add
EXAMPLES
$ heroku plugins:install myplugin
$ heroku plugins:install https://github.com/someuser/someplugin
$ heroku plugins:install someuser/someplugin
コードを参照: @oclif/plugin-plugins
heroku plugins:link PLUGIN
開発のためにプラグインを CLI にリンクします。
links a plugin into the CLI for development
Installation of a linked plugin will override a user-installed or core plugin.
e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello' command will override the user-installed or core plugin implementation. This is useful for development work.
USAGE
$ heroku plugins:link PLUGIN
ARGUMENTS
PATH [default: .] path to plugin
OPTIONS
-h, --help show CLI help
-v, --verbose
DESCRIPTION
Installation of a linked plugin will override a user-installed or core plugin.
e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
command will override the user-installed or core plugin implementation. This is useful for development work.
EXAMPLE
$ heroku plugins:link myplugin
コードを参照: @oclif/plugin-plugins
heroku plugins:uninstall PLUGIN...
CLI からプラグインを削除します。
removes a plugin from the CLI
USAGE
$ heroku plugins:uninstall PLUGIN...
ARGUMENTS
PLUGIN plugin to uninstall
OPTIONS
-h, --help show CLI help
-v, --verbose
ALIASES
$ heroku plugins:unlink
$ heroku plugins:remove
コードを参照: @oclif/plugin-plugins
heroku plugins:update
インストールされているプラグインを更新します。
update installed plugins
USAGE
$ heroku plugins:update
OPTIONS
-h, --help show CLI help
-v, --verbose
コードを参照: @oclif/plugin-plugins
heroku ps [TYPE [TYPE ...]]
アプリの dyno を一覧表示します。
list dynos for an app
USAGE
$ heroku ps [TYPE [TYPE ...]]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json display as json
EXAMPLES
$ heroku ps
=== run: one-off dyno
run.1: up for 5m: bash
=== web: bundle exec thin start -p $PORT
web.1: created for 30s
$ heroku ps run # specifying types
=== run: one-off dyno
run.1: up for 5m: bash
heroku ps:autoscale:disable
Web dyno のオートスケールを無効にします。
disable web dyno autoscaling
USAGE
$ heroku ps:autoscale:disable
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
コードを参照: @heroku-cli/plugin-ps
heroku ps:autoscale:enable
Web dyno のオートスケールを有効にします。
enable web dyno autoscaling
USAGE
$ heroku ps:autoscale:enable
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--max=max (required) maximum number of dynos
--min=min (required) minimum number of dynos
--notifications receive email notifications when the max dyno limit is reached
--p95=p95 desired p95 response time
コードを参照: @heroku-cli/plugin-ps
heroku ps:copy FILE
dyno からローカルファイルシステムにファイルをコピーします。
Copy a file from a dyno to the local filesystem
Example:
$ heroku ps:copy FILENAME --app murmuring-headland-14719
USAGE
$ heroku ps:copy FILE
OPTIONS
-a, --app=app (required) app to run command against
-d, --dyno=dyno specify the dyno to connect to
-o, --output=output the name of the output file
-r, --remote=remote git remote of app to use
DESCRIPTION
Example:
$ heroku ps:copy FILENAME --app murmuring-headland-14719
heroku ps:exec
dyno への SSH セッションを作成します。
Create an SSH session to a dyno
Example:
$ heroku ps:exec 'node -i' --app murmuring-headland-14719
USAGE
$ heroku ps:exec
OPTIONS
-a, --app=app (required) app to run command against
-d, --dyno=dyno specify the dyno to connect to
-r, --remote=remote git remote of app to use
--ssh use native ssh
--status lists the status of the SSH server in the dyno
DESCRIPTION
Example:
$ heroku ps:exec 'node -i' --app murmuring-headland-14719
heroku ps:forward PORT
ローカルポート上のトラフィックを dyno に転送します。
Forward traffic on a local port to a dyno
Provide a port or comma-separated list of ports to forward.
For example, "4000,9000:9001" will forward port 4000 to port 4000 and
port 9000 to port 9001.
Example:
$ heroku ps:forward 8080 --app murmuring-headland-14719
USAGE
$ heroku ps:forward PORT
OPTIONS
-a, --app=app (required) app to run command against
-d, --dyno=dyno specify the dyno to connect to
-r, --remote=remote git remote of app to use
DESCRIPTION
Provide a port or comma-separated list of ports to forward.
For example, "4000,9000:9001" will forward port 4000 to port 4000 and
port 9000 to port 9001.
Example:
$ heroku ps:forward 8080 --app murmuring-headland-14719
heroku ps:kill DYNO
アプリの dyno を停止します。
stop app dyno
stop app dyno or dyno type
USAGE
$ heroku ps:kill DYNO
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
stop app dyno or dyno type
EXAMPLES
$ heroku ps:stop run.1828
Stopping run.1828 dyno... done
$ heroku ps:stop run
Stopping run dynos... done
heroku ps:resize
dyno サイズを管理します。
manage dyno sizes
Called with no arguments shows the current dyno size.
Called with one argument sets the size.
Where SIZE is one of eco|basic|standard-1x|standard-2x|performance
Called with 1..n TYPE=SIZE arguments sets the quantity per type.
USAGE
$ heroku ps:resize
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Called with no arguments shows the current dyno size.
Called with one argument sets the size.
Where SIZE is one of eco|basic|standard-1x|standard-2x|performance
Called with 1..n TYPE=SIZE arguments sets the quantity per type.
heroku ps:restart [DYNO]
アプリの dyno を再起動します。
restart app dynos
if DYNO is not specified, restarts all dynos on app
USAGE
$ heroku ps:restart [DYNO]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
if DYNO is not specified, restarts all dynos on app
EXAMPLES
$ heroku ps:restart web.1
Restarting web.1 dyno... done
$ heroku ps:restart web
Restarting web dynos... done
$ heroku ps:restart
Restarting dynos... done
heroku ps:scale
dyno の数量をスケールアップまたはスケールダウンします。
scale dyno quantity up or down
Appending a size (eg. web=2:Standard-2X) allows simultaneous scaling and resizing.
Omitting any arguments will display the app's current dyno formation, in a
format suitable for passing back into ps:scale.
USAGE
$ heroku ps:scale
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Appending a size (eg. web=2:Standard-2X) allows simultaneous scaling and resizing.
Omitting any arguments will display the app's current dyno formation, in a
format suitable for passing back into ps:scale.
EXAMPLES
$ heroku ps:scale web=3:Standard-2X worker+1
Scaling dynos... done, now running web at 3:Standard-2X, worker at 1:Standard-1X.
$ heroku ps:scale
web=3:Standard-2X worker=1:Standard-1X
heroku ps:socks
dyno に SOCKS プロキシを起動します。
Launch a SOCKS proxy into a dyno
Example:
$ heroku ps:socks --app murmuring-headland-14719
Establishing credentials... done
SOCKSv5 proxy server started on port 1080
Use CTRL+C to stop the proxy
USAGE
$ heroku ps:socks
OPTIONS
-a, --app=app (required) app to run command against
-d, --dyno=dyno specify the dyno to connect to
-r, --remote=remote git remote of app to use
DESCRIPTION
Example:
$ heroku ps:socks --app murmuring-headland-14719
Establishing credentials... done
SOCKSv5 proxy server started on port 1080
Use CTRL+C to stop the proxy
heroku ps:stop DYNO
アプリの dyno を停止します。
stop app dyno
stop app dyno or dyno type
USAGE
$ heroku ps:stop DYNO
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
stop app dyno or dyno type
EXAMPLES
$ heroku ps:stop run.1828
Stopping run.1828 dyno... done
$ heroku ps:stop run
Stopping run dynos... done
heroku ps:type
dyno サイズを管理します。
manage dyno sizes
Called with no arguments shows the current dyno size.
Called with one argument sets the size.
Where SIZE is one of eco|basic|standard-1x|standard-2x|performance
Called with 1..n TYPE=SIZE arguments sets the quantity per type.
USAGE
$ heroku ps:type
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
Called with no arguments shows the current dyno size.
Called with one argument sets the size.
Where SIZE is one of eco|basic|standard-1x|standard-2x|performance
Called with 1..n TYPE=SIZE arguments sets the quantity per type.
heroku ps:wait
リリースの後にすべての dyno が最新バージョンを実行するまで待ちます。
wait for all dynos to be running latest version after a release
USAGE
$ heroku ps:wait
OPTIONS
-R, --with-run whether to wait for one-off run dynos
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-t, --type=type wait for one specific dyno type
-w, --wait-interval=wait-interval [default: 10] how frequently to poll in seconds (to avoid hitting Heroku API rate
limits)
コードを参照: @heroku-cli/plugin-ps
heroku psql [DATABASE]
データベースへの psql シェルを開きます。
open a psql shell to the database
USAGE
$ heroku psql [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --command=command SQL command to run
-f, --file=file SQL file to run
-r, --remote=remote git remote of app to use
--credential=credential credential to use
heroku redis [DATABASE]
Redis に関する情報を取得します。
gets information about redis
USAGE
$ heroku redis [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json format output as JSON
heroku redis:cli [DATABASE]
Redis プロンプトを開きます。
opens a redis prompt
USAGE
$ heroku redis:cli [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
heroku redis:credentials [DATABASE]
資格情報を表示します。
display credentials information
USAGE
$ heroku redis:credentials [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--reset reset credentials
heroku redis:info [DATABASE]
Redis に関する情報を取得します。
gets information about redis
USAGE
$ heroku redis:info [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--json format output as JSON
heroku redis:keyspace-notifications [DATABASE]
キー空間通知構成を設定します。
set the keyspace notifications configuration
Set the configuration to enable keyspace notification events:
K Keyspace events, published with __keyspace@<db>__ prefix.
E Keyevent events, published with __keyevent@<db>__ prefix.
g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
$ String commands
l List commands
s Set commands
h Hash commands
z Sorted set commands
t Stream commands
x Expired events (events generated every time a key expires)
e Evicted events (events generated when a key is evicted for maxmemory)
m Key miss events (events generated when a key that doesn't exist is accessed)
A Alias for "g$lshztxe", so that the "AKE" string means all the events except "m".
pass an empty string ('') to disable keyspace notifications
USAGE
$ heroku redis:keyspace-notifications [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --config=config (required) set keyspace notifications configuration
-r, --remote=remote git remote of app to use
DESCRIPTION
Set the configuration to enable keyspace notification events:
K Keyspace events, published with __keyspace@<db>__ prefix.
E Keyevent events, published with __keyevent@<db>__ prefix.
g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
$ String commands
l List commands
s Set commands
h Hash commands
z Sorted set commands
t Stream commands
x Expired events (events generated every time a key expires)
e Evicted events (events generated when a key is evicted for maxmemory)
m Key miss events (events generated when a key that doesn't exist is accessed)
A Alias for "g$lshztxe", so that the "AKE" string means all the events except "m".
pass an empty string ('') to disable keyspace notifications
heroku redis:maintenance [DATABASE]
メンテナンスウィンドウを管理します。
manage maintenance windows
Set or change the maintenance window for your Redis instance
USAGE
$ heroku redis:maintenance [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-f, --force start maintenance without entering application maintenance mode
-r, --remote=remote git remote of app to use
-w, --window=window set weekly UTC maintenance window
--run start maintenance
DESCRIPTION
Set or change the maintenance window for your Redis instance
heroku redis:maxmemory [DATABASE]
キーエビクションポリシーを設定します。
set the key eviction policy
Set the key eviction policy when instance reaches its storage limit. Available policies for key eviction include:
noeviction # returns errors when memory limit is reached
allkeys-lfu # removes less frequently used keys first
volatile-lfu # removes less frequently used keys first that have an expiry set
allkeys-lru # removes less recently used keys first
volatile-lru # removes less recently used keys first that have an expiry set
allkeys-random # evicts random keys
volatile-random # evicts random keys but only those that have an expiry set
volatile-ttl # only evicts keys with an expiry set and a short TTL
USAGE
$ heroku redis:maxmemory [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-p, --policy=policy (required) set policy name
-r, --remote=remote git remote of app to use
DESCRIPTION
Set the key eviction policy when instance reaches its storage limit. Available policies for key eviction include:
noeviction # returns errors when memory limit is reached
allkeys-lfu # removes less frequently used keys first
volatile-lfu # removes less frequently used keys first that have an expiry set
allkeys-lru # removes less recently used keys first
volatile-lru # removes less recently used keys first that have an expiry set
allkeys-random # evicts random keys
volatile-random # evicts random keys but only those that have an expiry set
volatile-ttl # only evicts keys with an expiry set and a short TTL
heroku redis:promote DATABASE
sets DATABASE as your REDIS_URL
sets DATABASE as your REDIS_URL
USAGE
$ heroku redis:promote DATABASE
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku redis:stats-reset [DATABASE]
RESETSTAT の対象となるすべての統計をリセットします (https://redis.io/commands/config-resetstat)。
reset all stats covered by RESETSTAT (https://redis.io/commands/config-resetstat)
USAGE
$ heroku redis:stats-reset [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
heroku redis:timeout [DATABASE]
アイドル接続を強制終了するまでに待つ秒数を設定します。
set the number of seconds to wait before killing idle connections
Sets the number of seconds to wait before killing idle connections. A value of zero means that connections will not be closed.
USAGE
$ heroku redis:timeout [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-s, --seconds=seconds set timeout value
DESCRIPTION
Sets the number of seconds to wait before killing idle connections. A value of zero means that connections will not be
closed.
heroku redis:upgrade [DATABASE]
インプレースバージョンアップグレードを実行します。
perform in-place version upgrade
USAGE
$ heroku redis:upgrade [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-c, --confirm=confirm
-r, --remote=remote git remote of app to use
-v, --version=version
heroku redis:wait [DATABASE]
Redis インスタンスが使用可能になるまで待ちます。
wait for Redis instance to be available
USAGE
$ heroku redis:wait [DATABASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--wait-interval=wait-interval how frequently to poll in seconds
heroku regions
デプロイに使用可能なリージョンを一覧表示します。
list available regions for deployment
USAGE
$ heroku regions
OPTIONS
--common show regions for common runtime
--json output in json format
--private show regions for private spaces
コードを参照: @heroku-cli/plugin-ps
heroku releases
アプリのリリースを表示します。
display the releases for an app
USAGE
$ heroku releases
OPTIONS
-a, --app=app (required) app to run command against
-n, --num=num number of releases to show
-r, --remote=remote git remote of app to use
--json output releases in json format
EXAMPLES
$ heroku releases
=== example Releases
v1 Config add FOO_BAR email@example.com 2015/11/17 17:37:41 (~ 1h ago)
v2 Config add BAR_BAZ email@example.com 2015/11/17 17:37:41 (~ 1h ago)
v3 Config add BAZ_QUX email@example.com 2015/11/17 17:37:41 (~ 1h ago)
heroku releases:info [RELEASE]
リリースに関する詳細情報を表示します。
view detailed information for a release
USAGE
$ heroku releases:info [RELEASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
-s, --shell output in shell format
--json output in json format
heroku releases:output [RELEASE]
release コマンドの出力を表示します。
View the release command output
USAGE
$ heroku releases:output [RELEASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku releases:rollback [RELEASE]
以前のリリースにロールバックします。
rollback to a previous release
If RELEASE is not specified, it will rollback one release
USAGE
$ heroku releases:rollback [RELEASE]
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
If RELEASE is not specified, it will rollback one release
heroku reviewapps:disable
レビューアプリか既存のパイプラインの設定、またはその両方を無効にします。
disable review apps and/or settings on an existing pipeline
USAGE
$ heroku reviewapps:disable
OPTIONS
-a, --app=app parent app used by review apps
-p, --pipeline=pipeline (required) name of pipeline
-r, --remote=remote git remote of app to use
--no-autodeploy disable autodeployments
--no-autodestroy disable automatically destroying review apps
--no-wait-for-ci disable wait for CI
EXAMPLE
$ heroku reviewapps:disable -p my-pipeline -a my-app --no-autodeploy
コードを参照: @heroku-cli/plugin-pipelines
heroku reviewapps:enable
レビューアプリか既存のパイプラインの設定、またはその両方を有効にします。
enable review apps and/or settings on an existing pipeline
USAGE
$ heroku reviewapps:enable
OPTIONS
-a, --app=app parent app used by review apps
-p, --pipeline=pipeline (required) name of pipeline
-r, --remote=remote git remote of app to use
--autodeploy autodeploy the review app
--autodestroy autodestroy the review app
--wait-for-ci wait for CI to pass before deploying
EXAMPLE
$ heroku reviewapps:enable -p my-pipeline -a my-app --autodeploy --autodestroy
コードを参照: @heroku-cli/plugin-pipelines
heroku run
Heroku dyno の内部で 1 回限りのプロセスを実行します。
run a one-off process inside a heroku dyno
Shows a notification if the dyno takes more than 20 seconds to start.
USAGE
$ heroku run
OPTIONS
-a, --app=app (required) parent app used by review apps
-e, --env=env environment variables to set (use ';' to split multiple vars)
-r, --remote=remote git remote of app to use
-s, --size=size dyno size
-x, --exit-code passthrough the exit code of the remote command
--no-notify disables notification when dyno is up (alternatively use HEROKU_NOTIFICATIONS=0)
--no-tty force the command to not run in a tty
--type=type process type
DESCRIPTION
Shows a notification if the dyno takes more than 20 seconds to start.
EXAMPLES
$ heroku run bash
$ heroku run -s basic -- myscript.sh -a arg1 -s arg2
コードを参照: @heroku-cli/plugin-run
heroku run:detached
分離された dyno を実行します。ここで、出力はログに送信されます。
run a detached dyno, where output is sent to your logs
USAGE
$ heroku run:detached
OPTIONS
-a, --app=app (required) app to run command against
-e, --env=env environment variables to set (use ';' to split multiple vars)
-r, --remote=remote git remote of app to use
-s, --size=size dyno size
-t, --tail continually stream logs
--type=type process type
EXAMPLE
$ heroku run:detached ls
コードを参照: @heroku-cli/plugin-run
heroku sessions
OAuth セッションを一覧表示します。
list your OAuth sessions
USAGE
$ heroku sessions
OPTIONS
-j, --json output in json format
コードを参照: @heroku-cli/plugin-oauth-v5
heroku sessions:destroy ID
ID で OAuth セッションを削除 (ログアウト) します。
delete (logout) OAuth session by ID
USAGE
$ heroku sessions:destroy ID
コードを参照: @heroku-cli/plugin-oauth-v5
heroku spaces
使用可能な領域を一覧表示します。
list available spaces
USAGE
$ heroku spaces
OPTIONS
-t, --team=team team to use
--json output in json format
heroku spaces:create
新しい領域を作成します。
create a new space
Example:
$ heroku spaces:create --space my-space --team my-team --region oregon
Creating space my-space in team my-team... done
=== my-space
ID: e7b99e37-69b3-4475-ad47-a5cc5d75fd9f
Team: my-team
Region: oregon
CIDR: 10.0.0.0/16
Data CIDR: 172.23.0.0/20
State: allocating
Created at: 2016-01-06T03:23:13Z
USAGE
$ heroku spaces:create
OPTIONS
-s, --space=space name of space to create
-t, --team=team team to use
--cidr=cidr RFC-1918 CIDR the space will use
--data-cidr=data-cidr RFC-1918 CIDR used by Heroku Data resources for the space
--region=region region name
DESCRIPTION
Example:
$ heroku spaces:create --space my-space --team my-team --region oregon
Creating space my-space in team my-team... done
=== my-space
ID: e7b99e37-69b3-4475-ad47-a5cc5d75fd9f
Team: my-team
Region: oregon
CIDR: 10.0.0.0/16
Data CIDR: 172.23.0.0/20
State: allocating
Created at: 2016-01-06T03:23:13Z
heroku spaces:destroy
領域を破棄します。
destroy a space
Example:
$ heroku spaces:destroy --space my-space
Destroying my-space... done
USAGE
$ heroku spaces:destroy
OPTIONS
-s, --space=space space to destroy
--confirm=confirm set to space name to bypass confirm prompt
DESCRIPTION
Example:
$ heroku spaces:destroy --space my-space
Destroying my-space... done
heroku spaces:info
領域に関する情報を表示します。
show info about a space
USAGE
$ heroku spaces:info
OPTIONS
-s, --space=space space to get info of
--json output in json format
heroku spaces:peering:info
ピアリング接続を開始するために必要な情報を表示します。
display the information necessary to initiate a peering connection
Example:
$ heroku spaces:peering:info example-space
=== example-space Peering Info
AWS Account ID: 012345678910
AWS Region: us-west-2
AWS VPC ID: vpc-baadf00d
AWS VPC CIDR: 10.0.0.0/16
Space CIDRs: 10.0.128.0/20, 10.0.144.0/20
Unavailable CIDRs: 10.1.0.0/16
You will use the information provied by this command to establish a peering connection request from your AWS VPC to your private space.
To start the peering process, go into your AWS console for the VPC you would like peered with your Private Space,
navigate to the VPC service, choose the "Peering Connections" option and click the "Create peering connection" button.
- The AWS Account ID and VPC ID are necessary for the AWS VPC Peering connection wizard.
- You will also need to configure your VPC route table to route the Dyno CIDRs through the peering connection.
Once you've established the peering connection request, you can use the spaces:peerings:accept command to accept and
configure the peering connection for the space.
USAGE
$ heroku spaces:peering:info
OPTIONS
-s, --space=space space to get peering info from
--json output in json format
DESCRIPTION
Example:
$ heroku spaces:peering:info example-space
=== example-space Peering Info
AWS Account ID: 012345678910
AWS Region: us-west-2
AWS VPC ID: vpc-baadf00d
AWS VPC CIDR: 10.0.0.0/16
Space CIDRs: 10.0.128.0/20, 10.0.144.0/20
Unavailable CIDRs: 10.1.0.0/16
You will use the information provied by this command to establish a peering connection request from your AWS VPC to
your private space.
To start the peering process, go into your AWS console for the VPC you would like peered with your Private Space,
navigate to the VPC service, choose the "Peering Connections" option and click the "Create peering connection" button.
- The AWS Account ID and VPC ID are necessary for the AWS VPC Peering connection wizard.
- You will also need to configure your VPC route table to route the Dyno CIDRs through the peering connection.
Once you've established the peering connection request, you can use the spaces:peerings:accept command to accept and
configure the peering connection for the space.
heroku spaces:peerings
領域のピアリング接続を一覧表示します。
list peering connections for a space
USAGE
$ heroku spaces:peerings
OPTIONS
-s, --space=space space to get peer list from
--json output in json format
heroku spaces:peerings:accept
Private Space に対する保留中のピアリングリクエストを受け付けます。
accepts a pending peering request for a private space
Example:
$ heroku spaces:peerings:accept pcx-4bd27022 --space example-space
Accepting and configuring peering connection pcx-4bd27022
USAGE
$ heroku spaces:peerings:accept
OPTIONS
-p, --pcxid=pcxid PCX ID of a pending peering
-s, --space=space space to get peering info from
DESCRIPTION
Example:
$ heroku spaces:peerings:accept pcx-4bd27022 --space example-space
Accepting and configuring peering connection pcx-4bd27022
heroku spaces:peerings:destroy
Private Space 内のアクティブなピアリング接続を破棄します。
destroys an active peering connection in a private space
Example:
$ heroku spaces:peerings:destroy pcx-4bd27022 --confirm pcx-4bd27022 --space example-space
Tearing down peering connection pcx-4bd27022
USAGE
$ heroku spaces:peerings:destroy
OPTIONS
-p, --pcxid=pcxid PCX ID of a pending peering
-s, --space=space space to get peering info from
--confirm=confirm set to PCX ID to bypass confirm prompt
DESCRIPTION
Example:
$ heroku spaces:peerings:destroy pcx-4bd27022 --confirm pcx-4bd27022 --space example-space
Tearing down peering connection pcx-4bd27022
heroku spaces:ps
領域の dyno を一覧表示します。
list dynos for a space
USAGE
$ heroku spaces:ps
OPTIONS
-s, --space=space space to get dynos of
--json output in json format
heroku spaces:rename
領域の名前を変更します。
renames a space
Example:
$ heroku spaces:rename --from old-space-name --to new-space-name
Renaming space old-space-name to new-space-name... done
USAGE
$ heroku spaces:rename
OPTIONS
--from=from (required) current name of space
--to=to (required) desired name of space
DESCRIPTION
Example:
$ heroku spaces:rename --from old-space-name --to new-space-name
Renaming space old-space-name to new-space-name... done
heroku spaces:topology
領域のトポロジーを表示します。
show space topology
USAGE
$ heroku spaces:topology
OPTIONS
-s, --space=space space to get topology of
--json output in json format
heroku spaces:transfer
領域を別のチームに移動します。
transfer a space to another team
Example:
$ heroku spaces:transfer --space=space-name --team=team-name
Transferring space-name to team-name... done
USAGE
$ heroku spaces:transfer
OPTIONS
--space=space (required) name of space
--team=team (required) desired owner of space
DESCRIPTION
Example:
$ heroku spaces:transfer --space=space-name --team=team-name
Transferring space-name to team-name... done
heroku spaces:vpn:config
VPN の設定情報を表示します。
display the configuration information for VPN
Example:
$ heroku spaces:vpn:config --space my-space vpn-connection-name
=== vpn-connection-name VPN Tunnels
VPN Tunnel Customer Gateway VPN Gateway Pre-shared Key Routable Subnets IKE Version
────────── ──────────────── ────────────── ────────────── ──────────────── ───────────
Tunnel 1 104.196.121.200 35.171.237.136 abcdef12345 10.0.0.0/16 1
Tunnel 2 104.196.121.200 52.44.7.216 fedcba54321 10.0.0.0/16 1
You will use the information provided by this command to establish a Private Space VPN Connection.
- You must configure your VPN Gateway to use both Tunnels provided by Heroku
- The VPN Gateway values are the IP addresses of the Private Space Tunnels
- The Customer Gateway value is the Public IP of your VPN Gateway
- The VPN Gateway must use the IKE Version shown and the Pre-shared Keys as the authentication method
USAGE
$ heroku spaces:vpn:config
OPTIONS
-n, --name=name name or id of the VPN connection to retrieve config from
-s, --space=space space the VPN connection belongs to
--json output in json format
DESCRIPTION
Example:
$ heroku spaces:vpn:config --space my-space vpn-connection-name
=== vpn-connection-name VPN Tunnels
VPN Tunnel Customer Gateway VPN Gateway Pre-shared Key Routable Subnets IKE Version
────────── ──────────────── ────────────── ────────────── ──────────────── ───────────
Tunnel 1 104.196.121.200 35.171.237.136 abcdef12345 10.0.0.0/16 1
Tunnel 2 104.196.121.200 52.44.7.216 fedcba54321 10.0.0.0/16 1
You will use the information provided by this command to establish a Private Space VPN Connection.
- You must configure your VPN Gateway to use both Tunnels provided by Heroku
- The VPN Gateway values are the IP addresses of the Private Space Tunnels
- The Customer Gateway value is the Public IP of your VPN Gateway
- The VPN Gateway must use the IKE Version shown and the Pre-shared Keys as the authentication method
heroku spaces:vpn:connect
VPN を作成します。
create VPN
Private Spaces can be connected to another private network via an IPSec VPN connection allowing dynos to connect to hosts on your private networks and vice versa.
The connection is established over the public Internet but all traffic is encrypted using IPSec.
USAGE
$ heroku spaces:vpn:connect
OPTIONS
-c, --cidrs=cidrs a list of routable CIDRs separated by commas
-i, --ip=ip public IP of customer gateway
-n, --name=name VPN name
-s, --space=space space name
DESCRIPTION
Private Spaces can be connected to another private network via an IPSec VPN connection allowing dynos to connect to
hosts on your private networks and vice versa.
The connection is established over the public Internet but all traffic is encrypted using IPSec.
EXAMPLES
$ heroku spaces:vpn:connect --name office --ip 35.161.69.30 --cidrs 172.16.0.0/16,10.0.0.0/24 --space my-space
Creating VPN Connection in space my-space... done
▸ Use spaces:vpn:wait to track allocation.
heroku spaces:vpn:connections
領域の VPN 接続を一覧表示します。
list the VPN Connections for a space
Example:
$ heroku spaces:vpn:connections --space my-space
=== my-space VPN Connections
Name Status Tunnels
────── ────── ───────
office active UP/UP
USAGE
$ heroku spaces:vpn:connections
OPTIONS
-s, --space=space space to get VPN connections from
--json output in json format
DESCRIPTION
Example:
$ heroku spaces:vpn:connections --space my-space
=== my-space VPN Connections
Name Status Tunnels
────── ────── ───────
office active UP/UP
heroku spaces:vpn:destroy
Private Space 内の VPN を破棄します。
destroys VPN in a private space
Example:
$ heroku spaces:vpn:destroy --space example-space vpn-connection-name --confirm vpn-connection-name
Tearing down VPN Connection vpn-connection-name in space example-space
USAGE
$ heroku spaces:vpn:destroy
OPTIONS
-n, --name=name name or id of the VPN connection to retrieve config from
-s, --space=space space to get peering info from
--confirm=confirm set to VPN connection name to bypass confirm prompt
DESCRIPTION
Example:
$ heroku spaces:vpn:destroy --space example-space vpn-connection-name --confirm vpn-connection-name
Tearing down VPN Connection vpn-connection-name in space example-space
heroku spaces:vpn:info
VPN の情報を表示します。
display the information for VPN
Example:
$ heroku spaces:vpn:info --space my-space vpn-connection-name
=== vpn-connection-name VPN Tunnel Info
Name: vpn-connection-name
ID: 123456789012
Public IP: 35.161.69.30
Routable CIDRs: 172.16.0.0/16
Status: failed
Status Message: supplied CIDR block already in use
=== my-space Tunnel Info
VPN Tunnel IP Address Status Status Last Changed Details
────────── ───────────── ────── ──────────────────── ──────────────
Tunnel 1 52.44.146.197 UP 2016-10-25T22:09:05Z status message
Tunnel 2 52.44.146.197 UP 2016-10-25T22:09:05Z status message
USAGE
$ heroku spaces:vpn:info
OPTIONS
-n, --name=name name or id of the VPN connection to get info from
-s, --space=space space the vpn connection belongs to
--json output in json format
DESCRIPTION
Example:
$ heroku spaces:vpn:info --space my-space vpn-connection-name
=== vpn-connection-name VPN Tunnel Info
Name: vpn-connection-name
ID: 123456789012
Public IP: 35.161.69.30
Routable CIDRs: 172.16.0.0/16
Status: failed
Status Message: supplied CIDR block already in use
=== my-space Tunnel Info
VPN Tunnel IP Address Status Status Last Changed Details
────────── ───────────── ────── ──────────────────── ──────────────
Tunnel 1 52.44.146.197 UP 2016-10-25T22:09:05Z status message
Tunnel 2 52.44.146.197 UP 2016-10-25T22:09:05Z status message
heroku spaces:vpn:update
VPN を更新します。
update VPN
Private Spaces can be connected to another private network via an IPSec VPN connection allowing dynos to connect to hosts on your private networks and vice versa.
The connection is established over the public Internet but all traffic is encrypted using IPSec.
USAGE
$ heroku spaces:vpn:update
OPTIONS
-c, --cidrs=cidrs a list of routable CIDRs separated by commas
-n, --name=name VPN name
-s, --space=space space name
DESCRIPTION
Private Spaces can be connected to another private network via an IPSec VPN connection allowing dynos to connect to
hosts on your private networks and vice versa.
The connection is established over the public Internet but all traffic is encrypted using IPSec.
EXAMPLES
$ heroku spaces:vpn:update --name office --cidrs 172.16.0.0/16,10.0.0.0/24 --space my-space
Updating VPN Connection in space my-space... done
heroku spaces:vpn:wait
VPN 接続が作成されるまで待ちます。
wait for VPN Connection to be created
USAGE
$ heroku spaces:vpn:wait
OPTIONS
-i, --interval=interval seconds to wait between poll intervals
-n, --name=name name or id of the vpn connection to wait for
-s, --space=space space the vpn connection belongs to
-t, --timeout=timeout maximum number of seconds to wait
--json output in json format
heroku spaces:wait
領域が作成されるまで待ちます。
wait for a space to be created
USAGE
$ heroku spaces:wait
OPTIONS
-i, --interval=interval seconds to wait between poll intervals
-s, --space=space space to get info of
-t, --timeout=timeout maximum number of seconds to wait
--json output in json format
heroku status
Heroku プラットフォームの現在のステータスを表示します。
display current status of the Heroku platform
USAGE
$ heroku status
OPTIONS
--json output in json format
コードを参照: @heroku-cli/plugin-status
heroku teams
自分がメンバーになっているチームを一覧表示します。
list the teams that you are a member of
Use heroku members:* to manage team members.
USAGE
$ heroku teams
OPTIONS
--json output in json format
DESCRIPTION
Use heroku members:* to manage team members.
heroku trusted-ips
領域の信頼済み IP 範囲を一覧表示します。
list trusted IP ranges for a space
Trusted IP ranges are only available on Private Spaces.
The space name is a required parameter. Newly created spaces will have 0.0.0.0/0 set by default
allowing all traffic to applications in the space. More than one CIDR block can be provided at
a time to the commands listed below. For example 1.2.3.4/20 and 5.6.7.8/20 can be added with:
USAGE
$ heroku trusted-ips
OPTIONS
-s, --space=space space to get inbound rules from
--json output in json format
DESCRIPTION
Trusted IP ranges are only available on Private Spaces.
The space name is a required parameter. Newly created spaces will have 0.0.0.0/0 set by default
allowing all traffic to applications in the space. More than one CIDR block can be provided at
a time to the commands listed below. For example 1.2.3.4/20 and 5.6.7.8/20 can be added with:
heroku trusted-ips:add SOURCE
信頼済み IP 範囲の一覧に 1 つの範囲を追加します。
Add one range to the list of trusted IP ranges
Uses CIDR notation.
Example:
$ heroku trusted-ips:add --space my-space 192.168.2.0/24
Added 192.168.0.1/24 to trusted IP ranges on my-space
USAGE
$ heroku trusted-ips:add SOURCE
OPTIONS
-s, --space=space space to add rule to
--confirm=confirm set to space name to bypass confirm prompt
DESCRIPTION
Uses CIDR notation.
Example:
$ heroku trusted-ips:add --space my-space 192.168.2.0/24
Added 192.168.0.1/24 to trusted IP ranges on my-space
heroku trusted-ips:remove SOURCE
信頼済み IP 範囲の一覧から範囲を削除します。
Remove a range from the list of trusted IP ranges
Uses CIDR notation.
Example:
$ heroku trusted-ips:remove --space my-space 192.168.2.0/24
Removed 192.168.2.0/24 from trusted IP ranges on my-space
USAGE
$ heroku trusted-ips:remove SOURCE
OPTIONS
--confirm=confirm set to space name to bypass confirm prompt
--space=space (required) space to remove rule from
DESCRIPTION
Uses CIDR notation.
Example:
$ heroku trusted-ips:remove --space my-space 192.168.2.0/24
Removed 192.168.2.0/24 from trusted IP ranges on my-space
heroku unlock
任意のチームメンバーが参加できるように、アプリのロックを解除します。
unlock an app so any team member can join
USAGE
$ heroku unlock
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku update [CHANNEL]
Heroku CLI を更新します。
update the <%= config.bin %> CLI
USAGE
$ heroku update [CHANNEL]
OPTIONS
--from-local interactively choose an already installed version
コードを参照: @oclif/plugin-update
heroku webhooks
アプリの Webhook を一覧表示します。
list webhooks on an app
USAGE
$ heroku webhooks
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku webhooks
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:add
アプリに Webhook を追加します。
add a webhook to an app
USAGE
$ heroku webhooks:add
OPTIONS
-a, --app=app app to run command against
-i, --include=include (required) comma delimited event types your server will receive
-l, --level=level (required) notify does not retry, sync will retry until successful or timeout
-r, --remote=remote git remote of app to use
-s, --secret=secret value to sign delivery with in Heroku-Webhook-Hmac-SHA256 header
-t, --authorization=authorization authoriation header to send with webhooks
-u, --url=url (required) URL for receiver
EXAMPLE
$ heroku webhooks:add -i api:dyno -l notify -u https://example.com/hooks
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:deliveries
アプリの Webhook 配信を一覧表示します。
list webhook deliveries on an app
USAGE
$ heroku webhooks:deliveries
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
-s, --status=status filter deliveries by status
EXAMPLE
$ heroku webhooks:deliveries
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:deliveries:info ID
アプリの Webhook イベントに関する情報。
info for a webhook event on an app
USAGE
$ heroku webhooks:deliveries:info ID
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku webhooks:deliveries:info 99999999-9999-9999-9999-999999999999
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:events
アプリの Webhook イベントを一覧表示します。
list webhook events on an app
USAGE
$ heroku webhooks:events
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku webhooks:events
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:events:info ID
アプリの Webhook イベントに関する情報。
info for a webhook event on an app
USAGE
$ heroku webhooks:events:info ID
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku webhooks:events:info 99999999-9999-9999-9999-999999999999
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:info ID
アプリの Webhook に関する情報。
info for a webhook on an app
USAGE
$ heroku webhooks:info ID
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku webhooks:info 99999999-9999-9999-9999-999999999999
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:remove ID
アプリから Webhook を削除します。
removes a webhook from an app
USAGE
$ heroku webhooks:remove ID
ARGUMENTS
ID id of webhook to remove
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
EXAMPLE
$ heroku webhooks:remove 99999999-9999-9999-9999-999999999999
コードを参照: @heroku-cli/plugin-webhooks
heroku webhooks:update ID
アプリ内の Webhook を更新します。
updates a webhook in an app
USAGE
$ heroku webhooks:update ID
OPTIONS
-a, --app=app app to run command against
-i, --include=include (required) comma delimited event types your server will receive
-l, --level=level (required) notify does not retry, sync will retry until successful or timeout
-r, --remote=remote git remote of app to use
-s, --secret=secret value to sign delivery with in Heroku-Webhook-Hmac-SHA256 header
-t, --authorization=authorization authoriation header to send with webhooks
-u, --url=url (required) URL for receiver
EXAMPLE
$ heroku webhooks:update 99999999-9999-9999-9999-999999999999 -i dyno -l notify -s
09928c40bf1b191b645174a19f7053d16a180da37332e719ef0998f4c0a2 -u https://example.com/hooks
コードを参照: @heroku-cli/plugin-webhooks
heroku which COMMAND
コマンドがどのプラグインに含まれているかを表示します。
show which plugin a command is in
USAGE
$ heroku which COMMAND
コードを参照: @oclif/plugin-which