chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata
This commit is contained in:
parent
7922475ecc
commit
daeae0f868
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Frontend-Architektur & Modularisierungsstrategie
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,8 @@
|
|||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
status: ARCHIVED
|
||||
owner: Lead Architect
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Repository-Architektur (MP-22)
|
||||
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
type: Roadmap
|
||||
status: ACTIVE
|
||||
status: ARCHIVED
|
||||
owner: Lead Architect
|
||||
last_update: 2026-03-09 (Ping Service Tracer Bullet abgeschlossen)
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# MASTER ROADMAP Q1 2026: "Operation Tracer Bullet"
|
||||
|
|
@ -3,6 +3,7 @@ type: Guide
|
|||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
tags: [coding-style, kdoc, documentation]
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# KDoc-Styleguide (Kurzfassung)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: Frontend Expert
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# SQLDelight-Integration in Compose Multiplatform
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: Frontend Expert
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Architekturstrategien für Asynchrone Persistenz in Kotlin Multiplatform: Eine umfassende Analyse zur Integration von SQLDelight in Web-Umgebungen
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Glossar der Domäne "Meldestelle"
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ type: Guide
|
|||
status: DRAFT
|
||||
owner: Backend Developer
|
||||
date: 2026-02-02
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# Database Best Practices & Exposed 1.0.0
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ type: Guide
|
|||
status: ACTIVE
|
||||
owner: Backend Developer
|
||||
tags: [testing, postman, backend, api]
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# 🧪 Testanleitung: Ping-Service & Gateway mit Postman
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Backend Developer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Backend Dokumentation
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ type: Reference
|
|||
status: ACTIVE
|
||||
owner: Backend Developer
|
||||
tags: [backend, service, reference, ping]
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# 🎯 Ping Service Reference
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
type: Task
|
||||
status: DONE
|
||||
status: ARCHIVED
|
||||
owner: Senior Backend Developer
|
||||
created: 2026-01-15
|
||||
completed: 2026-01-16
|
||||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Frontend Expert
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Offline-First-Architektur
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: Frontend Expert
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Web-Setup (Webpack & Worker)
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Heimnetzwerk
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Konfigurations-Matrix
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
## 🛡️ Pangolin vs. Cloudflare Tunnel
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ status: ACTIVE
|
|||
review_cycle: 180d
|
||||
last_reviewed: 2025-10-31
|
||||
summary: "Übersicht der wichtigsten lokalen URLs und Ports. Quelle: docker-compose.yaml + config/env"
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# Referenz: Wichtige URLs und Ports (lokal)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Zipkin Tracing
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# Roadmap: Zora Infrastructure & Deployment (Februar 2026)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
## 🏗️ System-Architektur "Zora" (ARM64)
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ type: Guide
|
|||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
tags: [jwt, oidc, keycloak, docker, networking, security]
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# Leitfaden: JWT-Validierung in der Docker-Umgebung
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Runbook: Lokale Entwicklungsumgebung
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
type: Journal
|
||||
status: COMPLETED
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
date: 2026-01-30
|
||||
participants:
|
||||
- Lead Architect
|
||||
last_update: 2026-01-30
|
||||
---
|
||||
|
||||
# Session Log: 30. Jänner 2026 - Refactoring Exposed & Ktor
|
||||
|
|
|
|||
|
|
@ -1,11 +1,12 @@
|
|||
---
|
||||
type: Journal
|
||||
status: COMPLETED
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
date: 2026-01-31
|
||||
participants:
|
||||
- Lead Architect
|
||||
- DevOps Engineer
|
||||
last_update: 2026-01-31
|
||||
---
|
||||
|
||||
# Session Log: 31. Jänner 2026 – E2E Smoke (Exposed 1.0.0, Ktor 3.4.0)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-02-03
|
||||
---
|
||||
# Session Log: Diagnose Docker Build Issues (IsolatedKotlinClasspathClassCastException)
|
||||
|
||||
**Datum:** 03.02.2026
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-02-03
|
||||
---
|
||||
# 🧹 Session Log: Gradle Build-Optimierung & Refactoring
|
||||
|
||||
**Datum:** 03.02.2026
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-02-04
|
||||
---
|
||||
# 🏗️ Journal: Infrastructure Setup & CI/CD Planning
|
||||
|
||||
**Datum:** 04.02.2026
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-02-04
|
||||
---
|
||||
# 🏗️ Journal: Ping Service Verification
|
||||
|
||||
**Datum:** 04.02.2026
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-02-06
|
||||
---
|
||||
# Session Log: Infrastructure Planning & Reporting Requirements
|
||||
|
||||
**Datum:** 06.02.2026
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-02-13
|
||||
---
|
||||
# Journal - 2026-02-13
|
||||
|
||||
## 📝 Zusammenfassung
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
# Journal - 2026-03-06 (Session 2)
|
||||
|
||||
## 📝 Zusammenfassung
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ status: ACTIVE
|
|||
owner: Curator
|
||||
date: 2026-03-06
|
||||
session: Immich & Pangolin — Konfiguration dokumentiert
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
|
||||
# Session Log — 2026-03-06: Immich & Pangolin Konfiguration
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
# Journal - 2026-03-06
|
||||
|
||||
## 📝 Zusammenfassung
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
type: JOURNAL
|
||||
status: DONE
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: DevOps
|
||||
date: 2026-03-06
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
|
||||
# Session Log — Pipeline 502 Bad Gateway Fix
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
type: journal
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
date: 2026-03-06
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
|
||||
# Session Log — Pipeline Fix v2: connection refused Port 443
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
type: journal
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
date: 2026-03-06
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
|
||||
# Session Log — Pipeline Fix v3: socat nicht verfügbar → iptables DNAT
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
type: journal
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
date: 2026-03-06
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
|
||||
# Session Log — Pipeline vollständig grün ✅
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
# Journal - 2026-03-06 (Session 3 — Proxmox-Korrektur)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: FINAL
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
date: 2026-03-06
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
# Session Log – Übersetzung aller Dokumente auf Deutsch
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
type: Session Log
|
||||
type: Journal
|
||||
date: 2026-03-06
|
||||
agent: DevOps Engineer + Curator
|
||||
status: DONE
|
||||
status: ACTIVE
|
||||
last_update: 2026-03-06
|
||||
---
|
||||
# Session Log: Zora — Vollständige Konfigurationsanalyse
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: DONE
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
date: 2026-03-07
|
||||
last_update: 2026-03-07
|
||||
---
|
||||
# Session Log — Tech-Stack Zusammenfassung
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ type: Journal
|
|||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
date: 2026-03-07
|
||||
last_update: 2026-03-07
|
||||
---
|
||||
# Session Log — 07. März 2026: Zora Hardware-Zusammenfassung
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-03-09
|
||||
---
|
||||
# Journal - 2026-03-09
|
||||
|
||||
## 📝 Zusammenfassung
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-03-10
|
||||
---
|
||||
# Session Log — 2026-03-10: Keycloak Hostname Fix, Git Push Analyse & DOCKER_REGISTRY Fix
|
||||
|
||||
**Datum:** Di. 10. März 2026
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-03-11
|
||||
---
|
||||
# Session Log: Pangolin Update & Meldestelle Configuration
|
||||
|
||||
**Datum:** 11. März 2026
|
||||
|
|
|
|||
|
|
@ -0,0 +1,86 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
|
||||
# 🧹 Session Log: Dokumentation Cleanup & Normalisierung
|
||||
|
||||
**Datum:** 15. März 2026
|
||||
**Agent:** 🧹 Curator
|
||||
**Kontext:** Vollständige Bereinigung, Korrektur und Optimierung der `docs/`-Struktur.
|
||||
|
||||
---
|
||||
|
||||
## 📝 Zusammenfassung
|
||||
|
||||
Umfassende Aufräum-Session der gesamten Dokumentation. Veraltete Dokumente wurden archiviert, fehlende Standard-Header ergänzt, inkonsistente Frontmatter-Werte normalisiert und temporäre Dateien entfernt.
|
||||
|
||||
---
|
||||
|
||||
## 🗂️ Archivierungen
|
||||
|
||||
| Originaldatei | Archivpfad | Grund |
|
||||
|---|---|---|
|
||||
| `docs/01_Architecture/ARCHITECTURE.md` | `docs/01_Architecture/_archive/2026-03-15_ARCHITECTURE.md` | Selbst als veraltet markiert (Jan 2026), kein aktiver Inhalt mehr |
|
||||
| `docs/01_Architecture/MASTER_ROADMAP_2026_Q1.md` | `docs/01_Architecture/_archive/2026-03-15_MASTER_ROADMAP_2026_Q1.md` | Alle Phasen der "Operation Tracer Bullet" abgeschlossen |
|
||||
| `docs/05_Backend/TASK_2026_Q1_Infrastructure_Hardening.md` | `docs/05_Backend/_archive/2026-03-15_TASK_2026_Q1_Infrastructure_Hardening.md` | Status war DONE, erledigte Task-Dokumente gehören ins Archiv |
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ Korrekturen
|
||||
|
||||
### `last_update`-Feld ergänzt (19 Dokumente)
|
||||
Folgende aktive Dokumente hatten kein `last_update`-Feld im Frontmatter:
|
||||
|
||||
- `docs/05_Backend/Services/PingService_Reference.md`
|
||||
- `docs/05_Backend/README.md`
|
||||
- `docs/05_Backend/Guides/Database_Best_Practices.md`
|
||||
- `docs/05_Backend/Guides/Testing_with_Postman.md`
|
||||
- `docs/06_Frontend/offline-first-architecture.md`
|
||||
- `docs/06_Frontend/web-setup.md`
|
||||
- `docs/07_Infrastructure/Heim-Netzwerk-Plan_02-2026.md`
|
||||
- `docs/07_Infrastructure/Konfig-Matrix_Dev-ProZora.md`
|
||||
- `docs/07_Infrastructure/Pangolin-vs-Cloudflare-Tunnel.md`
|
||||
- `docs/07_Infrastructure/Reference/ports-and-urls.md`
|
||||
- `docs/07_Infrastructure/Reference/zipkin.md`
|
||||
- `docs/07_Infrastructure/Zora_Infrastructure_Deployment_02-2026.md`
|
||||
- `docs/07_Infrastructure/Zora_System_Architektur.md`
|
||||
- `docs/07_Infrastructure/guides/jwt-in-docker.md`
|
||||
- `docs/07_Infrastructure/runbooks/local-development.md`
|
||||
- `docs/03_Domain/00_Glossary.md`
|
||||
- `docs/02_Guides/SQLDelight_Integration_Compose_Multiplatform.md`
|
||||
- `docs/02_Guides/SQLDelight_Web_Asynchron.md`
|
||||
- `docs/02_Guides/CodingGuidelines/kdoc-style.md`
|
||||
|
||||
### Journal-Header normalisiert (25 Einträge)
|
||||
- **Header hinzugefügt** (fehlten komplett): 11 Einträge (u.a. `2026-02-03_*`, `2026-02-04_*`, `2026-03-09_*`, `2026-03-10_*`, `2026-03-11_*`)
|
||||
- **Inkonsistente Werte korrigiert** (14 Einträge):
|
||||
- `type`: `journal` → `Journal`, `JOURNAL` → `Journal`, `Session Log` → `Journal`
|
||||
- `status`: `COMPLETED` → `ACTIVE`, `DONE` → `ACTIVE`, `FINAL` → `ACTIVE`, `In Progress` → `ACTIVE`
|
||||
- `last_update` aus Dateiname ergänzt wo fehlend
|
||||
|
||||
### Temporäre Dateien gelöscht
|
||||
- `docs/Bin/Temp.md` — leere Temp-Datei ohne Inhalt
|
||||
|
||||
---
|
||||
|
||||
## ✅ Quality Gate Status
|
||||
|
||||
| Prüfpunkt | Status |
|
||||
|---|---|
|
||||
| Alle aktiven Docs haben Standard-Header | ✅ |
|
||||
| `last_update` in allen aktiven Docs | ✅ |
|
||||
| `type`-Werte konsistent (Journal/Reference/Guide/ADR/Report/Roadmap) | ✅ |
|
||||
| `status`-Werte konsistent (DRAFT/ACTIVE/DEPRECATED/ARCHIVED) | ✅ |
|
||||
| Veraltete Dokumente archiviert | ✅ |
|
||||
| Temporäre Dateien entfernt | ✅ |
|
||||
|
||||
---
|
||||
|
||||
## 🔗 Offene Punkte / Empfehlungen
|
||||
|
||||
- **Domain-Analyse-Docs** (`docs/03_Domain/03_Analysis/`) haben noch kein `last_update` — diese sind DRAFT und sollten beim nächsten Domain-Workshop aktualisiert werden.
|
||||
- **`docs/06_Frontend/Logs/`** — zwei Docker-Build-Troubleshooting-Logs ohne `last_update`; da reine Logs, niedrige Priorität.
|
||||
- **ADR-Pflicht prüfen:** Die Entscheidung für den AI-Stack (Ollama + Open WebUI, Session 2026-03-06) ist bisher nur im Journal dokumentiert — ein ADR in `docs/01_Architecture/adr/` wäre angebracht.
|
||||
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
last_update: 2026-03-15
|
||||
---
|
||||
# Journal
|
||||
|
||||
Kurze Session-Protokolle, damit Entscheidungen/Erkenntnisse nicht „im Chat“ verloren gehen.
|
||||
|
|
|
|||
|
|
@ -1,87 +0,0 @@
|
|||
# **„Hello-World“-Testprojekt**
|
||||
|
||||
Bevor das **"Meldestelle"-Projekt** auf **Zora** losgelassen wird, erstellen wir ein **"Hallo Welt"-Projekt**. Das spart Zeit beim Debugging, wenn der Test-Build fehlschlägt, wissen wir sofort, es liegt an der Infrastruktur (Runner/Registry) und nicht an komplexen Gradle-Abhängigkeiten.
|
||||
|
||||
## Plan für "Sandbox-Projekt“, um die CI/CD-Leitung auf **Zora** zu testen.
|
||||
|
||||
---
|
||||
|
||||
### 1. Runner-Stabilisierung: Der „Herz-Check“
|
||||
|
||||
Bevor das Testprojekt gepusht wird, müssen wir sicherstellen, dass der Runner nicht nur „jetzt“ online war, sondern als stabiler Dienst im Hintergrund läuft.
|
||||
|
||||
**Checke das im Container `infra-runner`:**
|
||||
|
||||
```bash
|
||||
incus exec infra-runner -- systemctl status act_runner
|
||||
|
||||
```
|
||||
|
||||
* **Wenn „active (running)“:** Alles bestens.
|
||||
* **Falls nicht:** Starte ihn mit `systemctl enable --now act_runner`.
|
||||
* **Gitea-Check:** Im Browser sollte der Status jetzt von **Inaktiv** (Grau/Gelb) auf **Aktiv** (Grün) springen, sobald der Dienst läuft.
|
||||
|
||||
---
|
||||
|
||||
### 2. Das Test-Projekt: „Zora-Proof-of-Concept“
|
||||
|
||||
Erstelle in deiner IDEA (oder direkt in Gitea) ein neues, leeres Repository namens `zora-test`.
|
||||
|
||||
#### A. Die minimale Dockerfile
|
||||
|
||||
Wir nehmen ein extrem kleines Image, um die ARM64-Fähigkeit zu testen:
|
||||
|
||||
```dockerfile
|
||||
FROM alpine:latest
|
||||
RUN echo "Zora hat dieses Image gebaut!" > /hello.txt
|
||||
CMD ["cat", "/hello.txt"]
|
||||
|
||||
```
|
||||
|
||||
#### B. Der Workflow (`.gitea/workflows/test.yaml`)
|
||||
|
||||
Hier nutzen wir deine neuen Secrets `REGISTRY_TOKEN` und `REGISTRY_USER`.
|
||||
|
||||
```yaml
|
||||
name: Zora Test Build
|
||||
on: [push]
|
||||
jobs:
|
||||
build-and-push:
|
||||
runs-on: ubuntu-latest # Dein Runner erkennt das Label
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: Login to Registry
|
||||
uses: docker/login-action@v3
|
||||
with:
|
||||
registry: git.mo-code.at
|
||||
username: ${{ secrets.REGISTRY_USER }}
|
||||
password: ${{ secrets.REGISTRY_TOKEN }}
|
||||
|
||||
- name: Build and Push
|
||||
uses: docker/build-push-action@v5
|
||||
with:
|
||||
context: .
|
||||
push: true
|
||||
tags: git.mo-code.at/${{ secrets.REGISTRY_USER }}/zora-test:latest
|
||||
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### 3. Warum dieser Test so wertvoll ist
|
||||
|
||||
1. **Registry-Rechte:** Wir prüfen, ob dein neuer Token wirklich Pakete schreiben darf.
|
||||
2. **LXC-Docker-Check:** Wir sehen, ob Docker im Container `infra-runner` mit dem `fuse-overlayfs` Treiber wirklich Images bauen kann.
|
||||
3. **ARM64-Verifizierung:** Wir bestätigen, dass der Runner das Image nativ für dein Biest baut.
|
||||
|
||||
---
|
||||
|
||||
### Was wir kontrollieren müssen (Erfolgskriterien):
|
||||
|
||||
* [ ] Erscheint in Gitea unter dem Reiter **„Actions“** ein neuer Eintrag nach dem Push?
|
||||
* [ ] Läuft der Build ohne Fehler durch?
|
||||
* [ ] Taucht unter deinem Profil in Gitea ein neues **„Paket“** namens `zora-test` auf?
|
||||
|
||||
**Soll ich dir, sobald du das Testprojekt in Gitea angelegt hast, helfen das Log-Streaming des Runners zu analysieren, falls er beim `docker login` hängen bleibt?** (Das ist oft die Stelle, an der falsche Secret-Namen auffallen).
|
||||
Loading…
Reference in New Issue
Block a user