pkg/sops-nix
1
0
Fork 0
mirror of https://github.com/Mic92/sops-nix.git synced 2026-07-17 06:25:16 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

README: fix Home Manager Systemd unit configuration

Browse source 
Since Home Manager relies on the naming scheme used by Systemd, the
current way to set a dependent service defined in the README fails as
Systemd doesn't support it.
This commit is contained in:
gumball76 2025-11-29 13:56:43 -06:00 • committed by Jörg Thalheim
parent 5745e46834
commit 207df45fb4
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -851,7 +851,7 @@ The actual sops configuration is in the `sops` namespace in your home.nix (or in
The secrets are decrypted in a systemd user service called `sops-nix`, so other services needing secrets must order after it: The secrets are decrypted in a systemd user service called `sops-nix`, so other services needing secrets must order after it:
```nix ```nix
{ {
systemd.user.services.mbsync.unitConfig.After = [ "sops-nix.service" ]; systemd.user.services.mbsync.Unit.After = [ "sops-nix.service" ];
} }
``` ```