-
Notifications
You must be signed in to change notification settings - Fork 7
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
suggestion: multi pc stream setup #8
Comments
Can you create a config file or env variable with the server IP, then have both the python server and JS client read that and use the specified IP? |
yes I thought about this, too. But I don't think the released JS client will be able to read stuff from the filesystem, because it would violate the Browser sandbox design? |
I'm not sure off the top of my head, but I'll look into it. I'm not a web developer by any means. |
Hey first thanks for your awesome work! |
i think if we wanna make the client configurable to enable multi pc streaming, we have to serve it from the backend kinda like a webserver |
you made a "quickfix" for a friend. how is that working ? |
I don't understand your "read stuff from the filesystem" comment, @koin612. You are not reading data from files, you are serving it with websockets. Why wouldn't you be able to put the local IP+port of the playing computer at the websocket connection (in the client/streaming computer) and make it work? |
I was thinking about a elegant way to tell the client the ip and port of the websocket server (for normal users). @jfgh But I guess including a js file where the data could be edited should be easy enough for both sides |
Hi,
some streamers are using 2 pc setup (one for gaming one for streaming).
currently websocket server only allows localhost connections.
I recently made a quickfix for a friend, but it's not PR ready, because I can't figure out a user friendly solution.
maybe server sends udp broadcasts with its ipv4, client listens and sets it?
might need an external tool for this, or can node stuff be webpacked? any other ideas?
The text was updated successfully, but these errors were encountered: