| 14 Jul 2022 |
tylerjl | Ah, those are both great and should get me to where I need, I really appreciate it | 22:34:50 |
Buckley | at some point i stopped doing this as a performance optimization. by building the machine in the flake as nixosConfiguration, then feeding it to colmena to build it again, theres some overhead | 22:35:13 |
Buckley | its not much if you just have a couple machines | 22:35:32 |
tylerjl | Yeah, this is all personal infra / should be < 30 hosts at max | 22:35:52 |
tylerjl | nixosSystem is sort of a new one to me, is that significantly different than a flake nixosConfiguration? | 22:36:12 |
Buckley | i have 10 servers and I felt it was enough overhead to change it. | 22:37:06 |
tylerjl | Hm, some of my hosts are aarch64 so I could very well end up with a lot of overhead if I keep building them through binfmt. I'll keep that in mind | 22:37:51 |
Buckley | nixpkgs.lib.nixosSystem ? | 22:38:12 |
tylerjl | Oh, wait, yeah, nixosSystem is the "type" that you feed into a nixosConfiguration (I think). Makes sense | 22:39:17 |
Buckley | nixosSystem is a function that generates what goes in nixosConfigurations | 22:39:53 |
| 15 Jul 2022 |
garionion | hi, is there a way to upload single files or whole directories with colmena? | 07:44:22 |
CRTified | In reply to @garionion:entr0py.de hi, is there a way to upload single files or whole directories with colmena? This is more nix-like, but you can generally add files and directories to the nix store and copy them over by referencing them in your config. The easiest target is /etc/, but you are generally free to do as you wish by e.g. linking with systemd.tmpfiles.rules or writing a custom systemd service. Note that this approach is not suitable for secrets, as they're in the world-readable store. For these, use colmena's deployment.keys. | 08:36:34 |
CRTified | In reply to @garionion:entr0py.de hi, is there a way to upload single files or whole directories with colmena? * This is more nix-related, but you can generally add files and directories to the nix store and copy them over by referencing them in your config. The easiest target is /etc/, but you are generally free to do as you wish by e.g. linking with systemd.tmpfiles.rules or writing a custom systemd service. Note that this approach is not suitable for secrets, as they're in the world-readable store. For these, use colmena's deployment.keys. | 08:36:56 |
garionion | uhh, your right, i totally forgot about that (i already use it on my laptop ^^) | 08:37:50 |
garionion | thank you ^-^ | 08:37:55 |
CRTified | No problem 🙂 | 08:38:04 |
| 17 Jul 2022 |
| rendakuenthusiast joined the room. | 04:28:23 |
rendakuenthusiast | I'm getting a "child process was killled by signal 11" error when I try to use colmena to remove a specific piece of configuration from a remote machine, not sure how to debug | 04:29:16 |
rendakuenthusiast | specifically this happens when I try to remove a vhost from an nginx config | 04:29:45 |
rendakuenthusiast | literally deleting the block because I don't need that vhost anymore | 04:29:57 |
rendakuenthusiast | I tried renaming the vhost and that seemed to apply without a problem | 04:30:12 |
Winter (she/her) | oh wow that's weird
i assume the vhost names don't have anything weird about them? | 04:30:46 |
Winter (she/her) | like any weird characters or something | 04:30:53 |
rendakuenthusiast | nope, just normal ascii urls | 04:31:00 |
Winter (she/her) | if you run with --verbose, where is it segfaulting? eval? | 04:31:30 |
rendakuenthusiast | is there a way I can tell what the child process is? | 04:31:31 |
rendakuenthusiast | does colmena have a verbose option? | 04:31:54 |
rendakuenthusiast | I'm specifically running nix-shell -p colmena --run 'colmena apply -f my-hive.nix' | 04:32:19 |
Winter (she/her) | In reply to @winterqt:nixos.dev if you run with --verbose, where is it segfaulting? eval? ^^, it won't show what command is being run but it'll at least show if the failure is eval or apply related | 04:34:13 |
rendakuenthusiast | ok I'll try that | 04:36:39 |