Also great for running an SSH Agent, since they aren't coupled to some magic invocation in some bashrc but will always be started when the user session starts and cleanly terminated when you log out (or linger if you set that up)
https://git.sr.ht/~whynothugo/dotfiles/tree/c0bf9296c6ca8661...
Note that the ordering is important so that `SSH_AUTH_SOCK` is passed down to other services.
Ie, create a ssh-agent.target and have the default target depend on it.
Now your ssh-agent is guaranteed to be online when the default target comes up.
But, since the unit is already setting a fixed path for the agent, I would just put that path in my .profile and call it a day. Having systems do environment variable injection seems too fragile to me, especially for static variables.
But yeah, `environment.d` or `.profile` would be simpler. I mostly opted to keep everything in one place.