| 13 Mar 2023 |
 Shyim |
The option `nodeSpecialArgs' does not exist
| 08:17:58 |
| 14 Mar 2023 |
 Jeff | In reply to @shyim:matrix.org
Have someone an example for nodeSpecialArgs? I can't get it running it says that this option does not exists What version of Colmena are you running? I think that nodeSpecialArgs is new for v4.0 (although I'm not the expert here). | 04:27:09 |
| 15 Mar 2023 |
|  @agathasorceress:finallycoffee.eu joined the room. | 15:38:03 |
| 18 Mar 2023 |
|  lord-valen joined the room. | 03:42:21 |
| 20 Mar 2023 |
|  oddlama joined the room. | 18:52:44 |
| 21 Mar 2023 |
|  kdn joined the room. | 12:51:38 |
|  sefidel changed their profile picture. | 14:07:55 |
| 22 Mar 2023 |
|  segfault joined the room. | 09:45:23 |
| 25 Mar 2023 |
|  amardeeps joined the room. | 04:45:37 |
| 31 Mar 2023 |
 Ask Yourself🍉 | Hey there. Does anyone have an example of using colmena with flake-parts? | 00:07:14 |
| Ask Yourself🍉 | I upgraded my config to use flake-parts, it's really nice but I'm having trouble integrating colmena. | 00:07:45 |
| 1 Apr 2023 |
 mel (they/them) | I think this is what you want: https://flake.parts/define-custom-flake-attribute.html | 21:05:00 |
| 2 Apr 2023 |
|  Buckley left the room. | 02:26:51 |
| 3 Apr 2023 |
|  @dhl:edgerunners.eu.org joined the room. | 08:35:33 |
| @dhl:edgerunners.eu.org left the room. | 08:43:48 |
| 5 Apr 2023 |
|  R̴̨͕͇͍̞̮̐̅͆̌̀̉̐͋̈́̃̀͒́̎̅̚̚̚͠͝Ĕ̵̡̛͖͖̟̙̫̱͈̘̞̭͍͍͑̌̄͑̓̋̓̀̈̏̈́͊̇͊͆̉͂̏̀̃̚͘͝͝ͅͅD̶̡̢͔̱̖̮͙͉̘̺͓͍̩̮͈͍͗̃̀̏͌͘͜ͅŚ̸̬̭̯̬͙͇͓̬̩̳̤͚͓̤̩̺͉͖̉͛̓̿̎͊̿̆́̐͂̇͌̄̇̓͘ͅͅT̴̞̫̘̝͇͔̟̪̪̦͂̔̎̀̎ͅŎ̷̡̬̹̪͈̭̣͈̭̭͉̦̖̝̘̪͖͔̥̦̘̻̳Ṋ̶̛̫͈̳̘͚̜̔̋͆̅̈́͊̑͊̉̌̈́̾͑̈́̚ͅË̸̡̨̨̛͇̜̖͔͖̻̟̗̠̙͓̘̗̥͉͇̜͑͆͊͑͑̀̓͒͜͝͝ joined the room. | 05:47:55 |
| sefidel changed their display name from sef to sefidel. | 13:55:17 |
| 6 Apr 2023 |
 Rémy Grünblatt | hey | 11:56:22 |
| 8 Apr 2023 |
|  egor joined the room. | 18:26:49 |
| 9 Apr 2023 |
 dantefromhell | I was wondering if tags could be used to map nixpkgs overrides?
I do like the idea of each machines definition being fully contained within a single file/ directory. Needing to do per-machine meta.nodeNixpkgs feels "unclean".
I would rather prefer to use tags for grouping different machines together and than override the specific nixpkgs for this tag.
Is that possibly as of today?
| 00:58:07 |
 emily | In reply to @dantefromhell:matrix.org
I was wondering if tags could be used to map nixpkgs overrides?
I do like the idea of each machines definition being fully contained within a single file/ directory. Needing to do per-machine meta.nodeNixpkgs feels "unclean".
I would rather prefer to use tags for grouping different machines together and than override the specific nixpkgs for this tag.
Is that possibly as of today?
You might want to follow https://github.com/zhaofengli/colmena/issues/55 and https://github.com/zhaofengli/colmena/issues/71 | 01:07:44 |
 rendakuenthusiast | what's the correct way to pin the nixpkgs version when using colmena with a falke? | 04:44:07 |
| rendakuenthusiast | * what's the correct way to pin the nixpkgs version when using colmena with a flake? | 04:44:09 |
| emily | In reply to @rendakuenthusiast:imperishable.name
what's the correct way to pin the nixpkgs version when using colmena with a flake? can you elaborate?
you should have an auto-generated flake.lock | 17:42:10 |
| rendakuenthusiast | In reply to @me:indeednotjames.com
can you elaborate?
you should have an auto-generated flake.lock so in my current non-flake colmena setup, I have meta.nixpkgs = import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/<hash>/.tar.gz");, in order to pin the nixpkgs for my remote machines to a specific version | 20:58:19 |
| rendakuenthusiast | I would like to replicate this with a flake.nix setup, but I am not sure how to do that from the documentation at https://colmena.cli.rs/unstable/tutorial/flakes.html | 20:58:46 |
| dantefromhell | In reply to @me:indeednotjames.com
You might want to follow https://github.com/zhaofengli/colmena/issues/55 and https://github.com/zhaofengli/colmena/issues/71 thx a ton for the hints! | 21:49:23 |
| emily | In reply to @rendakuenthusiast:imperishable.name
I would like to replicate this with a flake.nix setup, but I am not sure how to do that from the documentation at https://colmena.cli.rs/unstable/tutorial/flakes.html oicic
you might want to read up some generic flake tutorials
an extremely brief introduction would be that inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable" you can see in the example you linked to sets the nixpkgs of your nodes to the nixos-unstable branch.
when you run colmena the first time with a flake.nix, nix will automatically create a flake.lock, containing a rev of a commit of that branch from github.com/NixOS/nixpkgs
you can use any branch you like, e.g. nixos-22.11 or nixos-22.11-small
to update the rev in the flake.lock, you can use nix flake update
| 23:17:34 |
| 10 Apr 2023 |
| rendakuenthusiast | In reply to @me:indeednotjames.com
oicic
you might want to read up some generic flake tutorials
an extremely brief introduction would be that inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable" you can see in the example you linked to sets the nixpkgs of your nodes to the nixos-unstable branch.
when you run colmena the first time with a flake.nix, nix will automatically create a flake.lock, containing a rev of a commit of that branch from github.com/NixOS/nixpkgs
you can use any branch you like, e.g. nixos-22.11 or nixos-22.11-small
to update the rev in the flake.lock, you can use nix flake update
is there a way to set the rev to an explicit value from the beginning, like I'm doing with the non-flake version? | 09:34:38 |
| dantefromhell | In reply to @zhaofeng:zhaofeng.li
Good idea! We can add aliases, and the whole config will be generated as a string by eval.nix Reading through some old message, I am wondering if the idea of an SSH config generated by eval.nix has already been implemented and/ or an issue/ FR to it?
Github search did not prove helpful to me 🤔 <-- beginner pondering | 16:15:49 |
