Support for Laravel Herd PHP-FPM binary naming convention

[woerndl]

Description
I am using Laravel Herd on macOS. The Symfony CLI correctly detects Herd's PHP CLI binary (e.g., php84), but it fails to detect the corresponding PHP-FPM binary.

It appears the current binary scanner does not recognize this naming pattern, causing symfony server:start to fall back to the PHP CLI server (causing various problems in my case).

Steps to Reproduce

1. Install Laravel Herd
2. Run symfony local:php:list

Actual Result
The FPM column is empty for the Herd installation, looking something like:

+---------+-----------+---------+---------+
| Version |    PHP    |   PHP   | Server  |
|         |    CLI    |   FPM   |         |
+---------+-----------+---------+---------+
| 8.4.15  | bin/php84 |         | PHP CLI |
+---------+-----------+---------+---------+

Workaround
Creating a symlink that matches standard naming conventions fixes the detection immediately:

ln -s "/Users/user/Library/Application Support/Herd/bin/php84-fpm" "/Users/user/Library/Application Support/Herd/bin/php-fpm"

Suggestion
Please consider updating the binary discovery logic to include the phpXY-fpm pattern to support Laravel Herd natively.

[Kocal]

Hi, adding support for a new "provider" is pretty simple, you can get inspiration from #26

[tucksaun]

Actually, changing the binary-name is probably the least easy of the changes and you can't really rely on the discoverPHPVia* functions 😓

But does it actually makes sense? I mean changing the binary name from one installation to another makes it really hard to use it programmatically but is also by the user. Can you imagine if bash or zsh were changing their binary name for every minor version?

To prove my point: this actually only works because Herd is adding a symlink named php (I guess to remain compatible with literally everything expecting PHP binary to be named php, not php84 🙄 ) and changes your PATH (without really letting you know).

IMHO it would be easier (maybe even better?) for them to add an php-fpm link.

[woerndl]

Disclaimer: I don't know much about the internal "politics" of either project.

IMHO it would be easier (maybe even better?) for them to add an php-fpm link.

From a user perspective, any solution is a good solution in this case, I'd say. Do you want me to ask "them" (meaning opening a related issue), or do you have a more direct channel of communication to gauge their willingness?

[tucksaun]

do you have a more direct channel of communication to gauge their willingness

Unfortunately I don't 🤷 maybe @nicolas-grekas ?