In order to get the status of the Puma workers, we can run /engineyard/bin/app_<app_name> status. This produces a status result and a bunch of unformatted json with details.
While that output is fine for system utilities, it's not so human friendly. Let's help ourselves by extending the control script with something like
In order to get the status of the Puma workers, we can run
/engineyard/bin/app_<app_name> status
. This produces a status result and a bunch of unformatted json with details.While that output is fine for system utilities, it's not so human friendly. Let's help ourselves by extending the control script with something like
or by passing a second argument to the script (like
--pretty
) and parse it as theey-puma_legacy
recipe does for port settingsUntil then, the following command show a pretty print of the status of the Puma workers:
/engineyard/bin/app_<app_name> status | tail -1 | json_pp
.