Allow stopping commands properly

[SamuelNitsche]

While using solo, I noticed there were some issues when trying to signal commands like php artisan serve, php artisan horizon, etc.
This is immediately visible in the case of serve, since the tasks can't be stopped and started again because of the old process still running and blocking the port.
As you can see in the screenshot below, the Symfony Process itself wraps the actual command defined in the service provider with another process. This is documented here

So when the process was stopped, only the wrapper process itself was stopped but not the actual php artisan serve process.

When starting the process using an array command instead of a string command, Symfony will not wrap it in a subprocess. This way we can stop the actual php artisan serve command process instead of its wrapper process.

I tested this manually with all the default commands solo ships however I am not entirely sure if and how this way of starting the process has some drawbacks.

A lot of command and process here, I hope this makes sense.

I think this is also the reason why pail didn't stop here

[aarondfrancis]

Oh I think this is the ticket. Great catch. I think I have one more thing to add and then I'll merge this. Thank you so much for the investigation

[aarondfrancis]

Actually I think it's perfect as is. I was gonna look at at Process::fromShellCommandline but it suffers from the same problem: https://github.com/symfony/symfony/blob/7.1/src/Symfony/Component/Process/Process.php#L175.

Thank you!