search

webrtc / testrtc

WebRTC Troubeshooter PROJECT IS ON HOLD
https://test.webrtc.org/
BSD 3-Clause "New" or "Revised" License
479 stars 215 forks source link

It's 2019, can anyone make this work? #286

Open pnoeric opened 5 years ago

pnoeric commented 5 years ago

I'd love to incorporate something like this into my project but I can't make this thing work at all. I've cloned it and followed the build process in the README, but it dies on the last step, where it tries to provision for Google App Engine SDK for Python (?!?!!) which I don't know anything about or even want to use.

I've been plugging away trying to get it to fly on my local environment, or even just parts of it, but there are weird things missing (presumably they are part of that app engine thing). (For example: the seemingly-basic parseUrlParameters() function is nowhere to be found, even though it's referenced in main.js.)

Has anyone cloned this repo and just simplified it? The code is four years old and development tools are more streamlined now... I'd love to see a more elegant/graceful version of what this is trying to do. I feel like this code is 90% there but the last 10% is remnants of the past ;-) that I can't get around yet.

(Generally speaking I'm also not sure why it this "PROJECT IS ON HOLD" as it says on the home page of the repo. There's no explanation in the README on anywhere else. It seems like a tool like this is SUPER useful, no?! For example: I have many users of my website who are having problems with their video connections and this is exactly the kind of diagnostics I need them to run on their end. I would send them to test.webrtc.org but that site is a little buggy, and it won't let you download a report... ugh. So I just want to incorporate this functionality into my code.)

Anyhow. I guess I'm just venting a little bit here ;-) but it's so weird that this tool, which seems extremely useful and full of functionality, was frozen in time in 2015 and nobody's bothered with it since. ¯\_(ツ)_/¯

I'll keep fussing with it and if I can get it to be more streamlined and less reliant on Google Cloud etc etc stuff, then I'll be happy to share it for others to enjoy.

KaptenJansson commented 5 years ago

git grep is your friend:

git grep parseUrlParameters .eslintrc: "parseUrlParameters": true, src/js/main.js:var parameters = parseUrlParameters(); src/ui/testrtc-main.html: function parseUrlParameters() { src/ui/testrtc-main.html: value: function() { return parseUrlParameters(); }

Lots of logic is in the polymer elements themselves in the src/ui folder.

It does not need GAE to work, in fact look how the test runs it. Just make sure to build it first. You do need to provide your own TURN server for the bandwidth tests to work however.

mailbyms commented 3 years ago

Same. I can't access to GAE, can it be hosted in a common way, like in Nginx ？