What's your rating of Heroku

Heroku is cool, but what exactly are the advantages?

An application must first be transferred to Heroku in order for it to run in any way. Git version control is Heroku's primary deployment tool, and it should please most developers. In theory, deployment would also be possible with GitHub and Dropbox, but with Git you are on the safe side. This is a good thing, because it enables a clean development workflow that is understandable for the developer.

Here is a quick example of how a simple website is transferred to Heroku.

First of all, a Git repository has to be initialized locally by the corresponding project.

Terminal:

cd project
$ git init
$ git add.
$ git commit -m "The website is going to be cool!"

Next we create under https://dashboard.heroku.com a new dyno called “heypickstest”. Now we have to log in to Heroku via the terminal and then tell Heroku which project we would like to deploy.

Terminal:

$ heroku login
$ cd project
$ git push heroku master

In principle that was it! This is followed by minor adjustments, such as adapting the start scripts so that Heroku knows which script to execute first.

With Node.js, for example, in the package.json define the start script as follows if we want to run the app.js first:

Editor:

"scripts": {
"start": "node app.js"
}

Without this line, Heroku will not know exactly which file to execute first and will therefore issue an error.