A Guide to Install and Configure Laravel Reverb on a Laravel Project 

You dont need a server for SQLite, to view the db, I use TablePlus, and for serving the sites, I use Laravel Herd

I used the sync option in this case because we were not using queues, but if you have a requirement where you need to work with queues, then you can use the database option, and for the events, you can use the ShouldBroadcastNow interface or simply use the ShouldBroadcast interface and process those events using queue.

@@TapanSharma. when i use the database as connection all jobs fail with a 0.9 http curl errpr.

you can check this out, this video is using queues to process the events: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-BEKiNgcBqJw.html

​@@lassestube As I understand it, sync runs the jobs on the main stack like PHP. I have no idea what the pitfalls of this are besides that fact that it completely nullifies the main reason of having a queue, which is that the jobs are managed asynchronously. This will only come up as a load problem I think. If you're alone and running less than one event per second, idk if you would notice. But if you have multiple users, you'll want db or redis queue because you will see performance issues. Lastly, I recently heard that you can use separate Queue Systems such as RabbitMQ, Redis Pub/Sub for really high traffick situations. But I wouldn't really know.

I have no idea man, I dont generally use docker

it means you're using an older version of Laravel

I haven't used typescript yet, but I think this will be helpful for you: advanced-inertia.com/blog/typescript

sorry for unclear question, but my question is related to reverb on typescript inertia+react I've follow all official docs and video docs but always getting error Pusher undefined even already installed all necessary also there isn't tutorial about reverb on inertiajs+react

There is one tutorial about Inertia/React and Reverb, and using above linked article, you can probably configure typescript as well, link to the video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UyEZ74l40yU.html

@@TapanSharma. thanks, will definitely checkout this video

The broadcasting part would be same, and if you're using API, then you'll probably use a dedicated frontend framework(react/vue), for that case, you can use Laravel Echo to listen for events in the frontend and react accordingly

Haha it was Sail (me) again. Forgot to open websocket port

yeah, things get messy when working with docker/sail

@@TapanSharma. Yes. After this debugging the auth, then the axios request, the dusk test, The event fired after Dusk Test, and undoubtedly the Queue will need a quarter day, and then I'll have confirmed the listener works :)

Thats sad man, have you figured it out?

​@@TapanSharma. haha well its a little fun. I did get through auth or at least got it to stop giving errors. And then I moved onto a smaller project where I'm just building a mortgage site with inertia. Below here I'll just document that issue: But lemme check the commit that did fix it... Ok I was getting 404's and 500 errors for an auth file in console. And the fix was related to Sail and Localhost, because I did not feel like setting up an ssl. So I had to set forceTLS to false, and disableStats to true(?), made sure the listener name now matched, made sure the auth logic made sense, and added this to web routes: Broadcast::routes(); Those two values are in echo.js, the listener is obviously on your frontend component, the auth route logic is inside routes/channels.php, and you know where web.php is. After this I just needed to do some logic cleanup. At least the devops portion should be done.