!zghijEASpYQWYFzriI:nixos.org

Hydra

344 Members
99 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
24 Jul 2025
@sandro:supersandro.deSandro 🐧That list at least put Samsung Mobile Browsers out because they are on Chromium 130 🙃23:13:55
@sandro:supersandro.deSandro 🐧If you open Developer Tools and choose Android, you get a Nexus with Android 623:14:37
@sandro:supersandro.deSandro 🐧Also I quickly found some friends which should have updated their Firefox more often23:14:55
25 Jul 2025
@luke:vuksta.comLuke joined the room.03:22:27
@luke:vuksta.comLuke

I posted this in the Terranix channel, but am hoping to get more eyes on it - sorry for double posting!

The high level idea I have is as follows:

  1. Orchestrator flake: sources all other flakes using input following. Hydra builds this flake, and some cron job regularly runs flake update to pick up new changes to all packages in the pipeline.
  2. Pipeline flake: a set of impure builds with a sequential dependency chain that are responsible for executing terraform plan and apply for each stage. These builds would use something like fixed output derivations with a fake hash to skirt network sandboxing. Integration tests would also be represented this way.
  3. Infrastructure flake: defines the terranix infrastructure, gets used by the various pipeline stages for deployment.
  4. Application flakes: flakes that define how to build and package application code, these get used by the infrastructure flake.

Then configure Hydra, and one machine should be able to act as a full devops pipeline?

This should let developers easily work on any subset of the system in a local workspace by modifying the flake inputs, as well as allowing things like manual deployments for rollbacks or emergency situations. There might be flaws with this idea, but I am curious to hear what folks think

03:24:57
@luke:vuksta.comLukeThis is for a declarative CI/CD deployment pipeline running from a single machine03:26:21
@hexa:lossy.networkhexa cleverca22, ma27, Sandro 🐧 we have moved to anubis since 12:47:44
@sandro:supersandro.deSandro 🐧I know12:48:02
@hexa:lossy.networkhexahttps://grafana.nixos.org/d/fejx5cl0i0s1sb/anubis?orgId=1&from=now-6d&to=now&timezone=utc&var-site=hydra.nixos.org:9001&viewPanel=panel-312:48:19
@sandro:supersandro.deSandro 🐧All those live sucking AI and SEO companies 😒12:48:59
@vuks:matrix.orgVuks joined the room.18:04:27
26 Jul 2025
@cleverca22:matrix.orgcleverca22i was considering doing that, got a link to how its all configured?01:45:12
@hexa:lossy.networkhexahttps://github.com/NixOS/infra/blob/main/build/hydra-proxy.nix#L1401:46:51
@hexa:lossy.networkhexawe currently have a map for some exceptions, but you likely don't need that01:47:12
@hexa:lossy.networkhexajust bypass the map and point the proxyPass directly at anubis01:47:23
@sandro:supersandro.deSandro 🐧I do proxy auth but that's more complicated11:46:58
@sandro:supersandro.deSandro 🐧And I also patch anubis to not lie about the http status code11:47:11

Show newer messages


Back to Room ListRoom Version: 6