You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I tried integrating the package to use Laravel-Websockets which is drop in replacement for pusher but failed to get it running, I changed to pusher host on laravel side but in browser console i see it connecting to '.pusher.com' instead of Websocket server that i have on local host.
Can you please guide me if it can be integrated with that package or not in current state so that we dont use pusher.com but use our own server.
The text was updated successfully, but these errors were encountered:
@akkhan20 #140
If you want to use the web socket, you will have to abandon Pusher and use the "Laravel Echo Server + Socket.IO + Redis" bundle. (Here is the link to the documentation )
yup thanks ill do it that way but i thought Laravel-websockets had some implementation for pusher client too anyway thanks for guiding
Sent from iPhone
On 10 Feb 2019, 3:10 AM +0500, DimaBDV ***@***.***>, wrote:
@akkhan20 #140
If you want to use the web socket, you will have to abandon Pusher and use the "Laravel Echo Server + Socket.IO + Redis" bundle. (Here is the link to the documentation )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Hello,
I tried integrating the package to use Laravel-Websockets which is drop in replacement for pusher but failed to get it running, I changed to pusher host on laravel side but in browser console i see it connecting to '.pusher.com' instead of Websocket server that i have on local host.
Can you please guide me if it can be integrated with that package or not in current state so that we dont use pusher.com but use our own server.
The text was updated successfully, but these errors were encountered: