YunoHost app settings system and Debian timezone changes: who propagates the new zone to app databases?
0 reputation · 29 Mar 2022, 05:12 UTC
0 reputation · 29 Mar 2022, 05:12 UTC
On a YunoHost server (assume the current stable release on its supported Debian base), the host timezone is set at the OS level, while each installed application keeps its own timezone value in its config file or internal database. YunoHost's app system pushes administrator-defined variables into app config files through its centralized settings mechanism, and its configure scripts can rewrite those files during upgrades.
I want a single, reliable way to change the server timezone once and have every installed app reflect it, without fighting the configuration scripts that may overwrite manual edits during app updates.
It is unclear whether the app settings system exposes a standard mechanism for syncing the system timezone into per-app configuration, or whether each community-maintained package handles this differently in its install/configure scripts. The behavior may also vary between apps that read the OS timezone at runtime and apps that store a fixed value in their database at install time.
YunoHost does not provide a global hook or native mechanism that automatically propagates a Debian-level timezone change to all installed application databases. The behavior depends entirely on how each individual community-maintained package was authored to handle time.
In the YunoHost ecosystem, applications generally fall into two categories regarding time: those that read the system clock at runtime (via /etc/localtime or the TZ environment variable) update automatically, and those that store a fixed timezone value in their own internal database or configuration file during installation or the last manual update.
To ensure an application reflects a new timezone without your changes being overwritten during an update, follow these steps:
timedatectl set-timezone Region/City to update the underlying Debian OS.yunohost app setting list to see if the specific app exposes a timezone variable.yunohost app setting set timezone="Region/City". This ensures the YunoHost configuration system is aware of the change and the configure script can maintain the value during future upgrades.yunohost restart to force the application to reload its configuration.Since there is no single "sync" status, you must verify each app individually. You can use the following methods:
tail -f /var/log//log to see if log entries match the new system offset.timezone column has been updated.Note: This analysis assumes you are using a current stable YunoHost release. If an app does not show a timezone setting via yunohost app setting, it likely relies on the system clock or requires a manual database update which may be volatile.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.