Colmena | 324 Members | |
| A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena | 111 Servers |
| Sender | Message | Time |
|---|---|---|
| 7 Jun 2022 | ||
| I don't know, but I've seen that reason a few times (not limited to colmena), always with the advice to make root as inaccessible as possible | 09:11:53 | |
| 8 Jun 2022 | ||
How do you folks feel about adding a --interactive or --confirm (actual name can be bikeshed) option to colmena that makes it prints the list of target hosts and asks you to confirm before proceeding? | 16:56:51 | |
| 9 Jun 2022 | ||
| That sounds like a reasonable feature to add | 03:42:09 | |
| 13:25:40 | ||
I'm hoping someone here can help me out. If not, I'll open an issue on the github. I can't get --keep-result to do anything. I'm running colmena build --keep-result, and it doesn't create any .gcroots directory. I've tried it with and without flakes. | 16:39:06 | |
In reply to @shine:proqqul.netThe current implementation only creates GC roots as one of the last steps after a successful activation (not build). It should probably be moved to after the build. | 16:56:15 | |
| (done) | 18:33:07 | |
Thank you! <3 I was trying to make that change myself and getting bogged down in where exactly mut should and shouldn't go (not a rust programmer) | 18:46:49 | |
Oh. Hm... I'm still having the same behaviour (nothing being produced with --keep-result) | 18:47:14 | |
Hmm, it does create them for me with colmena build | 18:56:13 | |
| Aha! It works when using flakes, but not without | 18:57:48 | |
| presumably it doesn't know how to find the hive directory in a non-flake build | 18:58:03 | |
| Weird, it should be able to create GC roots with non-flakes (actually we are only testing it in the non-flake path in the end-to-end tests) | 19:00:28 | |
| Just tried and it does work in the non-flakes case | 19:01:47 | |
| oh never mind, I see it now. | 19:09:28 | |
| I think i might have just been looking in the wrong place | 19:09:37 | |
| anyway, this works great. thank you :) | 19:22:21 | |
| 10 Jun 2022 | ||
| 08:54:46 | ||
| 18 Jun 2022 | ||
| Hey Zhaofeng Li: would you be willing to consider https://github.com/zhaofengli/colmena/pull/89? I wanted to continue hacking along on my colmena adoption, but I feel like a tightrope walker without security if I need to deviate too much from upstream. I think I'm just not ready yet for forking, so I'd appreciate if I can build on those building blocks. | 02:10:55 | |
| * Hey Zhaofeng Li: would you be willing to consider https://github.com/zhaofengli/colmena/pull/89? I wanted to continue hacking along on my colmena adoption, but I feel like a tightrope walker without security if I need to deviate too much from upstream. I think I'm just not ready yet for fully forking, so I'd appreciate if I can build on those building blocks. | 02:11:12 | |
| * Hey Zhaofeng Li: would you be willing to consider https://github.com/zhaofengli/colmena/pull/89? I wanted to continue hacking along on my colmena adoption, but I feel like a tightrope walker without security if I need to deviate too much from upstream. I think I'm just not ready yet for fully forking, so I'd appreciate if I could build on those building blocks. | 02:11:26 | |
| * Hey Zhaofeng Li: would you be willing to consider https://github.com/zhaofengli/colmena/pull/89? I wanted to continue hacking along on my colmena adoption, but I feel like a tightrope walker without security if I need to deviate too much from upstream. | 02:11:56 | |
| 10:03:38 | ||
| 19 Jun 2022 | ||
In reply to @blaggacao:matrix.orgHi sorry, been busy in the past couple of days. Minimizing the eval interface should be fine and I'll review and merge it today. | 20:09:17 | |
| Note that the eval interface is still subject to change in the near future, like for the upcoming auto rollback feature as well as https://github.com/zhaofengli/colmena/pull/96 | 20:09:18 | |
| Since using deploy-rs, I never used the auto-rollback feature. But this is probably less a fault of the rollback fearure amd more of the systemd-mediated choreographed (not orchestrated) reconciliation loop. | 20:49:17 | |
| (i'm alluding at the choreography vs orchestration discussion, here) | 20:50:28 | |
| 21 Jun 2022 | ||
| 00:04:54 | ||
| (New to Colmena and just Nix in general). How do y'all deal with bootstrapping secrets in a Colmena deployment. For example, I have a secret key that I don't want to keep in repo. So every time a developer clones the colmena nix code they would have to get the secret key and create the file on their local machine. I want to split my colmena deploymeny into 2 parts:
Does this make sense to do? | 00:24:45 | |
| * (New to Colmena and just Nix in general). How do y'all deal with bootstrapping secrets in a Colmena deployment. For example, I have a secret key that I don't want to keep in repo. So every time a developer clones the colmena nix code they would have to get the secret key and create the file on their local machine. I want to split my colmena deploymeny into 2 parts:
Does this make sense to do? | 00:25:36 | |