ChanServ changed the topic of #nixus to: Nixus is an experimental deployment tool for NixOS systems - https://github.com/Infinisil/nixus - https://logs.nix.samueldr.com/nixus/
veleiro has quit [Ping timeout: 260 seconds]
cole-h has joined #nixus
veleiro has joined #nixus
srk has quit [Remote host closed the connection]
srk has joined #nixus
veleiro` has joined #nixus
veleiro has quit [Ping timeout: 256 seconds]
cole-h has quit [Ping timeout: 256 seconds]
veleiro` is now known as veleiro
veleiro has joined #nixus
veleiro has quit [Changing host]
<veleiro> ok i did get to try from another x86 machine
<veleiro> and I still have the same exact error
<veleiro> from which source would the bad ssh key config originate?
<veleiro> i dont think this is a bad connection problem
<veleiro> bad ssh config*
<veleiro> every time I run the deploy result i have to re-run nixos-rebuild switch
<veleiro> to get the root passwordless login to work again
<veleiro> I've tried successTimeout too
<veleiro> i'm trying to deploy to a linode vps running nixos
veleiro` has joined #nixus
veleiro has quit [Ping timeout: 256 seconds]
veleiro`` has joined #nixus
veleiro` has quit [Ping timeout: 256 seconds]
srk has quit [Remote host closed the connection]
srk has joined #nixus
<infinisil> veleiro``: What's your nixus config?
veleiro`` is now known as veleiro
veleiro has quit [Changing host]
veleiro has joined #nixus
<veleiro> looks like this https://github.com/tgunnoe/nixus
<veleiro> the configuration was copied from the server, it doesnt reall differ
<veleiro> very basic nixos install
<infinisil> veleiro: Oh you have services.openssh.permitRootLogin = "no"
<infinisil> I suspect that's the problem
<infinisil> And you have `host = "root@gnu.lv"`, so it tries to SSH to root
<infinisil> If you don't want to use root, you can use a user that can sudo without a password instead
<veleiro> oh, on the server its prohibit-password though
<veleiro> but i wonder if having it in the build here affects it
<infinisil> veleiro: Well the servers configuration.nix won't influence a nixus system
<infinisil> With Nixus (and nixops, and most other deployment solutions), you specify the whole config locally, and using nixos-rebuild on the server is not really supported
<veleiro> wow how embarassing, i cant believe i missed that
<veleiro> days lost
<veleiro> at least i have nixos installed on an encrypted setup now
<veleiro> but it was because i wanted to make sure my ssh configs were fresh
<veleiro> lol
<veleiro> now life continues
<infinisil> Hehe
<veleiro> i appreciate your time and patience, thanks.
<infinisil> I like how Nixus fulfilled its purpose here: If it wouldn't have rolled back the machine, you couldn't deploy to it anymore since the config disabled root login
<infinisil> Glad we could figure it out in the end :
<infinisil> :)
<veleiro> look ive been evaluating nix devops tools all week, and i chose nixus
<veleiro> i really did not want to go back to a nixops idea, and reluctant to even do morph
<veleiro> nixus interested me the most becaus it was simple and 100% nix
<veleiro> some feedback about the potential movement to haskell.. =)
<infinisil> veleiro: Feedback received!
<infinisil> One idea I've played with is to base Nixus on executables with a standard API
<infinisil> So e.g. you'd have a binary that does a deployment to a machine, and what programming language that binary uses doesn't matter at all, as long as it speaks the API correctly
<infinisil> This allows splitting all parts of a deployment into different projects, and it allows each of these projects to use whatever language they want
<infinisil> Unfortunately I don't have much time to work on nixus, but the current state at least works well for me :)
<eyJhb> And for me as well, quite enjoy it :D
<eyJhb> infinisil++
<eyJhb> :( Come in here bot
<veleiro> yeah for me this works perfectly
<veleiro> i can incorperate it into same configuration repository
<veleiro> you can specify many machines in the default.nix, and it builds and deploys
<veleiro> for all of them right?
<eyJhb> Yes :)
<veleiro> thats amazing
<eyJhb> I use this `nix-build -A config.nodes.eos.deployScript` because I update my laptop all the time, and don't want to update all my servers, e.g. my router
<eyJhb> Doesn't seem like a great idea while at Uni
<veleiro> nice
<eyJhb> infinisil: Sorry to ask, but what was it you did for a living? You worked with NixOS right?
<veleiro> he's a nix celebrity that works at tweag
<veleiro> that's just an assumption
<eyJhb> veleiro: You are not new to Nix, right?
<veleiro> about a year going
<eyJhb> How does it feel to be free ? :D
<eyJhb> I think I am only at two years...
<veleiro> great but time consuming
<veleiro> its a long term thing though
<eyJhb> Yeah, but it works.. I just had to debug some Ubuntu some time ago
<eyJhb> I don't miss that
<veleiro> bunch of freaks of nature in tech like me here
<veleiro> especially in #nixos-aarch64, everyone using sway/nix/arm/emacs
<eyJhb> I want to do more aarch64 :|
<eyJhb> But never emacs
<veleiro> lol
<veleiro> whats so great about this tool and tells a lot is its like one big snippet
<veleiro> that i can copy to my configs and it will work
<veleiro> that's good design
<infinisil> eyJhb: veleiro is right, I work at tweag since 3 months ago :)
<eyJhb> Ohhh, nice! Congrats infinisil ! :D
<infinisil> Thx :D
<eyJhb> Is there any specific project you are working on for Tweag atm. then infinisil ?
<infinisil> eyJhb: I've been mainly doing Nix stuff for a client, not for a project by tweag. But occasionally I've had some time to work on Nix in general, such as https://github.com/NixOS/nix/pull/4154, or some other PR's :)
<veleiro> who says NixOS like NixAs and not Nix-OH-S anyways
veleiro has quit [Ping timeout: 256 seconds]
veleiro has joined #nixus
<veleiro> when i was having the SSH issue, i noticed how hard it was to kill process
<veleiro> as far as i could tell it runs in the background, loops retries
<veleiro> and kept getting a new process id
<veleiro> I think there's an issue for C-c
<infinisil> veleiro: Yeah definitely, there's an issue and PR about it, but it's not that easy to get right
<infinisil> Because there's processes both locally and remotely, and just killing the local ones wouldn't stop the remote one
<veleiro> understood
veleiro has quit [Ping timeout: 260 seconds]
veleiro has joined #nixus
veleiro has quit [Ping timeout: 265 seconds]