| 27 Jul 2025 |
 Zhaofeng Li | ah, someone just got to it: https://github.com/zackify/cli.rs/issues/113 | 23:55:10 |
 invariance | Wow, they really did just get to it | 23:55:47 |
| invariance | thanks for clarifying; maybe remove the CNAME from github pages until it's back up, so it's accessible at https://zhaofengli.github.io/colmena? | 23:56:49 |
| 28 Jul 2025 |
| Zhaofeng Li | Oops sorry, got distracted. Sadly removing the CNAME file is dangerous and will enable another repository to take over colmena.cli.rs for their GitHub Pages. | 03:21:13 |
| Zhaofeng Li | (there was no way to configure domain verification due to how cli.rs is set up, and obviously it's too late for that now) | 03:21:46 |
| Zhaofeng Li | In the meantime, I've pushed the manual to https://stuff.naive.network/colmena-docs-f560ed6/ as a temporary measure | 03:23:15 |
 niklaskorz | In reply to @zhaofeng:zhaofeng.li
looks like it, the domain name seems to have expired 🙁 At least they have 30 days to fix it, according to rnids.rs | 07:36:30 |
| Zhaofeng Li | yeah, looks like they are active on github so hopefully it gets renewed soon | 07:37:54 |
| 30 Jul 2025 |
|  sinan joined the room. | 06:57:11 |
| sinan | hi, colmena.cli.rs is down | 06:57:39 |
| sinan | Zhaofeng Li: | 06:58:43 |
 Johann Wagner | It's known. | 06:58:51 |
| Johann Wagner | See literally 3 messages above you. | 06:59:04 |
| sinan | Oo, whre do i go for docs ? | 06:59:06 |
| Johann Wagner | https://stuff.naive.network/colmena-docs-f560ed6/ | 06:59:20 |
| Johann Wagner | As mentioned. | 06:59:22 |
| Johann Wagner | They are working on a fix. | 06:59:36 |
| sinan | colmena is still maintained right ?
i was using nixos-rebuild till now, this is my first intro into the nix ops tools
waited around a little bit for nixops4 but i don't think it will happen any time soon | 07:01:39 |
| Zhaofeng Li | yup, monitoring the situation (see https://github.com/zackify/cli.rs/issues/113 and https://github.com/zhaofengli/colmena/issues/304), if it doesn't get resolved in the next few days I'll consider moving to somewhere more reliable | 07:01:59 |
| Zhaofeng Li | (would suck as there would be dead links everywhere, but better than no docs at all) | 07:02:06 |
| Zhaofeng Li | a few high-profile projects also use the domain (rustic, kmon, pls) so... at least we aren't suffering alone 😐️ | 07:02:19 |
| sinan | damn | 07:03:13 |
|  @badele:matrix.org left the room. | 08:13:28 |
| 31 Jul 2025 |
|  sammy (It/Its) joined the room. | 09:37:13 |
|  @sammy:cherrykitten.dev left the room. | 09:37:56 |
| 2 Aug 2025 |
| sinan changed their profile picture. | 06:58:26 |
| sinan | 06:58:39 |
| sinan | 06:58:46 |
| 3 Aug 2025 |
|  zsuper joined the room. | 06:49:35 |
| zsuper | is the hardware-configuration.nix file's contents something that needs to be included in a node's modules? I know deploy-rs requires this, and it was recommended to me to have a node-specific folder of NixOS modules containing each host's hardware-configuration.nix. I can work with this approach, but it makes things a LOT more awkward because in order to generate that file, I must first have access to the target running NixOS | 07:00:11 |
