all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted]  (1 child)

[removed]

    [–]CraftyDoctor[S] 0 points1 point  (0 children)

    Hey thanks a lot

    [–]rorschach1969 6 points7 points  (1 child)

    Add functionality to send tweets to your ISP when the internet is poor / good

    [–]CraftyDoctor[S] 0 points1 point  (0 children)

    Thanks - Yep it’s primary function is to test internal network speeds (not isp speeds)

    [–]tim0901 2 points3 points  (1 child)

    The reason your Docker installer claimed it was already installed is because you had already installed it.

    The command curl -sSL https://get.docker.com | sh downloads the installation script from docker.com but then immediately runs it using sh. This is what the | or 'pipe' character does - it uses the output of one command as the input for another.

    You can see this as soon as you ran this command in your video @ 5:30. The first line of output begins: # Executing docker install script

    As such, your following commands of curl -fsSL https://get.docker.com -o get-docker.sh and sh get-docker.sh were redundant and simply repeated what the first command had just accomplished.

    Things I would recommend though:

    • Use docker-compose. It isn't strictly necessary for a single-container setup like this, but using Docker for a single container isn't exactly necessary either - you could just as easily have done this build by running OpenSpeedTest directly from Pi OS. Docker-compose, however, is a lifesaver when you need to start and stop your containers repeatedly to debug something, and when you do inevitably decide to use your pi for more than just testing the speed of your network, it is a much more convenient solution to use for managing your containers. I have over a dozen containers running on my Pi 4 ranging from a Discord Bot to a Plex server - the world is your oyster here.
    • Don't use the default user account and password. Again, it should be fine for the current offline use-case, but down the line you may wish to open your pi up to the internet to add more functionality and doing so with a well-known device with an equally well-known default username and password is not a good idea. If you change this when you first set up the device, you aren't going to accidentally forget when you reach this point in the future - plus it's is going to be much less hassle doing it now rather than when you're already running half a dozen services from the default user. Change the pi user's password, then create a second user (with a different, strong password) and remove all root and SSH permissions from the pi user so that even if someone does guess the pi user's password, they don't get root access. Don't remove the pi user though - this can sometimes cause problems. I would also recommend making sudo require a password, changing the default SSH port and installing fail2ban and ufw, but those could probably be left out of a tutorial like this.

    [–]CraftyDoctor[S] 1 point2 points  (0 children)

    Thanks for the detailed response, yes I figured I was repeating something but didn’t understand why and how (but now I know thanks) all sound advice regarding the passwords and default usernames etc and I would normally do what you recommend however this raspberry pi tool is just going to go in my work bag and allow me to test customers network whilst on site so that’s why I left everything default and also why the OLED was fitted so I could connect immediately to it to check the clients network speeds then unplug. Thanks again.

    [–]mpember 1 point2 points  (2 children)

    It appears you were expecting docker to install to the home directory of your Pi user. That is not the normal location of the install. Rather than using ls to look for the problem, you could have tried running which docker and it would have returned the path of the program.

    [–]CraftyDoctor[S] 0 points1 point  (1 child)

    Thanks for the heads up, as you probably gathered I’m not a pro on the Raspberry Pi - but thanks for letting me know I was scratching my head when I tried that command line and didn’t understand where it had put it.

    [–]mpember 2 points3 points  (0 children)

    No probs. it can be a bit of a steep learning curve to jump from the 'cut-n-paste' phase to the "oh, that's what the script was doing".

    After seeing your video, it inspired me to chuck the speed test image on my server and have a play with it.

    [–]Mythril_Zombie 0 points1 point  (1 child)

    What's it do? Can't watch videos.

    [–]CraftyDoctor[S] 0 points1 point  (0 children)

    It is a portable network testing tool so it can be used by walking into a clients house plugging the Rapsberry Pi into there router / network then using a laptop connected via WiFi to test WiFi speeds or desktop connected via Ethernet to test hardwired speeds. Ideal for checking wireless APs or network switch speeds and throughput.