darmanandClaude Sonnet 5 9403122888 jupiter: fix Hermes cron scheduler defaulting to UTC ...

The container has no host /etc/localtime bind-mount, so hermes_time.py's
timezone resolution fell through to UTC. HERMES_TIMEZONE is its
highest-priority source (checked before config.yaml's timezone key).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-19 23:00:55 +02:00

..

configuration.nix

jupiter: add isolated Hermes Agent instance

2026-08-19 22:46:32 +02:00

disk-config.nix

refactor: move host configs under hosts/{jupiter,vps}

2026-07-13 19:34:27 +02:00

hardware-configuration.nix

refactor: move host configs under hosts/{jupiter,vps}

2026-07-13 19:34:27 +02:00

hermes-agent.nix

jupiter: fix Hermes cron scheduler defaulting to UTC

2026-08-19 23:00:55 +02:00

secrets.nix

jupiter: add isolated Hermes Agent instance

2026-08-19 22:46:32 +02:00

vm.nix

Reorganize services/ into category subfolders

2026-07-20 06:08:43 +02:00