Essential Heroku Commands for Java (Spring Boot) developers

This blog post captures the command used to create and configure java apps or spring boot apps deployed to Heroku Cloud. I use these commands in CI/CD deployment steps for continuous delivery and also to access the application's information from my local development machine.

These commands are tested with Heroku Client version: heroku/7.0.33 darwin-x64 node-v10.0.0

View help

heroku help

Login/Logout to heroku With email and password

heroku auth:login
heroku auth:whoami
heroku auth:logout

Login/Logout to heroku With token

# set HEROKU_API_KEY environment variable to login
export HEROKU_API_KEY=<<API Key from https://dashboard.heroku.com/account>>
heroku auth:whoami

# unset HEROKU_API_KEY environment variable to logout
unset HEROKU_API_KEY

# clear the history to clear the API Key
history -cw && cat /dev/null > ~/.bash_history

Show available regions for deployment

heroku regions

Create an application

heroku apps:create --app app-name --region eu --no-remote

# for deployment script
export APP_NAME=app-name
isAppAlreadyCreated=$(heroku apps | grep -c $APP_NAME)
if [ $isAppAlreadyCreated -eq 0 ]
then
    heroku apps:create --app $APP_NAME --region eu --no-remote
else
    echo "An existing application found"
fi

List applications

heroku apps

Display application's information

heroku apps:info --app app-name

Config variables (environment variable)

# list existing variables
heroku config --app app-name

# set a new variable
heroku config:set ENVIRONMENT_VARIABLE1="Some Value1" --app app-name

# unset an existing variable
heroku config:unset ENVIRONMENT_VARIABLE1 --app app-name

Deploy a spring boot jar file with system properties

heroku plugins:install heroku-cli-deploy

echo 'web: java -Dspring.profiles.active=live -Dserver.port=$PORT $JAVA_OPTS -jar target/my-app.jar' > Procfile

heroku deploy:jar --jar target/my-app.jar --app app-name --jdk 8

Open the application in browser

heroku apps:open --app app-name

Add custom domain

heroku domains:add test.example.com --app app-name

# for deployment script
export APP_NAME=app-name
isDomainAlreadyApplied=$(heroku domains --app $APP_NAME | grep -c "test.harishkannarao.com")
if [ $isDomainAlreadyApplied -eq 0 ]
then
    heroku domains:add test.harishkannarao.com --app $APP_NAME
else
    echo "Domain already applied"
fi

Upgrade to paid hobby plan and enable heroku SSL

heroku ps:resize web=hobby --app app-name

heroku certs:auto:enable --app app-name

Downgrade to free plan and disable SSL

heroku ps:resize web=free --app app-name

Check the application logs

heroku logs --app app-name --tail

List current scalability of an application

heroku ps:scale --app app-name

Stop or scale down an application

heroku ps:scale web=0 --app app-name

Start or scale up an application

heroku ps:scale web=1 --app app-name

Restart an application

heroku ps:restart --app app-name

Put and resume an application to/from maintenance mode

heroku maintenance:on --app app-name

heroku maintenance:off --app app-name

Delete an application

heroku apps:destroy --app app-name --confirm app-name

Comments

Post a Comment

Popular posts from this blog

JSON with curl and jq

This blog post captures some quick commands to deal with JSON from servers (Http APIs) using curl and jq command line tools About Jq: https://stedolan.github.io/jq/ Install jq: Mac: brew install jq Ubuntu or Debian: sudo apt-get install jq Sample JSON content: Assume the following JSON content will be returned from  URL http://api.example.com/some-json-content {     "user_name": "User 123",     "some_other_field": {         "sub_field": "sub_value"     },     "array_field": [         {             "field1": "value1",             "field2": "value2"         },         {             "field1": "value3",             "field2": "value4"         }     ] } URL http://api.example.com/some-json-array-content [     {         "field1": "array value 1",         "field2&
Read more

Import self signed in Linux for Chrome / Chromium headless testing

Chrome / Chromium browser offers headless mode, which is quite useful to run tests via Selenium WebDriver in CI servers. However under some circumstance your test will hit a server with self signed certificate or invalid certificate or expired certificate. This may happen for developers trying to write tests against a server started on localhost with self signed certificates or testers trying to write tests against non-production servers with expired certificates (invalid certificates). Chrome / Chromium browser ignores the SSL errors when running in non-headless mode. However in CI servers, then it should be running in headless mode and currently we cannot ignore the SSL errors for tests accessing non-localhost websites. This blogs explains the steps for import a certificate into Linux's trust store, which will make the Chrome / Chromium browser to trust the self signed certificate.  Please do not apply these steps in production servers as it will make server vulnerable to
Read more

Colima - Drop In replacement for Docker Desktop for Mac and Linux

Colima ( Co ntainer on Li nux Ma chines) is an open source alternative and drop in replacement for Docker Desktop on Mac and Linux. https://github.com/abiosoft/colima It is simple to setup and run containers without the need for sudo or root access. Images can be pulled form both Docker hub ( https://hub.docker.com ) or Amazon's public registry ( https://gallery.ecr.aws ) Amazon's registry is more permissive or friendly with pull rates for both clients and non-clients of AWS. This article show the setup and basics of running containers on mac. Installation command for Linux can vary based on the distribution type, hence please refer to official documentation for up-to-date steps at  https://github.com/abiosoft/colima/blob/main/docs/INSTALL.md Installation on mac: brew install docker  brew install docker-buildx brew install docker-compose brew install jq brew install colima Setup docker compose as docker plugin mkdir -p $HOME/.docker/cli-plugins ln -sfn $(which docker-compose) $
Read more