recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(flake): make Hetzner the canonical cc-ci host target
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-06-01 13:57:45 +00:00
parent 7225138f30
commit be4f451d3a
4 changed files with 33 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/architecture.md
View File

@ -5,11 +5,16 @@ reports the result back. Everything on the `cc-ci` host is declared in this repo
## Repo layout
All Nix code lives under **`nix/`** — `nix/hosts/cc-ci/` (the machine config) and `nix/modules/`
(the service modules). `flake.nix` / `flake.lock` stay at the **repo root** as the entry point, so
the build reference is unchanged (`nixos-rebuild switch --flake '…#cc-ci'`). Application source sits
at the root (`bridge/`, `dashboard/`, `runner/`, `tests/`); encrypted secrets are the `secrets/`
submodule.
All Nix code lives under **`nix/`** — `nix/hosts/cc-ci-hetzner/` (the live machine config),
`nix/hosts/cc-ci/` (the legacy Incus config), and `nix/modules/` (the service modules).
`flake.nix` / `flake.lock` stay at the **repo root** as the entry point. Host targets:
- `#cc-ci` = live Hetzner host
- `#cc-ci-hetzner` = explicit alias for the same live Hetzner host
- `#cc-ci-incus` = legacy Incus VM config only
Application source sits at the root (`bridge/`, `dashboard/`, `runner/`, `tests/`); encrypted secrets
are the `secrets/` submodule.
## Components