Closed caveman99 closed 11 months ago
Thanks for the contribution! Do you think you're able to make a test for this? Check this file for inspiration: https://github.com/jbergstroem/mariadb-alpine/blob/main/test/config.sh
You'd essentially set TZ and then check that its properly set in SHOW SESSION VARIABLES LIKE 'system_time_zone'
Sure thing, I'll commit later tonight.
@jbergstroem sorry for taking so long, the included test should work, at least it does on my fork :-)
@jbergstroem sorry for taking so long, the included test should work, at least it does on my fork :-)
Great! will take a look later today.
Thanks a lot for your contribution!
Thanks for including the patch... i had a compose stack running where the app was complaining that the DB was one hour off (CET vs. UTC). It was working, but the permanent error in the status bar was annoying and irritating for customers... :-)
Thanks for including the patch... i had a compose stack running where the app was complaining that the DB was one hour off (CET vs. UTC). It was working, but the permanent error in the status bar was annoying and irritating for customers... :-)
I will update the latest image shortly.
10.11.5
and latest
now contains the feature (bug? 😄) https://hub.docker.com/r/jbergstroem/mariadb-alpine/tags
so the container can be setup to use different timezones via the TZ ENV Variable