fix(mars): restart hermes when prepare-dirs' script changes
prepare-dirs is an inactive oneshot and switch-to-configuration only
restarts active units, so the .env delivery added in 461d6cc deployed
cleanly and then did nothing — the container kept running with the old
script until something else restarted it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -369,6 +369,10 @@ in
|
|||||||
];
|
];
|
||||||
requires = [ "hermes-agent-prepare-dirs.service" ];
|
requires = [ "hermes-agent-prepare-dirs.service" ];
|
||||||
unitConfig.RequiresMountsFor = [ "/mnt/jupiter" ];
|
unitConfig.RequiresMountsFor = [ "/mnt/jupiter" ];
|
||||||
|
# prepare-dirs is an inactive oneshot, and switch-to-configuration only
|
||||||
|
# restarts ACTIVE units — so editing its script otherwise lands nowhere
|
||||||
|
# until something else happens to restart the container.
|
||||||
|
restartTriggers = [ config.systemd.services.hermes-agent-prepare-dirs.script ];
|
||||||
};
|
};
|
||||||
|
|
||||||
# The two Gitea webhook routes, written as config (not via `hermes webhook
|
# The two Gitea webhook routes, written as config (not via `hermes webhook
|
||||||
|
|||||||
Reference in New Issue
Block a user