That's possible, but non-trivial. One reason the supervisor can only supervise multiple instances of *the same app* now is that limitation is inherent in the node cluster module API. There is precendent for "multi-app" supervision for node (forever, pm2), but that's not within scope here. For 1, its a lot more work ;-). It involves directly using child_process to create children, each of which would be a cluster master somewhat like what slr is now.

More importantly, we have a multi-app supervisor... the strongops console. It allows seeing all the apps that are running, and interacting with them there, and can be used to do the kinds of things that a multi-app supervisor would do from the command line, so adding that feature to strong-supervisor  wasn't so compelling. Not to close the door on the idea, but its not part of MVP.

Btw, supervisor does not, itself, use the (optional) pid file. I added support because they are commonly used by init scripts (for example), so /etc/init.d/lovely-app stop would do a `kill -TERM $(cat /var/pid/lovely-app.pid)` to do a clean shutdown, -HUP to restart all workers, etc.