(Update) Migrate from laravel-echo-server to laravel reverb#5056
(Update) Migrate from laravel-echo-server to laravel reverb#5056Roardom wants to merge 10 commits intoHDInnovations:developmentfrom
Conversation
5833035 to
b5ee9a0
Compare
Requires much less effort to get working. laravel-echo-server is way too finicky. There may be performance issues with https://www.github.com/laravel/reverb/issues/331 and https://www.github.com/laravel/reverb/issues/116 but maybe worth a shot? Fixes HDInnovations#4875.
Roardom
left a comment
There was a problem hiding this comment.
Missing reverb connection in config/broadcasting.php. Currently it seems to be falling back to pusher which just happens to be compatible with reverb.
|
The |
|
Yep, Reverb is good to go now. |
|
What's the story on this? |
Works great but missing nginx docs |
- from 4 vulnerabilities (3 moderate, 1 low) to no vulnerabilities found. - ref laravel/echo#473
- We do not use lodash. Laravel Mix auto-included lodash and it was in app.js from laravel boilerplate.
Could you please explain, are there any specific nginx settings that should be added for this PR to work? I checked Laravel docs, config seems mostly the same as for laravel-echo-server https://laravel.com/docs/12.x/reverb#web-server |
I'm finishing up the migration doc for mdbook which will be added to this PR and then merged for next release. |
Requires much less effort to get working. laravel-echo-server is way too finicky. There may be performance issues with https://www.github.com/laravel/reverb/issues/331 and https://www.github.com/laravel/reverb/issues/116 but maybe worth a shot? Fixes #4875.