Files
ProxMenux/AppImage/messages
MacRimi 9b5cefb81a feat(oci): GPU selection per host and per image, one notification per update, and App tab for stack containers
- Immich asks what runs its video and its recognition in one menu, in both
  modes, and gives the GPU to the server and to Machine learning; AMD uses ROCm
- Frigate, Ollama, llama.cpp, Faster Whisper and Piper take the image built
  for the chosen GPU
- The acceleration menu offers only what the host can run
- An update or a recreation sends one notification with its result instead of
  the stop, backup and start of each container
- A private bridge with nothing connected is not reported as down
- Secondary containers of a stack appear in the App tab with their version and
  logo; Secure Gateway shows the same update state in both views
- A mistyped value in the wizard asks the same question again
2026-10-02 21:45:38 +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.