Hydra | 383 Members | |
| 108 Servers |
| Sender | Message | Time |
|---|---|---|
| 27 Mar 2024 | ||
| 13:26:01 | ||
| 30 Mar 2024 | ||
| i seem to be having issues with hydra not serving static files
this is from a nginx remote proxy, in the browser the page just times out | 20:30:19 | |
| hydra itself doesnt log anything, im also not running this on nixos, but the module was copied from nixos mostly | 20:32:00 | |
| i dont see why it would be failing the serve | 21:11:17 | |
| interestingly reloading the page doesnt mark them ass missing? hydra isnt closing connections properly? | 21:22:57 | |
| * interestingly reloading the page doesnt mark them as missing? hydra isnt closing connections properly? | 21:23:44 | |
| i also got to do something to speed up the DB because clicking on one of my systems takes 20 seconds to load, its 6.5k store paths | 21:26:28 | |
| * i also got to do something to speed up the DB because clicking on one of my systems takes 20 seconds to load, its 6.5k build steps | 21:27:24 | |
| 31 Mar 2024 | ||
| 00:05:01 | ||
| 2 Apr 2024 | ||
| 06:58:30 | ||
| 07:36:25 | ||
| 3 Apr 2024 | ||
| Managed to fix a ca-derivations issue with hydra: https://github.com/NixOS/hydra/pull/1374 | 21:08:45 | |
| 4 Apr 2024 | ||
| 06:09:42 | ||
| 08:40:33 | ||
| How feasible would it be to run Hydra as a distributed system? Say I had a few dozen or maybe even a hundred or more thin clients (ARM or RISC-V or whatever). Is it theoretically possible for Hydra to be distributed among those clients (assuming they're all on the same overarching network, of course) so none of them is doing much work or for long, but the whole thing is entirely bootstrapped (reminiscent of IPFS)? And because this is distributed across an entire fleet, you can do some crazy Gentoo-level optimization... the prospect is very exciting indeed. | 08:56:09 | |