| 1 Dec 2022 |
 @linus:schreibt.jetzt | So `colmena apply` will build all the configs and deploy them via SSH, even to the laptop it's running on | 08:21:37 |
| @linus:schreibt.jetzt | (And it SSHes in as root) | 08:22:33 |
 Zhaofeng Li | In reply to @raitobezarius:matrix.org
do colmena allow to copy the nix exprs on the target so I can still run local deployment there? Copying expressions themselves can be a bit tricky to do cleanly. As an alternative, Colmena can deploy directly from a remote Flake URI like github:.
(This is tracked in https://github.com/zhaofengli/colmena/issues/33)
| 08:47:42 |
| Zhaofeng Li | In reply to @ask-yourself:matrix.org
How can I apply all my systems at once if I have to sudo colmena apply-local for local system and colmena apply --on x for remote systems? If I just run colmena apply then the local system will fail cause no sudo. I could tag the nodes and build everything but the local system, but that seems inferior to building all at once. Anybody know how to resolve this? Currently apply and apply-local are separate because apply-local requires either being launched as root or running sudo (with interactive authentication) during activation. The interactive sudo password prompt doesn't play well with the parallel deployment process. | 08:49:51 |
 @ask-yourself:matrix.org | Hmm, ok. I'm not sure I follow. I get the part about apply and apply-local needing to be separate. But are you also saying that if I build remotely that can overcome this? I don't think I will build remotely but I'd like to understand what you meant with remote FLake URI. | 08:52:32 |
 @NobbZ:matrix.org | They say, they treat the local machine as a remote one, and have set up everything to connect from local user to local root via SSH, making it transparent for colmena.
This is a common approach for all of these tools | 08:55:44 |
| @ask-yourself:matrix.org | So everything would build remotely then push back to my machines, instead of anything being built on main workstation? | 09:17:18 |
| @linus:schreibt.jetzt | No, where it's built is unrelated | 09:54:05 |
| @linus:schreibt.jetzt | but if you set it up so that your user can SSH into your workstation as root, you can deploy your workstation as if it were a remote system. | 09:54:43 |
| @linus:schreibt.jetzt | By default it will build everything on your workstation | 09:55:23 |
| @linus:schreibt.jetzt | if you set deployment.buildOnTarget for a machine, or pass --build-on-target on the command line, it will instead build directly on the host that's being deployed (though in the case of your workstation it will still end up being built on your workstation because that's what's being deployed) | 09:57:02 |
| @linus:schreibt.jetzt | but that's completely orthogonal to whether you deploy via SSH or locally | 09:57:57 |
|  hexa changed their display name from hexa to hexa (22.11 now). | 13:08:59 |
 roshan | byteio.in 🌷 | 
Download image.png | 14:07:16 |
| roshan | byteio.in 🌷 | why my userge container get stops in 1-2 seconds | 14:07:47 |
| roshan | byteio.in 🌷 | running through command line working find | 14:08:05 |
| roshan | byteio.in 🌷 | * running through command line working fine | 14:08:07 |
| roshan | byteio.in 🌷 | 
Download image.png | 14:08:27 |
| roshan | byteio.in 🌷 | 
Download image.png | 14:22:10 |
| @linus:schreibt.jetzt | That doesn't seem like a colmena-specific question, maybe try #nix:nixos.org | 14:22:59 |
| roshan | byteio.in 🌷 | im using colmena to deploy my docker container | 14:25:27 |
| @linus:schreibt.jetzt | the nixos host containing the container right? | 14:25:45 |
| roshan | byteio.in 🌷 | docker container workiing fine in local | 14:25:53 |
| roshan | byteio.in 🌷 | In reply to @linus:schreibt.jetzt
the nixos host containing the container right? yes | 14:26:00 |
| @linus:schreibt.jetzt | yeah this doesn't look like an issue with the deployment (which is colmena's job), but with the configuration | 14:26:39 |
| hexa changed their display name from hexa (22.11 now) to hexa. | 14:38:47 |
| @ask-yourself:matrix.org | In reply to @linus:schreibt.jetzt
if you set deployment.buildOnTarget for a machine, or pass --build-on-target on the command line, it will instead build directly on the host that's being deployed (though in the case of your workstation it will still end up being built on your workstation because that's what's being deployed) Ok, yes I see. This makes a lot of sense, thank you. | 16:57:29 |
 Wanja Hentze | how are you folks coping with long NixOS eval times when using colmena? | 17:40:42 |
| Wanja Hentze | any practical tricks I can pull to make my hive eval faster? | 17:40:55 |
| Zhaofeng Li | Have you tried `--evaluator streaming`? It makes evaluation actually parallel using nix-eval-jobs. It's not the default yet but may be soon | 17:54:22 |
