infra: clean up Keycloak configuration, enforce consistency in .env, and improve health checks
Streamlined Keycloak configurations with defaults for development and production in `.env`. Added health checks and improved environment variable documentation with comments to differentiate local and server deployments. Ensured compatibility with pre-built registry images.
This commit is contained in:
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# Frontend Architecture & Modularization Strategy
|
||||
|
||||
**Status:** DRAFT
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# Architektur: Das Platform-Modul
|
||||
|
||||
## Überblick
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# Repository-Architektur (MP-22)
|
||||
|
||||
**WARNUNG (Januar 2026): Dieses Dokument ist veraltet.** Die hier beschriebene "Soll"-Struktur wurde teilweise umgesetzt, aber wichtige strategische Änderungen sind in den Statusberichten vom Januar 2026 dokumentiert. Dieses Dokument dient nur noch als historischer Referenzpunkt.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# Open-Source-Konformität & Lizenz-Checkliste
|
||||
|
||||
Dieses Dokument dient der Überwachung und Sicherstellung der Open-Source-Konformität des Projekts **Meldestelle**. Es wird vom Lead Architect gepflegt.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# Enable Gitea Actions Cache to Accelerate CI/CD
|
||||
|
||||
[Gitea](/)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# 💻 Client-Setup: Arbeitsplatz an "Das Biest" anbinden
|
||||
|
||||
Diese Anleitung beschreibt die Einrichtung eines lokalen Rechners, um via SSH und Cloudflare-Tunnel auf die
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# Technisches Referenzhandbuch: MS-R1 "Das Biest"
|
||||
|
||||
## 1. System-Übersicht & Architektur
|
||||
|
||||
+3
-1
@@ -1,5 +1,7 @@
|
||||
---
|
||||
Betriebsanleitung Minisforum MS-R1
|
||||
type: Reference
|
||||
status: ARCHIVED
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
|
||||
# MINISFORUM MS-R1
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# SSoT Konfigurations-Masterplan für Zora (ARM64)
|
||||
|
||||
## 1. System-Umgebung (Infrastruktur)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# Setup Guide: Host OS (Minisforum MS-R1)
|
||||
|
||||
**Status:** DEPRECATED / HISTORIC
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Guide
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# Setup Guide: Infrastructure Services (Minisforum MS-R1)
|
||||
|
||||
**Status:** DEPRECATED / HISTORIC
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# Spezifikation
|
||||
|
||||
| CPU | CP8180, 12 Cores/12 Threads, 2.6Ghz |
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# Dokumentation: Zentrales Mail-Relay (SSoT) auf Zora
|
||||
|
||||
## 1. Identität & Rollenverteilung
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# Roadmap: Finalisierung Gitea-Infrastruktur (MS-R1)
|
||||
|
||||
## Phase 1: Konnektivität & Erreichbarkeit 🌐
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
Hier ist der Quellcode des Berichts im Markdown-Format:
|
||||
|
||||
# Architektonische Resilienz in verteilten Systemen: Ein umfassender Leitfaden zur Implementierung von Offline-First Kotlin Multiplatform Architekturen mit SQLDelight
|
||||
|
||||
@@ -1,5 +1,7 @@
|
||||
---
|
||||
Datenblatt USV
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: DevOps Engineer
|
||||
---
|
||||
# Eaton 3S
|
||||
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: DRAFT
|
||||
owner: Lead Architect
|
||||
---
|
||||
# PENDING DECISIONS: Backend Infrastructure & Architecture
|
||||
|
||||
**Status:** RESOLVED
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0000: Vorlage für Architekturentscheidungsaufzeichnungen
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0001: Modulare Architektur
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0002: Domain-Driven Design
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0003: Microservices-Architektur
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0004: Ereignisgesteuerte Kommunikation
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0005: Polyglotte Persistenz
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0006: Authentifizierung und Autorisierung mit Keycloak
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0007: API-Gateway-Muster
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0008: Multiplatform-Client-Anwendungen
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0009: Final KMP Architecture
|
||||
|
||||
Status: Accepted
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR 001: Backend Infrastructure & Architecture Decisions
|
||||
|
||||
**Status:** ACCEPTED
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0010: SQLDelight für Cross-Platform-Persistenz
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0011: Koin für Dependency Injection
|
||||
|
||||
## Status
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: ADR
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
# ADR-0012: Strukturierung der Domänen-Dokumentation
|
||||
|
||||
* **Status:** Accepted
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
type: Reference
|
||||
status: ACTIVE
|
||||
owner: Lead Architect
|
||||
---
|
||||
Architecture Decision Records (ADRs)
|
||||
|
||||
Dieses Verzeichnis enthält Architekturentscheidungen in kurzer, überprüfbarer Form.
|
||||
|
||||
Reference in New Issue
Block a user