Heroku

[andrewyakonyuk]

Since the (non) official heroku buildpack is very experimental, I use the fork of this buildpack where fixed a few critical errors.

The source code contain multiple project.json files, so needed to use .deployment file. Something like that:

[config] project = Vault.Web

[andrewyakonyuk]

Heroku tips and hacks

Some interesting points:

logs

heroku logs -t - watch the logs in real time

This is the quickest and simplest way to see your live logs. You can also filter the logs by source (e.g. -s heroku) or process (e.g. -p web).

TIP Press control-C to exit logs when you use the -t flag.

Heroku Scheduler

Heroku Scheduler - designed for quick tasks that need to be run at intervals (every 10 minutes, every hour or every day). This addon is free but does contribute to your dyno hours.

[andrewyakonyuk]

Running ASP.NET Core in Heroku

Currently there are 2 options to deploy an app into Heroku's containers (also called dynos):

• Using Dockerfile, which is a pretty new in Heroku. There are some naming issues due to copyright, thus it's called Container Registry and Runtime
• Using buildpack, which is similar to Kudu in Azure. The buildpack is responsible to setup a correct runtime for the application in container, build the application and provision it into container Each option has its pros and cons. After trying both, I decided to stick with buildpack.