Release 2.5.0: service cards, acknowledging problems, hardware monitoring #5
Loading…
Reference in a new issue
No description provided.
Delete branch "Dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Release 2.5.0.
New
Changes / fixes
[object Object]; qBittorrent speeds readable; Pause/Resume buttons styled.Migration 0014 (schema 14):
entity_acktable + two triggers onentity_state;service_cardtable; moves approved Unraid drives to the newhardwaresurface; swaps old stand-in icons for the logos; adds theservice_cardsmodule to every stored layout (phone, desktop, tablet, every saved view and its tiers).Package:
updates/versions/2.5.0.zip, 8,099,597 bytes, SHA-256796ef11a46d25951d3613f6db76f5d4afb50e5ef3da6080a563d369a227e3c00, 101 entries.Verified: migration 0014 on a throwaway database seeded with every layout shape (all stay valid); ack kept while down and cleared on recovery; drives moved to hardware; problems/devices/hardware/shares split in the bootstrap; card create/update/resolve; all Python compiles and all JS parses.
Not verified: in a browser, and against the real services (Plex, Sonarr, Radarr, qBittorrent, Immich, Unraid) — Sonarr/Radarr history and Unraid's
sharesquery are new calls. AdGuard and TrueNAS not testable (air-gapped). qBittorrent Pause/Resume not exercised.