Comments
Would it be bad if we create another main key for soketi in [broadcasting.php] instead of replacing the pusher one?
0
Shouldn't Soketi be installed a devDependency instead with the -D option?
Update: Oh, never mind. It's not among devDependencies, because using it wouldn't be through the compiled bundle, I guess.
0
@alexgarrett-smith
It would be a good idea to add a Forge installation guide with SSL to make this a more practical real world solution.
Local set up is fine, but users need to see how to set these things up in the wild as well.
Thanks as always for your hard work.
8
I agree, As i’ve been having issues setting it up correctly on my end as well.
0
+1
0
+1
0
I've tried this, but having error on SSL using laravel valet. Can u do a video showing how to use laravel valet.
1
Either run as http or if you are already running as http, run valet secure site_name
0
-Update It connected with the following error Pusher error: cURL error 52: Empty reply from server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for
0
In valet you can set up a proxy that will map a secure domain to a specific local port.
Let's say your Laravel site domain is example.test, you can create a proxy like so:
1valet proxy socket.example http://127.0.0.1:6001 --secureThen you should be able to change your PUSHER_HOST setting to https://socket.example.test
You may need to play around with the env, broadcast.config, and echo settings to get it working perfectly.
0
Local environment is connected, but still seeing curl issue as mentioned above
{"event":"pusher:error","data":{"code":4001,"message":"App key local does not exist."}}
0
Did you set a local app key?
0
Yes, now it works. I have had few challenges with it, but it works now. Soketi is better than laravel websockets package.
0
Is anyone getting problems for whispering or presence channels (joining and living)?