Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

BKristof's avatar

When do I *actually* need to restart Reverb?

I've been curious about something for a while now. On a live Laravel app, when does Reverb actually need to be restarted? The docs are pretty vague on this.

Currently I am restarting it on every deployment, which causes some annoying cURL errors now and then, since there's a small window of downtime.

So, does Reverb need to be restarted for code changes? Like, every time I want to add a new event? Or only when I edit its configuration? (reverb.php)

Thanks for the help in advance.

0 likes
1 reply
tykus's avatar

I believe this is pretty clear...

Since Reverb is a long-running process, changes to your code will not be reflected without restarting the server...

Changes in your application (after Reverb server is started) will not be seen without restarting that server.

Please or to participate in this conversation.