[JesusPaz]

Summary

This PR adds a new app: Warden (folder Apps/Warden/). I maintain the upstream project. Warden provides self-hosted uptime monitoring, adaptive latency alerts, incident history and public status pages.

What changed

• New app directory Apps/Warden/:
  • docker-compose.yml with x-casaos metadata (id: com.projecthelena.warden), English and Spanish localization, installation tips and release metadata.
  • icon.svg and screenshot-1.png from the upstream project.
• Source package for the repository's v2 store and legacy v1 compatibility archive.

About the app

• Image: ghcr.io/projecthelena/warden:v0.9.0 (linux/amd64 and linux/arm64).
• Port: container 9090 → host 9196, avoiding the store's Lyrion Music Server port 9090.
• Data: SQLite in a persistent Docker volume at /data. A named volume preserves the image's UID 65532 ownership without host-side chown or running Warden as root. Backup/storage behavior is explained in the installation tips.
• First launch creates the administrator account in the browser. No default credentials, privileged mode or host Docker socket are included. Unprivileged ICMP checks are enabled through ping_group_range.
• Upstream: https://github.com/projecthelena/warden
• Release: https://github.com/projecthelena/warden/releases/tag/v0.9.0

Validation

• Compose file is valid YAML; repository validator reports zero errors or warnings.
• docker compose config -q passed locally.
• scripts/build_dist.sh passed using an isolated source tree with Warden and the repository's store configuration/languages. Default/Spanish metadata and amd64/arm64 Compose files generated with zero errors or warnings.
• Legacy v1 builder passed against the complete repository; archive includes Apps/Warden/docker-compose.yml.
• Published image manifest confirms linux/amd64 and linux/arm64.
• Docker Compose smoke test on arm64: fresh database, administrator setup/login, container recreation and login using the persisted account; runs as UID 65532. Repeated after changing the host port to 9196.
• CasaOS local platform test on arm64: registered this PR branch as an App Store source, installed Warden from its store listing, completed setup in the browser, created a working HTTP monitor, restarted through the CasaOS API and logged in with the persisted account. Confirmed named volume warden_warden_data and UID 65532. The harness used the official AppManagement v0.4.10-alpha2 and UI v0.4.25 release artifacts selected by the CasaOS installer, inside an isolated Docker environment.
• ZimaOS v1.6.2 x86_64 in a local QEMU VM: installed the generated docker-compose.amd64.yml through the ZimaOS AppManagement API, completed Warden setup in the browser, created a working HTTP monitor, restarted through the ZimaOS API and logged in with the persisted account. The installed Compose retains the pinned amd64 image digest, port 9196 and named data volume.
• ZimaOS visual App Store install flow. The VM boots and its AppManagement API works, but its main zimaos.service repeatedly exits and the visual store is unavailable. The API installation test above does not establish visual store-flow compatibility.

The PR remains a draft while the ZimaOS visual store flow is unverified. The CasaOS test uses official application-management and UI components in a container harness, not a physical CasaOS device. ZimaOS runs the actual OS image under software emulation; these tests verify installation and persistence, not performance.

An initial attempt with the unmodified third-party dockurr/casa image was discarded: its modified components rewrote the app user, ports and storage. The successful CasaOS result above was obtained after replacing those components with the official release artifacts, without modifying the Warden package.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud