Use pusher driver for laravel reverb

[dstemberger]

Resolves #2564

• Added or updated tests
• Documented user facing changes
• Updated CHANGELOG.md

Changes

Allow reverb broadcast to reuse the pusher driver

Breaking changes

[thekonz]

looks like it should work, but i have to tested it

[spawnia]

looks like it should work, but i have to tested it

So should I wait or merge now?

[stayallive]

My 2 cents:

I don't really feel like this is really needed... since there is essentially just a single change which is the connection name vs. the current "pusher" driver.

This might be better fitted as a documentation blurb? Otherwise we might need to consider creating one for every Pusher compatible project like Reverb, Socketi, Socket Chief etc. The one thing this has going for it is that it is a official Laravel package of course.

Also Reverb doesn't support web hooks so technically that route isn't needed and cleanup is not happening which is also nice if this is knows. Same issue Laravel WebSockets has.

Not against this change but also not really enthusiastic about it personally.

[spawnia]

Also Reverb doesn't support web hooks so technically that route isn't needed

So we could add another method to SubscriptionRouter that does the minimal amount of work for it?

I don't mind adding support for Reverb, as it is an official Laravel package.

[stayallive]

So we could add another method to SubscriptionRouter that does the minimal amount of work for it?

The route should be removed completely for Reverb, since it will never be called (because Reverb does not have web hooks)

I don't mind adding support for Reverb, as it is an official Laravel package.

Agreed!

[spawnia]

I made a bit of a larger overhaul in #2639, please review that.

[spawnia]

I released #2639 with https://github.com/nuwave/lighthouse/releases/tag/v6.47.0.