#procfile

I like running most things on Heroku since I don’t have to run an entire environment and they have add-ons for many things.

I got SuperScript up and running and went ahead and created Deploy to Heroku buttons for an Express and Slack client.

One of the things I learned is that Heroku has a bot process type you can specify in the Procfile, and if you don’t specify it, it will kill your script for failing to connect to a web port.

Prior to v1.22 there was a disparity between Resque’s signal handling and Heroku’s process management that caused orphaned and incomplete jobs between worker restarts. Starting with v1.22 Resque’s handling of TERM and QUIT signals is in accordance with UNIX standards and maintains compatibility with the Heroku runtime that previous versions lacked.

Make sure to update your worker process definition in Procfile:

worker: env TERM_CHILD=1 RESQUE_TERM_TIMEOUT=10 bundle exec rake resque:work QUEUE=alerts

Running through Heroku's tutorial for Django, and one step tripped me up.

When declaring the Procfile, the instructions say:

web: python hellodjango/manage.py run_gunicorn -b "0.0.0.0:$PORT" -w 3

The problem is when you run foreman, you might get an error saying:

Error: '5000"' is not a valid port number.

The fix to the problem seems that -b command option 0.0.0.0:$PORT should be declared without the quotes. This seems to be a problem with newer versions of foreman.