I noted that a significant number of the entries in the master .json list, have (and need) timezone data - all of these have been hard-set to "America/Chicago" - of course, many of us down live there... I have been giving a little bit of thought to how to address this. Github doesn't (to my knowledge) allow conditional (on location) variations. Perhaps a script that takes the base .json and a selected (from a menu) alternate location, and does a mass substitution, but then, that means that the .json can't be referenced as it is (on github) in the portainer menu. The only other option that I see (Which is almost as ugly) is to maintain all of the timezones in separate json's in the github repo (I think there are 387 in total) - as I said - ugly.
One final, and possibly most elegant solution - change the .json to be only UTC, and allow within the portainer code, the ability to select a timezone, apply the UTC offset, and then set that into the TZ for the container(s) in question...
There may be the weird (and unlikely use case) where someone may want to run different containers in different timezones, but that then points back to the UTC+offset as a more elegant solution (Applying to all containers, or selected containers, becomes the separate issue...)
I noted that a significant number of the entries in the master .json list, have (and need) timezone data - all of these have been hard-set to "America/Chicago" - of course, many of us down live there... I have been giving a little bit of thought to how to address this. Github doesn't (to my knowledge) allow conditional (on location) variations. Perhaps a script that takes the base .json and a selected (from a menu) alternate location, and does a mass substitution, but then, that means that the .json can't be referenced as it is (on github) in the portainer menu. The only other option that I see (Which is almost as ugly) is to maintain all of the timezones in separate json's in the github repo (I think there are 387 in total) - as I said - ugly.
One final, and possibly most elegant solution - change the .json to be only UTC, and allow within the portainer code, the ability to select a timezone, apply the UTC offset, and then set that into the TZ for the container(s) in question...
There may be the weird (and unlikely use case) where someone may want to run different containers in different timezones, but that then points back to the UTC+offset as a more elegant solution (Applying to all containers, or selected containers, becomes the separate issue...)