NixOS Deployments | 1249 Members | |
| NixOS Deployment tooling | 309 Servers |
| Sender | Message | Time |
|---|---|---|
| 29 Jun 2021 | ||
| Zhaofeng Li Is there a command to build and apply? Rather then having to seperately run both operations? | 21:51:57 | |
In reply to @noah:matrix.chatsubo.cafeapply automatically builds. apply defaults to apply switch and build is just a alias to apply build | 21:57:22 | |
So it's apply [nixos-rebuild target] | 21:57:26 | |
| Oh awesome, so switching from nixops should be painless then. | 21:58:12 | |
| Groovy | 21:58:14 | |
| Now I just need a util to mirror and rewrite flakes so I can serve them from my git instance. | 21:58:38 | |
| Zhaofeng Li Question, is colomena able to tell if there's no changes on a node and therefore do nothing? That is one complaint I have of nixops, by default it makes a generation per run even if there's no changes. | 23:55:28 | |
| 30 Jun 2021 | ||
| It shouldn't unless the system derivation is different, and this should be true for normal nixos-rebuild as well. I just tested by deploying to the local machine, and the second deployment didn't result in a new generation link. | 00:00:39 | |
| Cool, thanks | 00:06:08 | |
In reply to @zhaofeng:zhaofeng.liThat looks pretty awesome! As NixOps seems to be dying I've been looking for a good replacement that could ideally also act as a drop-in replacement with minimal modifications. Colmena looks very promising, thank you! | 08:54:45 | |
| 16:27:38 | ||
Zhaofeng Li: Question, when specifying a specific nixpkgs for a node can I supply it a URL? A la https://github.com/nixos/nixpkgs/archive/master.tar.gz? | 21:23:40 | |
In reply to @noah:matrix.chatsubo.cafebuiltins.fetchTarball should work | 21:26:08 | |
| So like the following:
| 21:28:23 | |
| Like
| 21:29:26 | |
| Zhaofeng Li: So I've got the following hive.nix
I've pinned the nixpkgs for the memex node that way as it relies on the linux_5_9 kernel package which is no longer in tree. However running
| 21:51:10 | |
| So as far as I figure it's not picking up it's pinned nixpkgs | 21:53:38 | |
| Looks like a typo. `memx` -> `memex`? | 22:12:46 | |
| I should probably add a warning if you are trying to override Nixpkgs for a non-existent node | 22:13:06 | |
| Sigh doy | 22:15:17 | |
| Okay now I'm seeing
| 22:15:26 | |
| So I can only assume something is off with how I'm pulling my revision down... | 22:15:50 | |
| Let's se | 22:15:52 | |
| * Let's see | 22:15:53 | |
| Okay fixed that finally. | 22:32:49 | |
| Zhaofeng Li: Final question I think, have you been able to manage aarch64 machines from an x64 machine at all? | 22:58:51 | |
| I've got the following flags in my aarch64 machines config to allow for cross compiling:
| 23:01:51 | |
| * I've got the following flags in my aarch64 machines config to allow for cross compiling:
| 23:01:58 | |
| As well as the needed quemu stuff to allow for cross compiling with binfmt. | 23:02:11 | |
No, I'm not deploying across architectures myself at the moment. But I think it should work if you either specify an aarch64-linux builder, or have extra-platforms = aarch64-linux in you nix config if you have binfmt set up | 23:08:39 | |