In reply to @darkwater4213:matrix.org
For RISC-V? Does the main instance of Hydra compile for RISC-V?

In reply to @darkwater4213:matrix.org
How feasible is self-hosting a Hydra instance? Say I want to deploy to a whole bunch of RISC-V thin clients... I already know what packages I want to be compiled, so is there a way to configure Hydra to only build and serve those? Or am I fundamentally messengering something about Hydra?

i seem to be having issues with hydra not serving static files

4#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/js/jquery/jquery-ui-1.10.4.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/jquery/jquery-ui-1.10.4.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client:, server: hydra.redalder.org, request: "GET /static/js/moment/moment-2.24.0.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/moment/moment-2.24.0.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/fontawesome/css/all.css HTTP/2.0", upstream: "http://127.0.0.1:8666/static/fontawesome/css/all.css", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/js/popper.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/popper.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/css/tree.css HTTP/2.0", upstream: "http://127.0.0.1:8666/static/css/tree.css", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/images/emojione-check-2714.svg HTTP/2.0", upstream: "http://127.0.0.1:8666/static/images/emojione-check-2714.svg", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:33 [warn] 125

this is from a nginx remote proxy, in the browser the page just times out

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.