Heroku notes

Two main concepts:
	* dyno
		* smart container that know how to deploy and run specific technologies such as a node server or Java JVM
		* they are like small lightweight server containers
		* can be scaled up and down usin the Heroku tools
	* add-ons
		* allow you to add other tools and platforms to your dynos
		* examples:
			* databases (Postgres, Mysql)
			* logging aggregators
			* other tools

Heroku Buildpacks
	* the dynos are configured and set up using Heroku Buildpacks
	* buildpacks are set of scripts and files that act kind like a giant application compiler and build tool
	* they take all of your raw application files and prepare them to be usable as a final application product

Most used commands:
	heroku login
		authenticates you to heroku
	heroku create
		creates an empty container space
	heroku apps
		list all apps on your account
	heroku logs -a <app>
		logs output for your app
	heroku logs -a <app> -- tail
		logs output for your app realtime
	heroku config
		configure environment

Procfile
	specifies the command that should run the web dyno
	heroku use it to determine what web server to deploy our app
	must be placed at the root at the project
	<process type>: <command>
		process types:
			web - web server command
			worker - background jobs