New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Wobserver usable as a standalone Plug #1
Comments
Completely agree. We are currently running into the same thing. It is a waste to have multiple cowboy instances. Completely dropping it would not be possible, because I would like to keep the drop-in usability. I'm currently working on an option to just run it as plug without starting cowboy and when done will update the readme to show how to redirect the websocket. Do note that the interface will fallback to the api/ajax if it can't connect through websocket. |
I'd like to have real-time updates, so forcing it to use fallback mode is kind of undesirable. |
I think #2 should enable you to run wobserver as a plug. Wobserver does not start a supervisor or |
Version 0.1.4 is now on hex and has this feature. |
Cool, thanks. |
Instead of having wobserver run its own cowboy instance with (apparently) no authentication, I'd like to be able to run wobserver from inside an app's existing administrator panel.
The main barrier to this is wobserver's websockets, which can be replaced with
EventSource
.The text was updated successfully, but these errors were encountered: