I know there's a (now free) self-hosted Websockets plugin as an alternative to Pusher. But frankly, I'd be happier just using the stock Pusher functionality because I know it's maintained by the core team.
However, I've been running my own drop-in-replacement to Pusher for years now.
I've been using https://github.com/beyondcode/laravel-websockets all this time, and am now planning to switch to the newer and more actively maintained https://github.com/socketio/socket.io
The point is, both of these are meant as drop-in-replacements to Pusher, meaning the API is identical and so are all the supported features, you just have to point to the server where you're hosting it instead of the regular Pusher service.
I had a look at the Pusher configuration and you don't seem to allow us to add the server as a configuration option. I believe it would be as simple as that. I'm sure I can just fork/modify the code myself but.. it seems it would make a lot of sense if you just let us provide you with the server URL.
Any chance that can be added or else.. any thoughts on this?
Many thanks!
