-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd service drop-ins #5401
Labels
Comments
It seems like HM doesn't have built-in support for drop-in files, so I've been creating them like this: xdg.configFile."systemd/user/my.service.d/overrides.conf".text = ''
[Service]
EnvironmentFile=.../env
''; |
Thanks! It worked: xdg.configFile."systemd/user/my.service.d/99-env.conf" = let
envFile = pkgs.writeTextDir "override.env" ''
VAR_A=1
VAR_B=2
'';
in {
text = ''
[Service]
EnvironmentFile=${envFile}/override.env
'';
}; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
NixOS allows defining
foo.service.d
drop in files usingsystemd.user.services.<name>.overrideStrategy
. How do I do the same with home-manager?I tried various things, but do not get the result I would expect, a
~/.config/systemd/user/foo.service.d/override.conf
file containing:causes:
creates
~/.config/systemd/user/foo.service
:which overrides the whole
foo.service
installed by NixOS.creates
~/.config/systemd/user/foo.service
:which again overrides the whole
foo.service
installed by NixOS.causes:
I also skimmed through https://github.com/nix-community/home-manager/blob/44677a1c96810a8e8c4ffaeaad10c842402647c1/modules/systemd.nix but could not figure out how systemd service drop-ins are supposed to work.
My
flake.nix
:The text was updated successfully, but these errors were encountered: