Files
ProxMenux/AppImage/messages
MacRimiandClaude Opus 5 5f09af0162 fix(audit): state what the backup checks observed, not more
Two next steps in the backup area claimed more than the evidence behind
them supports, reported by @Vaso73 while reviewing the pattern.

A failed run is now treated as unsuccessful with a copy to confirm,
rather than asserted to have produced nothing usable — the task log does
not establish that. And a missing host-configuration record says no
backup is recorded here, leaving room for one this node cannot see.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-22 19:59:39 +02:00
..

Monitor dashboard translations

The ProxMenux Monitor dashboard uses a small client-side i18n layer.

  • English (en) is the source language and the runtime fallback.
  • Eight locales are shipped and fully populated end-to-end: en, de, es, fr, it, pt, sk, sv. Non-English catalogs started from an automated bootstrap and are being polished as native speakers pass through them.

To improve a translation, edit the values in your locale's common.json — keep placeholders such as {uptime}, {vmid} or {count} unchanged, and don't translate brand or product names (ProxMenux Monitor, Proxmox Backup Server, Secure Gateway, Tailscale, etc.). Missing keys fall back to English at runtime, so a partial refresh is always safe to merge.

Backup message composition regressions

From the repository root, run:

node tests/test_backup_archives_empty.cjs
node tests/test_backup_destination_messages.cjs

Prerequisites: Node.js and the typescript development dependency from AppImage/package.json must be installed/resolvable (normally in AppImage/node_modules). These tests compile actual JSX message branches and pure i18n lookup functions without importing the component or calling a backend. They cover whole English messages, missing-key locale fallback, loading/error branches, nonempty lists, the removal notice at zero/one/multiple archives, local-attach help, and unchanged shared labels. They do not replace browser or real-host acceptance. Keep literal paths in the local-attach help unchanged.

To add a new locale, see §11 → Adding a new locale in the Contributing Guide.