Open mikkotikkanen opened 6 years ago
What config file are you copying?
You can ssh once to each machine and run:
echo "$FULLPAGEOS_OVERRIDE_TIMEZONE" > /etc/timezone
dpkg-reconfigure -f noninteractive tzdata
This should be permanent.
I'm (or anyone else) installing the ready-built images, or if update is needed just overwriting the existing install with new write to the SD card. The boxes are/would be used in multiple locations in multiple countries so SSHing to every new one isn't really feasible. Having the config file like fullpageos-wpa-supplicant.txt
ready-made which could be copy-pasted on any computer as the SD card has been written would be the ideal solution for anyone doing similar things.
Just to understand your usecase - you personally have multiple devices around the world? Or are you saying hypothetically? What exactly are you doing?
Not me personally but the company that I work for, offices in 4 different countries, thus the "distributed" nature of problem. Currently we are using FullPageOS for devops screens that show graphs & statistics about the production stacks for each location/team specifically and for the shared systems, however, one of the issues is that the timestamps in the screens don't match the locations as timezones default to UTC, so they need to mentally do the time conversion whenever looking at the screens. Currently only thing that they need to do for new screen is to just install FullPageOS to new SD-card, copy the network settings file and power the thing up. If there would be similar file for other settings as well, they could add that as well, specify their timezone and get correct graphs.
I understand that you can always SSH into things and do whatever you wish but the reason we ended up using FullPageOS was the ease of use and the lack of keyboards, SSH etc. to get it working, which seems perfect fit for people using it for dashboards, especially in our situation as people don't need to be familiar with *nix. Even your basic marketing person is able to get one up and running. And so far everything else works without any issues, the timestamp difference just creates an issues for potential human errors. Which is a bummer.
ok, Cool. I have zero time to implement this, so a pull request would be appreciated. You can probably also pay a developer outside the company if you don't have the knowledge in-house, and I can help you understand where to put this. I am building this in my own free time, I am not paid like you, and I barely have time to maintain this distro along with my other 7, which are all FOSS I do in my spare time.
A timezome file module would make sense in CustomPiOS.
This doesn't work in debian stretch and later. They have reconfigured how tzdata is read.
Found a post describing it here https://www.illucit.com/en/linux/timezone-in-debian-9-stretch/
Modified the following in FullPageOS/src/modules/fullpageos/start_chroot_script:
if [ "$FULLPAGEOS_OVERRIDE_TIMEZONE" != "default" ] then echo "$FULLPAGEOS_OVERRIDE_TIMEZONE" > /etc/timezone dpkg-reconfigure -f noninteractive tzdata fi
to
if [ "$FULLPAGEOS_OVERRIDE_TIMEZONE" != "default" ] then ln -fs /usr/share/zoneinfo/"$FULLPAGEOS_OVERRIDE_TIMEZONE" /etc/localtime dpkg-reconfigure -f noninteractive tzdata fi
This works for me but I haven't tested it on any other time zones as my builds take about 40 min.
@asd1int A pull request would be welcomed
I'll do a bit of testing this week and if there's no issues with setting it this way I'll submit it.
Timezone should be configurable with the config files, similar to network settings.
Currently, using FullPageOS for graph dashboards (in order to set timezone correctly) is bit tedious with multiple screens as for every installation/update you would need to separately SSH to each box or dig out keyboards to manually go through every box. This would be far superior with just copying the same config files on every install/update, much like with network settings.