Enable configuring which process type (web, worker, etc.) to run instead of defaulting to "web"

[motin]

Currently, dokku is hard-coded to start the "web" process on deploy.

Instead, this should be configurable so that any process type (web, worker, etc.) defined in the Procfile can be run. A config-directive PROCESS_TYPE that defaults to web if not set to determine this, maybe?

This would make it possible to start worker processes as different docker containers / deployments so that we don't have to resort to using dokku-shoreman or dokku-supervisord, who both require manual efforts to avoid port collisions.

This brings dokku closer to how Heroku and other PaaS handle process types - each process is started in it's own container/dyno.

[josegonzalez]

A procfile isn't strictly necessary with dokku though. Is this related to #733 ?

[motin]

A procfile isn't strictly necessary with dokku though.

This enhancement would not change that fact in any way. :)

Is this related to #733 ?

Not really. It could be, if we'd call the environment variable DYNO instead of PROCESS_TYPE, but I find PROCESS_TYPE more descriptive.

[josegonzalez]

A pr to add this functionality would be great. I can't think of a good way myself to implement it.

[josegonzalez]

As of #1118, we now have container-level scaling, which allows you to run whichever process in the Procfile you see fit :)