Colmena | 302 Members | |
| A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena | 104 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 Feb 2022 | ||
| because i already had a flake with my servers 🤔 | 02:15:31 | |
| Found it | 02:15:34 | |
| It looks perfect for me, as I also want another possible flake output (to generate sd images for my SBCs with the same config) | 02:16:16 | |
| Thanks, that's really useful 🙂 | 02:16:22 | |
In reply to @schnecfk:ruhr-uni-bochum.deIt's because Colmena needs to inject its own modules for deployment.* options as well as module arguments (nodes, name). This is also consistent with the way NixOps implements its flakes support (outputs.nixopsConfigurations). | 02:16:35 | |
| It also provides a clear upgrade path for users using legacy hive.nix to flakes | 02:17:13 | |
| Oh, that explains a lot. In that case, it might be great to document the shim-method that Buckley posted, as it should give "the best of both worlds" | 02:17:50 | |
| there has actually been an update since then as well, i have a custom module to store my deployment options, but you dont actually need that anymore, as the colmena flake exposes its modules as an output now | 02:18:27 | |
In reply to @zhaofeng:zhaofeng.li Also regarding upgrading to flakes, note that Colmena can auto-call if
and importing it like | 02:27:38 | |
If the current directory contains both flake.nix and hive.nix, then flake.nix is always preferred | 02:28:12 | |
* If the current directory contains both flake.nix and hive.nix, then flake.nix is always preferred if you don't specify a config file explicitly | 02:29:39 | |
| That iirc fails as I previously imported channels directly all over the place 😅 So my goal is indeed to have a flake config without such a transition configuration | 02:33:48 | |
| 03:46:59 | ||
In reply to @phaer:matrix.orgno exactly, | 14:27:34 | |
| 14:28:23 | |
*
| 14:30:17 | |
*
| 14:30:53 | |
*
| 14:31:31 | |
| only this works to me. If I import nixosModules.deploymentOptions and move deployment directive to nixosConfiguration I get this error: | 14:33:32 | |
error: The option deployment.allowLocalDeployment' in <unknown-file>' is already declared in /nix/store/rz7wzrgh4fpdgab95dgrx46ig2gc2nym-source/flake.nix'.` | 14:38:23 | |
* error: The option 'deployment.allowLocalDeployment' in '<unknown-file>' is already declared in '/nix/store/rz7wzrgh4fpdgab95dgrx46ig2gc2nym-source/flake.nix'. | 14:38:45 | |
* only this works to me. If I import nixosModules.deploymentOptions and move deployment directive to nixosConfiguration I get this error running colmena apply-local | 14:39:27 | |
* only this works to me. If I import nixosModules.deploymentOptions and move deployment directive to nixosConfiguration I get this error running colmena apply-local | 14:39:46 | |
| 15:15:09 | ||
| Im also realize while playing with colmena/nixosConfigurations outputs that colmena are impure builds. Is there some option to force pure builds?? | 15:35:17 | |
In reply to @janejasperous:one.ems.hostthere isn't, but you can just remove this line: https://github.com/zhaofengli/colmena/blob/f674ddf1739aa79ac9dcad38771cc89c662eaa6a/src/nix/evaluator/nix_eval_jobs.rs#L84 | 16:42:07 | |
| but i'm curious why impure is passed by default, i only see it mentioned there and in a test, cc Zhaofeng Li | 16:42:30 | |
hello, is it possible to define specialArgs per node? I'd like to "inject" some attributes which depend on different values of system | 16:58:07 | |
In reply to @pacien:pacien.netApart from specialArgs, there are also normal arguments. For example, you can set the _module.args.someArg option in node configs. | 18:35:56 | |
In reply to @winterqt:nixos.devCurrently, there is an eval.nix that takes a normal hive.nix or a flake URI, evaluated in a normal impure context. If a flake URI is passed, then it's fetched using builtins.getFlake. | 18:40:37 | |