Node RailwayJS app – Deploying to Heroku – ENOENT, open ‘/app/log/production.log

I’m currently working on a project involving a node.js app, using RailwayJS, deploying to Heroku.

After doing my

git push Heroku

Everything seemed ok, however, the app was not running.

I ran Heroku logs and was shown:

app[web.1]: listening on port 32168 within production environment
app[web.1]:
app[web.1]: events.js:48
app[web.1]: throw arguments[1]; // Unhandled ‘error’ event
app[web.1]: ^
app[web.1]: Error: ENOENT, open ‘/app/log/production.log’
heroku[web.1]: Process exited with status 1
heroku[web.1]: State changed from starting to crashed

This didn’t tell me much, apart from

ENOENT, open ‘/app/log/production.log’

This means that the file specified can’t be found- or opened in our case.

To resolve this, after suggestion from RailwayJS’ extremely helpful creator, Anatoliy Chakkaev, I simply disabled quiet logging, by changing my environment config to:

app.disable(‘quiet’);