Colmena | 329 Members | |
| A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena | 112 Servers |
| Sender | Message | Time |
|---|---|---|
| 27 Apr 2026 | ||
| 14:57:03 | ||
| 30 Apr 2026 | ||
| 23:23:43 | ||
| 2 May 2026 | ||
| 18:41:07 | ||
| 4 May 2026 | ||
| 02:29:31 | ||
| 10:57:40 | ||
| 10:58:19 | ||
| 18:10:18 | ||
| 7 May 2026 | ||
| 00:48:55 | ||
| 00:49:03 | ||
| 11 May 2026 | ||
| 09:45:18 | ||
| 12 May 2026 | ||
| 06:47:17 | ||
| hi, thanks a lot for colmena. though I'm a long time NixOS user this is the first deployment tool I use. :) we had the problem yesterday, that the separate repo containing secrets wasn't pulled before applying changes. thus old secrets were pushed. how would you solve that? thinking about aliasing there are no pre-run hooks, right? | 07:08:44 | |
| wanna move to a CI using comin soonish, that should solve it aswell. happy about any input :) | 07:10:48 | |
| Have you considered not using a separate repo for the secrets? Secrets are part of the system configuration which can't function without them. So they need to be versioned together. | 07:57:56 | |
| Because instead of needing exactly one commit hash to reproduce a known configuration, you somehow need to keep a map between the commits of each repo. That just sounds like trouble. | 08:00:08 | |
| yep, you're right! gonna put that in one repo, solves that problem. thanks :) | 08:11:27 | |
| 11:14:42 | ||
| 14 May 2026 | ||
| 03:53:26 | ||
| 15 May 2026 | ||
| is there any doc/blog comparing colmena vs deploy-rs right now i just keep things like ./hetzner-ex63-base ./hetzner-ex63-01 ./hetzner-ex63-02 ./hetzner-ex63-02 hetzner-ex63-0[1-3]+ just imports base and set hostname and private link ip and deploy with nixos-anywhere deploy | 20:07:09 | |
| * is there any doc/blog comparing colmena vs deploy-rs right now i just keep things like ./hetzner-ex63-base ./hetzner-ex63-01 ./hetzner-ex63-02 ./hetzner-ex63-02 hetzner-ex63-0[1-3]+ just imports base and set hostname and private link ip and deploy with nixos-anywhere | 20:07:29 | |
| * is there any doc/blog comparing colmena vs deploy-rs right now i just keep things like ./hetzner-ex63-base ./hetzner-ex63-01 ./hetzner-ex63-02 ./hetzner-ex63-02 hetzner-ex63-0[1-3] just imports base and set hostname and private link ip and deploy with nixos-anywhere | 20:07:36 | |
| * is there any doc/blog comparing colmena vs deploy-rs right now i just keep things like ./hetzner-ex63-base ./hetzner-ex63-01 ./hetzner-ex63-02 ./hetzner-ex63-03 hetzner-ex63-0[1-3] just imports base and set hostname and private link ip and deploy with nixos-anywhere | 20:07:50 | |
| it would work the advantage for colmena vs deploy-rs is parallel eval/deployment and the downside ofc, is u dont have magic rollback | 20:17:42 | |
| feel like magick rollback should be a nixos (nixpkgs) feature like the activation script would start a systemd unit and listen for ssh connection, if anyone logs in successfully it's exits, otherwise it's rollbacked to previous version and there might be some post hook in colmena that we can use to automate the ssh login to deployed machine after switch | 20:23:57 | |
| * feel like magick rollback should be a nixos (nixpkgs) feature like the activation script would start a systemd unit and listen for ssh connection, if anyone logs in successfully it exits, otherwise it's rollbacked to previous version and there might be some post hook in colmena that we can use to automate the ssh login to deployed machine after switch | 20:24:12 | |
| * feel like magick rollback should be a nixos (nixpkgs) feature like the activation script would start a systemd unit and listen for ssh connection, if anyone logs in successfully it exits, otherwise machine is rollbacked to previous version and there might be some post hook in colmena that we can use to automate the ssh login to deployed machine after switch | 20:24:22 | |
im not aware of any | 20:25:33 | |
| tbh at this point the project hasnt seen any activity in more than 6mo i plan to fork it and just use it for myself | 20:26:24 | |
| colmena or deploy-rs | 20:27:17 | |
| colmena | 20:27:24 | |