6 Commits

Author	SHA1	Message	Date
Kevin Veen-Birkenbach	e09f561f0b	Refactor run-once orchestration and bootstrap Mailu/Mastodon in a single deploy ... - Replace legacy utils/run_once.yml with the new helpers utils/once_flag.yml and utils/once_finalize.yml - Introduce utils/compose_up.yml to ensure docker-compose stacks are up and to flush handlers safely without coupling to run-once flags - Migrate all affected roles (desk-*, dev-*, sys-ctl-*, sys-svc-*, web-app-*, web-svc-*, util-*) to the new run-once helpers - Rework sys-svc-msmtp to auto-load Mailu once per deploy, check reachability, and reuse the running stack instead of requiring multiple playbook passes - Adjust web-app-mailu to integrate cert deployment, handler flushing, and run-once handling so Mailu is fully initialized in a single deploy - Improve Matomo, CDN, logout and CSP/health-check related roles to cooperate with the new compose_up / once_* pattern - Simplify alarm/backup/timer/service orchestration (sys-ctl-alm-*, sys-bkp-provider, sys-timer-cln-bkps, etc.) by moving run-once logic into dedicated 01_core.yml files - Update integration tests so utils/once_flag.yml and utils/once_finalize.yml are recognised as valid run-once providers, keeping the global run_once_* guarantees consistent - Align frontend injection and service dependencies so Mastodon- and Mailu-related services can be brought up coherently within a single deployment cycle rather than several iterations	2025-12-01 13:30:50 +01:00
Kevin Veen-Birkenbach	880d0ab1d6	Removed block from main.yml and moved run_once logic to 01_core.yml	2025-11-28 23:24:04 +01:00
Kevin Veen-Birkenbach	a312f353fb	Refactor JVM memory filters, add Redis sizing and Docker cleanup service ... - Replace jvm_filters with unified memory_filters (JVM + Redis helpers) - Add redis_maxmemory_mb filter and unit tests - Introduce sys-ctl-cln-docker role (systemd-based Docker prune + anon volumes) - Refactor disk space health check to Python script and wire SIZE_PERCENT_CLEANUP_DISC_SPACE - Adjust schedules and services for Docker cleanup and disk space health See discussion: https://chatgpt.com/share/6925c1c5-ee38-800f-84b6-da29ccfa7537	2025-11-25 15:50:27 +01:00
Kevin Veen-Birkenbach	91ce097a0a	feat(sys-service): migrate cleanup/backup services to generic units; harden disk-space cleanup ... Services: add SYS_SERVICE_CLEANUP_BACKUPS and SYS_SERVICE_CLEANUP_DISC_SPACE in group vars. sys-ctl-bkp-docker-2-loc: switch to sys-service; add ExecStartPre lock; ExecStartPost triggers backup cleanup; OnFailure → cleanup-failed; fix shell quoting. sys-ctl-cln-bkps: switch to sys-service; pass CLI args via ExecStart; add ExecStartPre lock; set OnFailure; copy files; remove role-specific service template. sys-ctl-cln-disc-space: switch to sys-service; enable timer; set OnFailure; provide ExecStart/ExecStartPre; copy files; remove role-specific service template. script.sh (disc-space): non-interactive docker exec; consistent threshold message (use parameter); guard docker/pacman via command checks; robust container check; fix typo; use POSIX '='. svc-opt-keyboard-color: minor formatting cleanup. sys-ctl-hlth-disc-space: chain OnFailure to cleanup-disc-space service. Context: ChatGPT conversation (Sep 10, 2025, Europe/Berlin) — https://chatgpt.com/share/68c1982e-bdc8-800f-bf13-a8b9f084f90e	2025-09-10 17:24:56 +02:00
Kevin Veen-Birkenbach	4ce681e643	Add integration test: ensure roles including 'sys-service' define system_service_id ... This test scans all roles for tasks including: - include_role: name: sys-service If present, the role must define a non-empty 'system_service_id' in vars/main.yml. Helps enforce consistency and prevent misconfiguration. Ref: https://chatgpt.com/share/68a536e5-c384-800f-937a-f9d91249950c	2025-08-20 04:46:27 +02:00
Kevin Veen-Birkenbach	55cf3d0d8e	Solved unit performance tests	2025-08-20 04:35:46 +02:00