How to install Speedtest Tracker on CasaOS

Discover How to Install Speedtest Tracker on Casa OS! :sparkles: In this tutorial, we’ll walk you through the process step by step, ensuring you’re set up and ready to go in no time.

1 Like

This is actually really handy to use if you are experiencing networking issues with your ISP. I had to do similar manually when I was having speed issues and needed to prove it to the ISP. eventually they offered compensation but great to have it automated.

Just be aware that obviously it will use bandwidth and need to be aware of it if you are on a limited data solution

Yes, I created a similar solution when I was having issues with an ISP and didn’t know this existed.

It does use bandwidth; between 25 and 50 MB is the estimate. Great insight, though I forgot to say that.

1 Like

Everyone, have you tried using the dev tag of the speedtest tracker docker image?

I was torn between using either the latest or dev tag. The latest tag seems very outdated. The last update was since 2 years ago.

I’ve added it to one of my appstores (CasaOS Coolstore) months ago, but I’ve set it to track the dev tag instead (specifically henrywhitaker3/speedtest-tracker:v1.12.3-dev) since it is much more updated, however there’s a problem with the cron job and it still hasn’t been fixed even until now. I was able to figure out the issue and commented this workaround into the issue thread in github so others who are experiencing the same thing can follow but it requires some manual tinkering inside the container. For me, this would be an easy task but for other users it’s a different thing.

I thought about making the video on the dev tag, but then I thought it could be unstable and the user might have issues. I noticed that the latest tag is old. So far, it has done what it was supposed to do.

I see that you changed:

schedule:run

to

speedtest:run

Schedule:run is Laravel’s way to run the commands in

which, if changed, will not let the other jobs run now.

Here is some more info: Task Scheduling - Laravel 8.x - The PHP Framework For Web Artisans

Right. but checking the logs, running schedule:run will stumble on something and stops the execution in which I had to manually set it to speedtest:run for the auto speedtest to work fine.

Did you find out what it was that it was stumbling on? Anything in the laravel.log?

I’ve forgot the specific cause, but I think it had something to do with the PHP version that was used by laravel in the image. Actually, if you ssh into the container, there’s two versions of PHP that are installed. PHP 8.2 and PHP 8.1. and as far as I remembered, it was using the PHP 8.1 one but it doesn’t have pdo extension installed. I had to switch the version to 8.2 that it came with. I mean it’s weird that it’s using two versions of PHP. I guess the developer forgot to remove the other one or something (which is understandable since this was a development branch).

I’m thinking of forking the project and fixing it myself and deploy my own docker image, but it’s an additional work. XD

If I was to fork it I would update Laravel and move to using: GitHub - serversideup/docker-php: Production-ready Docker images for PHP. Optimized for Laravel, WordPress, and more!.

I don’t know if I have time to do it.

It could use a good maintainer, though.

I think he’s in limbo with two versions trying to maintain two compatibilities which is weird.

I agree. and while someone’s at it, I would suggest to re-write the UI. It works just fine, but I think it needs some make over.

It would be cool to change Laravel to just the backend API and then create a next.js frontend that is fast and communicates with the backend API.