Closed radbasa closed 5 months ago
Sorry for the delay. I'm gonna take a look into that :)
Seeing this same issue. typically in a docker running environment, an environment variable is supported so that for example we can add a timezone
"docker run -d -p 5216:5216 -v myspeed:/myspeed/data -e TZ=Australia/Brisbane --restart=unless-stopped --name MySpeed germannewsmaker/myspeed"
the fix would be to support this variable in your docker file
ENV TZ=Etc/UTC
https://github.com/gnmyt/myspeed/blob/development/Dockerfile
anyone can then override it to the timezone they want the application to run in.
I've created a PR to fix this issue.
To make sure cronjobs run at the correct time, I've added support for the TZ
variable.
The Test Overview also now runs on browser-time instead of server time to make sure users from other time zones can see the test times correctly
General
The Bug
The "Test Overview" page shows local time correctly.
The "Test Statistics" page shows UTC time.
The cron job uses UTC time. I use
17 */3 * * *
The MySpeed storage.db contains:
Which confirms that the cronjob runs on UTC.
The last result was started manually. The "Test Overview" page shows the local time of "12:27". But, the "Test Statistics" shows the result as "04:27" which is UTC.
The following are from the host OS (Debian 12):
I am running MySpeed using the
germannewsmaker/myspeed 1.0.8
Docker container.What device are you using to access the page?
In the browser
Which operating system is your MySpeed instance running on?
Linux