ornxka has quit [Quit: No Ping reply in 180 seconds.]
ornxka has joined #home-manager
kalbasit has joined #home-manager
kalbasit has quit [Ping timeout: 240 seconds]
cole-h has quit [Ping timeout: 265 seconds]
tdeo has quit [Ping timeout: 260 seconds]
tdeo has joined #home-manager
ece has joined #home-manager
niacdoial has joined #home-manager
Reventlov has joined #home-manager
<Reventlov>
Hei.
<niacdoial>
hey
zmacs has quit [Ping timeout: 260 seconds]
zmacs has joined #home-manager
<Reventlov>
I have a kind of egg/chicken problem. I'd like to use home-manager to manage my home, but from the system configuration.nix.
<Reventlov>
This includes cloning a private repository, but using a private key also deployed using home-manager; how can I do that ?
<NobbZ[m]>
As I do not want to make secrets of any kind public through the store, I do not manage them through HM or anything else.
<NobbZ[m]>
SSH keys are sideloaded from an encrypted USB stick I always carry with me
<Reventlov>
I don't really care about this, myself, I store everything in the store
<Reventlov>
so right now I have a ".ssh/id_ed25519".source = "${../../nixos-secrets/foo/bar_private.key}";
<NobbZ[m]>
As the store is world readable I'd suggest to revise that decision
<Reventlov>
1. My computer is encrypted
<Reventlov>
2. I'm the only user of my computer
<Reventlov>
yes, this is world readable, but as my home for any process running with my user not tightly isolated as a service would be. On a server, I agree, on a desktop, I feel that's useless.
<NobbZ[m]>
As of today. Anyway, I don't see much of a solution rather than preprovisioning those keys
ardumont has quit [Ping timeout: 264 seconds]
ardumont has joined #home-manager
niacdoial has quit [Ping timeout: 260 seconds]
niacdoial has joined #home-manager
justanotheruser has quit [Ping timeout: 264 seconds]
superherointj has joined #home-manager
superherointj has quit [Remote host closed the connection]
niacdoial has quit [Ping timeout: 260 seconds]
niacdoial has joined #home-manager
justanotheruser has joined #home-manager
justanotheruser has quit [Ping timeout: 264 seconds]
__monty__ has joined #home-manager
ardumont has quit [Ping timeout: 240 seconds]
cole-h has joined #home-manager
niacdoial has quit [Ping timeout: 260 seconds]
niacdoial has joined #home-manager
kalbasit has joined #home-manager
woffs has quit [Ping timeout: 256 seconds]
c0c0 has quit [Ping timeout: 272 seconds]
niacdoial has quit [Ping timeout: 240 seconds]
johnw has joined #home-manager
c0c0 has joined #home-manager
kalbasit has quit [Ping timeout: 256 seconds]
<rycee>
rogerr: If that's the `startwm.sh` that gets executed then I don't see why the `hm-session-vars.sh` content isn't available. Are you absolutely certain that script is what is executed when you login? Perhaps you have two i3 desktop manager sessions available in the display manager menu and accidentally chose the non-HM one?
<rogerr>
rycee i don't have a display manager, i login with freerdp and go right into window manager. re: if ~/startwm.sh is used or not, it's configured using xsession.scriptPath = "startwm.sh" like docs say. that confirm it or?
<rycee>
rogerr: I don't know how freerdp works but I imagine it needs to be told which session script to use? The `xsession.scriptPath` option just says where the script should be written, it doesn't attempt to do any integration with anything. The default of `.xsession` is chosen because NixOS will by default use that file, if it is present.
<rycee>
So unless freerdp somehow knows to execute `~/startwm.sh` it probably would choose some other session to start.