Repository navigation
nix: point the daemon at the generated config - #117
Merged
Merged
Conversation
The module wrote /etc/watt.toml but never passed it to the service, so the daemon ignored services.watt.settings and ran the builtin default. Set WATT_CONFIG on the unit.
NotAShelf
approved these changes
Oct 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The NixOS module wrote
services.watt.settingsto/etc/watt.tomlbut never told the service where it was. Watt only reads--configorWATT_CONFIG, so the daemon quietly ran its built-in default config.This sets
WATT_CONFIGto the generated file onsystemd.services.watt. Because the value is a store path, changing the settings also restarts the unit, but I suppose that's not really an issue in practise.