Update
Update the NasDash image with backup and rollback.
The latest tag tracks the latest published image; it does not guarantee an immutable version. Back up data/ before pulling. If you use the optional named volume, back up nasdash-data instead. Never run docker compose down -v as part of a normal update.
docker compose images
docker image inspect --format '{{.RepoDigests}}' ghcr.io/lucas-lepajollec/nasdash:latest
docker compose stop nasdash
# Back up and verify /app/data (named volume or ./data bind mount).
docker compose pull nasdash
docker compose up -d
docker compose ps
docker compose logs --tail 100 nasdashTest /api/health, connectivity, pages, and a representative integration.
To roll back, change the Compose image: line to the previous digest or sha-<full-commit> tag, then recreate the container. Restore data only if a migration made it incompatible.
image: ghcr.io/lucas-lepajollec/nasdash:sha-<full-commit>docker compose up -dCurrent version status
See published GitHub releases for the current version. For exact rollback, keep the recorded image digest or sha-<full-commit> tag; do not recreate the deleted v1.0.0 tag.
Upgrading to 0.3.6
Keep the complete existing data mount. Existing accounts, privacy mode, appearance and pages are retained; the private defaults and first-start guide apply to fresh installations. The guide is not imposed on upgrades. You can choose the new bundled wallpapers in Settings → Appearance → Wallpaper, and save several Gluetun, NUT or apcupsd connections in Settings → Integrations. If you enable public mode, NasDash creates viewer when missing; review its page and widget permissions before allowing anonymous access.
The five bundled wallpapers are now drawn for NasDash under the project’s licence. Settings → Appearance → Wallpaper veil adjusts the background from 0 to 60 %, darkening it in dark mode and lightening it in light mode; blurred surfaces gain light translucent hairlines and saturation. New installations use card opacity 60 %, blur 24 px and veil 15 %. The sign-in screen and guide follow the dashboard’s glass settings. The dashboard tour can be replayed from Settings → Help → Replay the tour. Empty pages show administrators a dashed Add a widget slot that opens edit mode and the library; other users see one line of text.
Upgrading to 0.3.5
For upgrades through 0.3.5, keep the same complete data mount; the 0.3 releases introduce no automatic data migration. Grant newly added Media, Music, Downloads, Photos, Custom API, VPN and UPS widgets to readers with explicit widget allowlists. Preserve the original Host header through reverse proxies for saving and controls. VPN and UPS need their own connections in Settings → Integrations. Proxmox discovery in 0.3.5 avoids duplicate nodes; an existing duplicate can be removed from Devices. Rollback to a recorded 0.3.4 image keeps the data format; older images ignore newer widgets and settings, so remove unsupported widgets first or restore the pre-upgrade backup for the exact previous state. See the changelog for release details.
Earlier releases
Version 0.2.4 preserves existing accounts, integrations and saved pages without an automatic data migration. It fixes Docker relay responses and error handling, access and recovery safeguards, calendar imports and monitoring refreshes. Images/Volumes gain filters, pagination and protected bulk selection; CPU/GPU temperatures are separate. The supplied Docker proxy is optional: existing proxy users must retain their Compose service or run with --profile docker-proxy. Set NASDASH_TRUST_PROXY=true only behind a trusted proxy if forwarded client addresses are needed for rate limits. Demo edits survive reloads until Reset. Rolling back to 0.2.3 restores its earlier behavior and omits these security and reliability fixes.
Version 0.2.3 introduces no data migration from 0.2.2. It fixes secondary-link bubbles and ping details, recognizes Synology CPU temperature sensors, and adds host/usage/manual Storage ordering and widget-local metric/group ordering. Save the page to keep manual orders. Rolling back to 0.2.2 preserves the same data but ignores manual reading/group order and restores the earlier Storage presentation. Restore your pre-update backup for the exact earlier configuration.
Version 0.2.2 introduces no new storage migration from 0.2.1: existing accounts, passwords, keys and configuration are preserved. Startup now rejects inaccessible data or logos with the actual UID:GID; correct the folder permissions or Synology ACLs before retrying. Generated passwords appear once at startup for new accounts. For a lost existing password, stop NasDash and follow offline recovery. Rolling back to 0.2.1 keeps the same data, but restores first-login initialization and removes the recovery helper.