samueldr changed the topic of #nixops to: NixOps related talk | logs:
<sevanspowell> In the following nix-expression:
<sevanspowell> { pkgs ? import ./pkgs.nix { } }:
<sevanspowell> ```
sevanspowell has quit [Excess Flood]
sevanspowell has joined #nixops
<sevanspowell> So sorry, I meant to send that as a snippet.
* sevanspowell Aaand I posted in the wrong channel, excuse me.
<DigitalKiwi> it's ok i was just excited to see activity
<sevanspowell> Haha
{^_^} has quit [*.net *.split]
johnny101 has quit [*.net *.split]
{^_^} has joined #nixops
{^_^} has joined #nixops
{^_^} has quit [Changing host]
johnny101 has joined #nixops
kreetx has joined #nixops
<kreetx> hi
<kreetx> I have a question about deploying from multiple computers -- is it so that out of the box that is not possible?
<kreetx> since there is a state file from the first machine
<kreetx> the use case I have is that I have three nixos machines where I work from, and would want to use any of these to deploy
<adisbladis> kreetx: Right now there is indeed no good story around that use case. Many have a deployment server and do deployments from a single box.
<adisbladis> State backends is something that is in the works
<gchristensen> indeed, there is a PR in which does it -- but maybe we won't take that route
<gchristensen> easy review, short diff, fixing's handling of multi-arg'd exceptions:
<{^_^}> nixops#1265 (by grahamc, 9 minutes ago, open): parallel: handle exceptions more modern-like
<DigitalKiwi> has anyone experience with
* DigitalKiwi still dreams of the day someone else uses digital-ocean has time to review my changes :(
<DigitalKiwi> this is built on top of the digitalocean branch which brought the old digitalocean code pre-plugins into the post plugins world
<gchristensen> DigitalKiwi: I am scared to review it because the plugin stuff is so in flux right now
<gchristensen> <- adisbladis test-driven development going on here
dongcarl has quit [Read error: Connection reset by peer]
<DigitalKiwi> gchristensen: i'm not worried so much about that kind of changes i still have to add mypy and stuff and i know it's going to need a lot of work i guess i'm just not confident in my python or familiar with nixops internals to know if it's even "right" despite seemingly working (and i'm also not sure it always works either so if anyone wants to test... :P )
<DigitalKiwi> something like "lgtm you're on the right track keep it up" vs "this is wrong (while there's not a lot of stuff that can be wrong) course correct before you end up with even more of a mess"
<DigitalKiwi> i saw multiple different ways of doing that same thing in different places and i didn't know why
abathur has joined #nixops
nuncanada has joined #nixops
nuncanada has quit [Ping timeout: 258 seconds]
nuncanada has joined #nixops
nuncanada2 has joined #nixops
nuncanada has quit [Ping timeout: 272 seconds]
bhipple has joined #nixops
kreetx has quit [Quit: WeeChat 2.7.1]
nuncanada2 has quit [Ping timeout: 272 seconds]
nuncanada has joined #nixops
nuncanada has quit [Ping timeout: 272 seconds]
blumenkranz has joined #nixops
<blumenkranz> Hello. I've been reading on NixOps and nixpkgs pinning, and I still don't know what's the best way to do it. Most people seem to recommend using a nix-shell to set NIX_PATH, but I found you can also use nix.nixPath, which I find "cleaner". However, I find conflicting information on how to use nix.nixPath. Some users say it has to be set in the logical deployment (as it would make sense), but others
<blumenkranz> say it doesn't work, and one says it has to be set on the deploy host as well. Does anyone here know whether setting nix.nixPath only in the logical configuration of the target works reliably?
<gchristensen> nix.nixPath doesn't set the version of nixpkgs used to create your system, it will set the version of nixpkgs used when you use Nix on the system
<blumenkranz> gchristensen: Oh, that makes sense. So basically, it will only work on second deployment, right?
<gchristensen> no, it still won't work because presumably you're not deploying from the system you are setting the nixPath on
<blumenkranz> Alright, that makes sense. Do you happen to know why NixOps was designed without a way to declaratively pin the used nixpkgs version?
<gchristensen> I'm not sure :) it is on the list for nixops 2.0:
<{^_^}> nixops#1242 (by grahamc, 3 weeks ago, open): Release 2.0
<blumenkranz> Okay, knowing that it's on the roadmap makes me very happy hahaha.
<blumenkranz> Thanks for the help!
<gchristensen> thank you!
blumenkranz has quit [Quit: WeeChat 2.7.1]
nuncanada has joined #nixops
abathur has quit [Ping timeout: 240 seconds]