feat(deploy): set the timezone per machine, sintra to Europe/Paris
Every machine inherited America/Guatemala from the shared base config, which is right for douro and tejo and wrong for sintra in France. It read six hours behind, so its journal timestamps had to be converted by hand against anything on the relay. The clock is not cosmetic here. system.autoUpgrade's `dates = "04:00"` is local time, so the zone decides when the nightly rebuild restarts the app and the Fujitsu dispenser runs its audible init routine. On sintra that was firing at 10:17 in the morning, in the room, rather than at 4am. timeZoneForModel mirrors fiatCodeForModel and lists only the exceptions. The base config keeps America/Guatemala as the fleet default, now under mkDefault so a per-model value wins without mkForce. Verified by eval: sintra resolves to Europe/Paris, douro, tejo and batm3 are unchanged. batm3 is deliberately left alone. It is USD and in the field, and I do not know where.
This commit is contained in:
parent
74e488cd00
commit
e98fd67653
2 changed files with 19 additions and 2 deletions
|
|
@ -46,8 +46,9 @@
|
|||
};
|
||||
};
|
||||
|
||||
# Timezone - set to your location
|
||||
time.timeZone = "America/Guatemala";
|
||||
# Fleet default. Override per machine with timeZoneForModel in flake.nix —
|
||||
# mkDefault is what lets that override win without mkForce.
|
||||
time.timeZone = lib.mkDefault "America/Guatemala";
|
||||
|
||||
# Locale
|
||||
i18n.defaultLocale = "en_US.UTF-8";
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue