Add rake job for restarting dyno when condition met

[PikachuEXE]

Running an additional dyno seems expensive Unless you are talking about running it in another Heroku app (In that case please write that to readme)

[likethesky]

I have essentially the same question that @PikachuEXE has here: Does this run in a separate dyno from the application dyno? I couldn't tell from the README. The impression I get is that it doesn't require a separate dyno ( heroku ps:scale whacamole=1 --app YOUR_APP_NAME and by reading https://devcenter.heroku.com/articles/dyno-types -- though I'm unclear on what whacamole=1 means vs web=1 or worker=1 ) in any case, it'd be great if it doesn't require an additional dyno.

If it does require an additional dyno, then some kind of self-running check that monitors (the app checks itself) every 5 minutes or so, via a Nailgun process or something would be a nice feature. I think the README could be more explicit one way or another, whichever is the case. Thanks for your work on this!

[arches]

it's intended to run in another dyno but you could probably take the guts of it and run it anywhere. whacamole=1 and web=1 both refer to your Procfile. The Procfile is what sets up the different dyno types. So whacamole=1 spins up a single dyno and runs the whacamole line from your Procfile.

When I wrote this I was at a company where we cared more about our performance than the $30/mo for the dyno. I agree it's not the most elegant of solutions for all use cases.