Procfile: Drop the Worker process type, and use Heroku Scheduler instead #2294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We use the Heroku Scheduler to run the "jobs:workoff" Rake task (from the Delayed Job gem).
https://devcenter.heroku.com/articles/procfile#other-process-types mentions that
And this is a
worker:
named process type.This whole "worker" dyno can be stopped. The cost for this dyno is about 25 USD per month.
We have it double-configured, both correctly in Scheduler AND wrongly with this line in the Procfile.