Alternative method of running rake work_jobs

[zlogic]

A fix for the forked bundle exec rake work_jobs process crashing on Heroku (issue #411).
This includes a basic worker (just run bundle exec rake work_jobs and restart on failure) and a "full worker" which does most of the daily tasks without a scheduler. It's possible to choose which ones to use in the dashboard and having up to 1 worker is free of charge.

[swanson]

Thanks - I need to look into this more in-depth. I missed this blog post: https://blog.heroku.com/archives/2015/5/7/heroku-free-dynos that introduces the free worker dyno, which sounds awesome.

[Koronen]

I like the gist of this fix. Thank you! 👍

Here are some of my thoughts:

• Do we need two process definitions?

  The docs currently instruct users to configure cron jobs (Heroku Scheduler or similar) for scheduling fetching of new stories, and for cleaning out old stories. Maybe it's sufficient to keep just the delayed_worker process definition?

• Do we need the loop?

  I think at least Heroku restarts crashed processes automatically.

  Dynos are also restarted if the processes running in the dyno exit.

  https://devcenter.heroku.com/articles/dynos#restarting

• How can we provide a smooth upgrade process for everyone using this app?

  There's probably some documentation that could be updated to reflect this change in behavior.

[gabrielpoca]

Closing this PR for lack of activity.