Hydra | 384 Members | |
| 109 Servers |
| Sender | Message | Time |
|---|---|---|
| 29 Jun 2023 | ||
| I'm not sure if there is anything. But splitting a single derivation into multiple would work everywhere. I'm not entirely sure why Nixpkgs errs on the side of more monolithic derivations. | 12:32:29 | |
| if you were super big on always adding gcroots, you could add a postbuildhook that would add a root for every build you had.
| 15:48:02 | |
| that's a nix postbuildhook, apart from hydra. | 15:48:15 | |
| 30 Jun 2023 | ||
| I would need to clean them up manually, right? | 01:48:04 | |
| 14:22:47 | ||
| 1 Jul 2023 | ||
| 09:47:24 | ||
| 3 Jul 2023 | ||
| 18:01:50 | ||
| 4 Jul 2023 | ||
| 14:26:16 | ||
| 5 Jul 2023 | ||
| 14:20:06 | ||
| 18:19:58 | ||
| 6 Jul 2023 | ||
| 20:16:47 | ||
| 7 Jul 2023 | ||
| 05:36:35 | ||
| 8 Jul 2023 | ||
| 13:59:18 | ||
| 16:30:14 | ||
| 9 Jul 2023 | ||
| 10:53:38 | ||
Hi all, I am trying to make a declarative project. I am trying to wrap my head around the declInput argument. Why do so many projects cat it? | 10:57:41 | |
| 10 Jul 2023 | ||
In reply to @hacker1024:matrix.orgDepends on what your declInput is. For me it's usually a git repo so it's not cat-table | 06:58:58 | |
| declInput is what you configure in the "Declarative input type" in the project settings | 06:59:27 | |
| Thanks. But what is the purpose of printing it at build time? Take [this one](https://github.com/dhess/pinpon/tree/f4f984f3a45e4239914c912f489fd37110b65d45/nix/jobsets), for example - the input in spec.json is just the repository. | 07:25:21 | |
In reply to @hacker1024:matrix.orgI guess debug things | 08:16:21 | |
| Btw if you try hard enough, you don't even need nixpkgs in your declarative spec: https://git.helsinki.tools/helsinki-systems/hydra-nixos/-/blob/master/default.nix#L44 | 08:18:02 | |
| * Btw if you try hard enough, you don't even need nixpkgs in your declarative spec: https://git.helsinki.tools/helsinki-systems/hydra-nixos/-/blob/master/default.nix#L44 - makes it nicer imo because you don't have to fetch/update nixpkgs every time | 08:18:34 | |
| Thanks, that's pretty cool. Another question: Does Hydra have a way to limit all access to logged in users, or do I need to set up a reverse proxy with authentication? In particular I do not want anyone to be able to view output hashes or access our binary cache. | 23:17:17 | |
| * Thanks, that's pretty cool. Another question: Does Hydra have a way to limit all access to logged in users, or do I need to set up a reverse proxy with authentication? In particular I do not want anyone to be able to view build logs or output hashes or access our binary cache. | 23:17:38 | |
| * Thanks, that's pretty cool. Another question: Does Hydra have a way to limit all access to logged in users, or do I need to set up a reverse proxy with authentication? In particular I do not want anyone to be able to view build logs or output hashes, or access our binary cache. | 23:17:44 | |
| 11 Jul 2023 | ||
| How can I stop Hydra from serving my whole system Nix store as a binary cache? I have the following line in my config, but it seems to have no effect at all.
| 13:25:53 | |
| I think the answer to both those questions is using a reverse proxy in front of it | 13:44:32 | |
| I've got Caddy set up doing basic auth, but I don't see how I could use that to only serve the specific derivations I'm building in Hydra (excluding other things I have installed in my system)? | 13:45:47 | |
| ah, I assumed you'd just want to block access to the binary-cache altogether | 13:47:24 | |
| Actually, upon futher inspection, I think I can see why my
I don't understand why this is happening, though - | 13:48:16 | |