Colmena | 343 Members | |
| A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena | 120 Servers |
| Sender | Message | Time |
|---|---|---|
| 13 May 2022 | ||
Interesting. I'm currently not at home and tried apply-local for the first time to update my laptop. It fails and claims my machine isn't a NixOS machine 🤔 | 13:48:31 | |
| Which versions of nixpkgs and Colmena? It doesn't look like they changed the format of /etc/os-release again | 18:59:04 | |
| 18 May 2022 | ||
| hi, im configuring my systems using colmente to deploy in my network. I'd like to have some machines running 21.11 others 22.05 other unstable. I get working this for packages, but not for full nixos system (modules,...) | 12:27:06 | |
| * hi, im configuring my systems using colmena to deploy in my network. I'd like to have some machines running 21.11 others 22.05 other unstable. I get working this for packages, but not for full nixos system (modules,...) | 12:27:13 | |
i expected declare machines as server1 = inputs.nixpkgs-2305.lib.nixosSystem { (...) | 12:29:26 | |
* i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) | 12:29:35 | |
* i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) to work | 12:29:58 | |
In reply to @janejasperous:one.ems.hostYou don't need lib.nixosSystem for colmena, just the config | 15:01:51 | |
server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) }.config could also work, i think? But haven't tested this | 15:03:21 | |
In reply to @phaer:matrix.orgKind of - I'm using such a shim to use nixosConfigurations and colmena together: https://github.com/zhaofengli/colmena/issues/60#issuecomment-1047199551 | 15:04:14 | |
| Ah, good to know. I personally just keep my stuff in the nixosModules output of my flake and can then put them into colmena configs for hosts I deploy with colmena or nixosConfigurations as needed | 15:05:44 | |
| Effectively im using colmena + nixos-rebuild | 19:57:00 | |
In reply to @phaer:matrix.orgok that work locally with nixos-rebuild. This piece of code fails becuase overwrite nixpkgs-2205 for nixpkgs | 21:43:00 | |
| 21:43:21 | |
In reply to @phaer:matrix.org* ok that works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:43:48 | |
* ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } that works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:44:21 | |
* ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:44:30 | |
* ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } works locally with nixos-rebuild. This piece of code makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:44:42 | |
In reply to @janejasperous:one.ems.hostFor that to work, you'll likely also need to use nodeNixpkgs as described in the colmena manual | 22:59:32 | |
| 19 May 2022 | ||
In reply to @schnecfk:ruhr-uni-bochum.deof course, that works. but duplicate code. Could be interesting colmena accepts nixosSystem.config as is | 08:39:52 | |
Maybe I can change my shim a bit 🤔 Might be non-ideal. For example: nodeNixpkgs could probably be populated from nixosConfigurations.hostname.pkgs | 09:10:59 | |
| 17:33:16 | ||
| 21 May 2022 | ||
| 20:31:51 | ||
| 23 May 2022 | ||
| How colmena would look like in a nushell: | 05:17:05 | |
| * How colmena would look like in a nushell: (pseudo code) ```nu colmena | where tag = oakland | each { |it| ^colmena deploy ($it.fragment) } ``` | 05:17:58 | |
| 24 May 2022 | ||
any way to increase debug/error logging for the deployment.keys options? i'm not getting much and i don't know what i'm doing wrong | 20:27:15 | |
using keyCommand, btw | 20:27:33 | |
-v is as far as it can get at the moment, and it should dump stderr from the keyCommand when it fails | 20:53:35 | |
| ok thanks feel free to ignore this so i'm forced to level up my | 20:58:23 | |
The %DESTINATION% here is templated with key.path() which is generated from the modules which should only care about the latter name | 21:19:08 | |