Can I create a background process in the app cluster to just run a custom php artisan reverb:start? Or that's not going to work? I read that we must use another server for reverb, but I'm wondering why it will not work on Cloud.
#Reverb or Queue listen in Laravel Cloud
blazing wave
fleet idol
I tried doing this but I haven't been able to test cause I keep getting cloudfare error when I visit the domain
shut ridge
Reverb is not supported atm, but being worked on atm.
runic laurel
blazing wave
Thanks Sylvester! I thought that maybe adding a custom reverb command in the cluster could work. I guess there's not an expected delivery date for this support, right? I'm releasing an MVP in two months and I was wondering if I should just go with another approach instead of cloud just to be safe on the reverb support.