M5 Doku: Gitea-1.27.2-Inventar, CT-116-Runner, gruene statische CI in GNAI-008 Abschnitt 12
ci-static / secret-scan (push) Successful in 21s
ci-static / yamllint (push) Successful in 30s
ci-static / ansible-syntax (push) Successful in 28s
ci-static / markdown-links (push) Successful in 21s
ci-static / secret-scan (pull_request) Successful in 21s
ci-static / yamllint (pull_request) Successful in 30s
ci-static / ansible-syntax (pull_request) Successful in 27s
ci-static / markdown-links (pull_request) Successful in 21s
ci-static / secret-scan (push) Successful in 21s
ci-static / yamllint (push) Successful in 30s
ci-static / ansible-syntax (push) Successful in 28s
ci-static / markdown-links (push) Successful in 21s
ci-static / secret-scan (pull_request) Successful in 21s
ci-static / yamllint (pull_request) Successful in 30s
ci-static / ansible-syntax (pull_request) Successful in 27s
ci-static / markdown-links (pull_request) Successful in 21s
Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
This commit is contained in:
@@ -761,6 +761,30 @@ Zustandsdatei und Recovery-Timer (Abschnitt 14.6, T1–T7 bestanden; nach
|
||||
Host-Neustart am 09.11.2026 automatisches Recovery auf Production verifiziert).
|
||||
Frage 5 bleibt bis zur Delivery-Kette (Gitea Actions, Meilenstein 5) offen.
|
||||
|
||||
**M5-Fortschritt 10.11.2026 (Fragen 1 und 2 teilweise beantwortet):**
|
||||
- **Gitea live (CT 110, `git.ghostnet.selfhost.eu`):** Version 1.27.2 (go1.26.5),
|
||||
`ROOT_URL http://10.0.0.17:3000/` hinter NPM, `DISABLE_REGISTRATION=true`,
|
||||
Actions-API aktiv (`has_actions=true` für `ghostnet.ai/infrastructure`),
|
||||
bisher 0 Runner, 0 Branch-/Tag-Protection, 7 Repos. Registrierungs-Endpunkt
|
||||
in 1.27.2: `POST /api/v1/repos/{owner}/{repo}/actions/runners/registration-token`.
|
||||
- **Statische CI ohne Serverzugang eingeführt:** `.gitea/workflows/ci-static.yml`
|
||||
(Jobs `secret-scan`, `yamllint`, `ansible-syntax`, `markdown-links`; Job-Image
|
||||
`node:22-trixie` per Digest gepinnt, `actions/checkout@v4`, ansible-core und
|
||||
yamllint per `ci/requirements-ci.txt` gepinnt; Skripte unter `scripts/ci/`).
|
||||
Erster Lauf auf Branch `ci/static-ci` am 10.11.2026 grün (alle 4 Jobs
|
||||
`success`); zwei gebrochene Doku-Links dabei gefunden und gefixt.
|
||||
- **Runner:** dedizierter LXC **CT 116** (`runner`, `10.0.0.60/24`, unprivileged,
|
||||
nesting=1), `act_runner v0.2.13` (SHA-256
|
||||
`3acac8b506ac8cadc88a55155b5d6378f0fab0b8f62d1e0c0450f4ccd69733e2`), Podman 5.4.2
|
||||
rootful mit Socket als Docker-API (`docker_host=unix:///run/podman/podman.sock`),
|
||||
systemd-Unit `act-runner.service`, repo-scoped Runner `ci-static-01` online
|
||||
(Labels `ubuntu-latest`/`ubuntu-22.04`/`ubuntu-20.04`; Jobs laufen in
|
||||
gepinnten Job-Containern). Der Runner-LXC besitzt keine Server-Zugangsdaten.
|
||||
- Branch-Protection `main` (PR-Pflicht + required status check `ci-static`,
|
||||
1 Approver, kein Direkt-Push) wird mit dem Merge des CI-Branches gesetzt.
|
||||
- Offen: Fragen 3–5 (Review-/Freigabe-Rechte, Secret-Store, Promotion-Tag),
|
||||
privilegierter Deployment-Runner, Secret-Scan über die Git-Historie.
|
||||
|
||||
---
|
||||
|
||||
## 13. Referenzstand der Planung
|
||||
|
||||
Reference in New Issue
Block a user