Hi there, I found in this thread that the

dius/pact-broker

image is going to be deprecated. Is that still the case? There are some benefits that I would benefit from. Thanks 🙂

If you want to run the container as a standalone instance, then the dius/pact-broker image which uses Phusion Passenger may serve you better, as Passenger will restart any crashed processes.

Correct

Many thanks! It'd be even clearer now 🎩

My pleasure, out of interest, what would be the feature(s) that you are looking for? Would there be appetite to participate in maintenance of the image at all, feel free to comment in the issue as well where it will have longer visibility.

These ones caught my eye when I was reading this entry

If you want to run the container as a standalone instance, then the dius/pact-broker image which uses Phusion Passenger may serve you better, as Passenger will restart any crashed processes.

Management tools
Puma provides a control server which allows you to stop or restart Puma and to query its status. However, it appears to be rather minimalistic (it only displays the size of the backlog and the number of running requests), and doesn't appear to be a first-class citizen. For example, the control server does not work in clustered mode. <-- That issue is now marked as fixed and supported since 2.3.0.

Phusion Passenger, both the open source and Enterprise variants, have management tools that provide much more insight. Phusion Passenger allows you to stop, restart and to query its status through command line tools like passenger-status, passenger-config, passenger-memory-stats. These tools are regular command line tools, and their access can be controlled through sudo, which is a very Unix way of doing things. These tools display everything Puma's status server displays, plus the exact requests that are currently running, how long they've been running, the application's CPU and memory usage, etc.

In our experience, the Puma one is much simpler to use