1. heroku CLI install and login on terminal
  2. (Command) git clone: sample application provided by heroku
  3. (Command) heroku create: creating app using above example on internet and git repository. Internet and git path is printed out on terminal
  4. (Command) git push heroku master: 
    deploy command
  5. (Command) heroku ps:scale web=1
    Confirm app is running using 1 dyno
  6. (Command) heroku logs --tail
    View command to see streaming logs on real time
  7. Check the file name Procfile in example folder
    Inside the file, there is some text to declare — web: node index.js
    it means (specially keyword web:) this process type will be attached to the HTTP routing stack of Heroku, and receive web traffic when deployed.
  8. (Command) heroku ps:scale web=0
    It means dyno makes zero so application is shutdown. Dyno is Linux container related to server storage — maybe. If web application becomes more heavy, dynos is more needed.
  9. (Command) npm install
  10. (Command) heroku local web
    These commands is preparing to run application on local. When type heroku ps:scale web=1, heroku run Procfile. And when type heroku local web, heroku run Procfile on local.
  11. pakage.json and git changes
    (Command) npm install --save --save-exact [new package name]
    index.js file modify
    git add, commit, and push then complete to reflection local file change on git.
  12. (Command) heroku run node
    Running node command on dyno. After that, on dyno, I can declare and use variables, function and others.
  13. (Command) heroku run bash
    Similar command with heroku run node
  14. config vars
    A kind of configuration commands like config, config:set, config:get and config:unset.
Like what you read? Give Minoo Joo a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.