Now, that we have WebRTC support both in the browser (Chrome + Firefox) and Nodejs in libp2p-webrtc-star, it becomes interesting and useful to have a signalling server hosted by us that IPFS developers can rely on for their tinkering with IPFS, of course, the option to choose which signalling server to use still relies on the user, but for demos and quick hacks, this can be extremely useful.
The need for a hosted signalling server will be obliviated once IPFS does relay.
The tricky bit is that in order for a WebSockets connection to happen within a WebApplication that is being served behind HTTPS, the WebSockets, even if within a different domain, needs to be hosted behind HTTPS as well, which makes us do a little bit more work in order to host this signalling server, namely:
(I can't find the other issue you're keeping about this one.)
If you wanna be a real protocolian hero, you integrate siimon/prom-client and make one or two metrics, e.g. number of signallings done :tulip:
This is not critical from the start but monitoring is generally super useful.
Update
@diasdavid what's that ip?
Logged here: https://github.com/libp2p/js-libp2p-webrtc-star#hosted-signalling-server
We now have a hosted Signalling Server available and it is behind https too! :D
See everything here: https://github.com/libp2p/js-libp2p-webrtc-star#hosted-signalling-server
It would be reaaalllly useful if the signalling server exported metrics for prometheus. At the latest when we promote it to a domain under libp2p.io.
Is there a way to execute the star-signal (libp2p-webrtc-star) server with ssl from the cli for local development?
And if so, what parameters do I need to send?
Most helpful comment
It would be reaaalllly useful if the signalling server exported metrics for prometheus. At the latest when we promote it to a domain under libp2p.io.