kitsunekyo/isp-speedtest-logger

basic application to run, persist, and display speedtests

isp-speedtest-logger's Issues

Remove http-server requirement and self host

Use Expressjs and self host the web server which will remove the dependency on a global package (http-server) and make the installation easier.

error: Segmentation fault

When I run the speedtest.sh, I get the following error:

$ sh speedtest.sh
Last Speedtest:
speedtest.sh: line 10: 73772 Segmentation fault      jq '.log[-1]' $LOG_FILE

Any Idea?

Risk: potentially fails when run for the first time due to license accept option in cli

when starting up the application for the first time, the speedtest fails with a dump of the license. even though license agreement options are set correctly.

it appears that it has to be done once, before an actual speedtest runs through. maybe hit the speedtest api once to accept the license on startup?

this is an issue within the speedtest-net package: (issue is created)
ddsol/speedtest.net#117

allow speedtest scheduling via node-cron (and ui)

To simplify the use of this application, node-cron would maybe be a good idea to schedule speedtests. Speedtests can anyway only be run through the api, so the api should run 24/7, which gives us a node platform to schedule tasks on.

editing the speedtest task via the ui would be great.

Nothing shows on Safari (iOS or MacOS)

So it works on Firefox and Chrome.. but its just a blank page on Safari.

The page source is correct just nothing is being shown.

I have tried to figure out why but my skills are lacking!

api call getting stuck

after 5 reloads via the UI button, api state gets stuck in loading

Wrong alias in docker-compose.yml

api seems unable to connect to the db. i think the problem is the wrong alias used in docker-compose.yml file

suggestion:
change
MONGODB_CONNECTION_STRING=mongodb://isp-db:27017/isp
to
MONGODB_CONNECTION_STRING=mongodb://db:27017/isp

and add the option

    links:
        - db

to the api service.

also change the environment in example.env to
MONGODB_CONNECTION_STRING=mongodb://db:27017/isp

furthermore:

example.env seems to miss the NODE_ENV enviroment

suggestion add to example.env
NODE_ENV=production

my speedtest-cli doesn't put out "Speed result"

Example json output:

{"upload": 394316287.9202392, "download": 710810930.4632795, "server": {"country": "United States", "url2": "http://sp2.aethosting.com/upload.php", "latency": xxx, "lon": "xxx", "sponsor": "AET Hosting Solutions", "name": "Washington, DC", "host": "speedtest.aethosting.com:8080", "d": 478.1985075127686, "lat": "38.9047", "url": "http://sp1.aethosting.com/upload.php", "cc": "US", "id": "7960"}, "timestamp": "2017-01-20T00:11:17.559249", "ping": 12.474}

MongoDb sometimes not persisting data on windows

Reproduce:

1. run docker containers, and add speedtests via the api
2. restart machine
3. run docker container again

Current Result:
Data is empty

Expected Result:
Data from previous run is still available

Add proper loading and error data loading handlers on dashboard

As a user I want to see visual feedback, that data is loading, until its displayed. Same goes for errors when fetching data.

dockerized api not working

when running docker compose, api does not respond on /speedtest.

possibly mongodb issue

License?

Hi,
can you please add a licence to your code?

[Enhancement] Reduce bundle size by importing only used lodash functions

You're currently importing the whole lodash library with import _ from 'lodash'; in:

• client/src/shared/utils/math.js
• client/src/Dashboard/TestHistory/index.jsx
• client/src/Dashboard/AveragePerformance/index.jsx
• client/src/Dashboard/Speedtest/index.jsx

This leads to an unnecessarily increased bundle size.
Check out this blog post and the mentioned babel plugin to decrease the bundle size.

add unit tests

obviously

demo page down

since my ISP is acting up, i cant get port 8080 to open to the public from my nas. will try to get this up and running again. hope the screenshot gives a decent picture till then.

Keep app stateless and move config into mongodb

configuration should be stored outside the application. having a stateful app could lead to issues.

move "scheduling" config into a configuration state in mongodb

jq not found on osx

in osx, better add in requirement in README.MD
brew install jq

Move hardcoded links to a config file

For example:

https://github.com/kitsunekyo/internet-speed-log/blob/master/js/app.js#L153

Publish to NPM

To make the installation easier, publish the package to NPM.
Preferably after #11 and #12 are implemented.

breaks when updating speedtest schedule

last update broke the schedule update. something is wrong with the body validation on the post request.

demo page not working

having some port issues because i switched ISP. so the demo page is not working atm :)
The screenshot should give you a good idea nevertheless

provide server events to get realtime progress on speedtest

speedtest-net offers events to listen to, when starting a test.

test phases could be pushed to the client via socket.io and displayed to give better ux

Switch to using speedtest-net

You are mixing js and python and the installation is complex.
Move to just using Node.js with the speedtest-net package.

Pagination for Test Results

currently all test results are fetched from the db and displayed, when the user navigates to /dashboard. for large datasets this will be 💩.

add a query option to only load speedtests between a start and enddate. (selected through UI)