Found this off of DDG results to see if anyone was using Mercure + Laravel in prod yet.

Honestly for the hype and promise of FrankenPHP, it seems many are still too scared to use it, and also Laravel's support for Octane runners across the tool stack is half-baked for local development. That then extends to a lack of realworld anecdata about Octane, FrankenPHP and for this case Mercure.

Herd needs you to do some workarounds using proxies to get to the octane port, which kind of defeats the purpose of the Sites configs with Herd. Sail you can get away with "just" replacing the php artisan serve at least.

This is all to say: I'm glad you wrote this up, I definitely want to re-look at using Mercure broadcaster now that it all seems a bit more settled within the stack!