mocode-software/meldestelle
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore(docs+infra): add hardware setup logs, guidelines, and Minisforum MS-R1 documentation

Browse Source 
- Updated `MASTER_ROADMAP_2026_Q1.md` to reflect delivery of Minisforum MS-R1 hardware and progress on infrastructure setup.
- Added detailed documentation for Minisforum MS-R1, including specifications, host OS setup guide, and service configuration guide.
- Logged DevOps setup session and curator's session with focus on hardware integration, SSH hardening, and networking adjustments (Macvlan workaround).
- Included user manual for Minisforum MS-R1 and related assets (e.g., images).
This commit is contained in:
Stefan Mogeritsch
2026-02-08 01:25:47 +01:00
parent bc093ba3ff
commit c50acd641e
51 changed files with 1181820 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/01_Architecture/MASTER_ROADMAP_2026_Q1.md
+4 -3
View File
@@ -2,7 +2,7 @@
type: Roadmap
status: ACTIVE
owner: Lead Architect
last_update: 2026-02-06
last_update: 2026-02-07
---
# MASTER ROADMAP Q1 2026: "Operation Tracer Bullet"
@@ -10,11 +10,12 @@ last_update: 2026-02-06
**Strategisches Ziel:**
Wir validieren die gesamte Architektur-Kette (Frontend -> Gateway -> Service -> DB) anhand des **Ping-Service**. Dieser Service dient als **technischer Blueprint** (Vorlage) für alle kommenden Fach-Services. Er muss "Production Ready" gehärtet sein, bevor wir Fachlichkeit implementieren.
**Aktueller technischer Stand (06.02.2026):**
**Aktueller technischer Stand (07.02.2026):**
* Build System: ✅ Grün (Gradle, Kotlin 2.3, Spring Boot 3.5.9, Spring Cloud 2025.0.1).
* Code-Basis: ✅ `ping-service` existiert, Delta-Sync implementiert.
* Infrastruktur: ✅ Docker Environment stabil (Valkey, Keycloak, Consul, Zipkin).
* Frontend: ✅ Web-App & Desktop-App (KMP), Login funktioniert, Sync-Logik vorhanden.
* Hardware: ✅ Minisforum MS-R1 eingetroffen.
---
@@ -70,7 +71,7 @@ Wir validieren die gesamte Architektur-Kette (Frontend -> Gateway -> Service ->
* Architektur-Entscheidung: Dezentraler Microservice (wegen Resource-Bursts).
* Technologie-Evaluierung: JasperReports, Thymeleaf + Flying Saucer, etc.
4. **Infrastructure Setup (Home-Server):**
* Hardware: Minisforum MS-R1 (ARM64, 12 Cores, 10G LAN).
* Hardware: Minisforum MS-R1 (ARM64, 12 Cores, 10G LAN) ✅ **GELIEFERT (07.02.2026)**.
* OS: Debian 12 (Vendor Variant) als Host.
* Hypervisor: **Incus** (LXC/LXD Fork).
* Virtualization Strategy: