From 5bf755960d7ed21ef7ac97535030973469323543 Mon Sep 17 00:00:00 2001 From: NotAShelf Date: Sat, 28 Feb 2026 13:04:56 +0300 Subject: [PATCH] docs: clarify hydra components in design document Signed-off-by: NotAShelf Change-Id: I56a1dee4df5e3898aa7ef6e24ed7342c6a6a6964 --- docs/DESIGN.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/DESIGN.md b/docs/DESIGN.md index 517bf82..fd94589 100644 --- a/docs/DESIGN.md +++ b/docs/DESIGN.md @@ -46,3 +46,10 @@ Hydra follows a tightly-coupled architecture with three main daemons: ```plaintext Git Repository -> Evaluator -> Database -> Queue Runner -> Build Hosts -> Results -> Database - Web UI ``` + +1. **hydra-server** (Perl/Catalyst): Web interface and REST API +2. **hydra-evaluator**: Polls Git repos, evaluates Nix expressions, creates + `.drv` files +3. **hydra-queue-runner**: Dispatches builds to available builders via SSH/Nix + remote +4. **Database (PostgreSQL)**: Central state management for all components