pocahontasdividends realized the nodejs service would purely expose that nodejs in that path I assume
That's what I'm thinking, yes.
I do still like the generic runner service idea — you could use it to run things other than Node.js stuff, eg php's built-in server, or running Laravel's queue workers with
php artisan queue:work.
Also I think running a Node.js app would not necessarily be 1:1 with the Node.js Indigo service — you might want to run > 1 app from the one Node.js service.
However, you make a good point (if I'm understanding correctly); if a stack has two Node.js services, how would a generic runner know which to use? I'm thinking it could have a drop down allowing you to choose one of the existing services in the stack. In the GUI the implication is that you are going to run the app using that service. At a technical level it would actually just mean the chosen service is first in your PATH.
For example, if you have added a Node.js 18..0 service to your stack, you could then add a runner and configure it like this:
Is this anything like you're envisaging?