-
Notifications
You must be signed in to change notification settings - Fork 427
(Update) Migrate from laravel-echo-server to laravel reverb #5056
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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.