Nia documentation · 3.3.1
Updates
Update Docker or Debian installations while preserving data and keeping a rollback path.Read the release notes and create a current backup before major updates.
Update checks and privacy
The nia-todo server checks for stable releases when it starts, once per hour at a randomized minute, and when an administrator opens or refreshes the server-update status in the admin panel.
The primary source is the official update manifest at https://nia-todo.homelabdiary.dev/update/stable.json. If that request fails or returns invalid data, the server contacts the GitHub Releases API directly as a technical fallback. Both services receive normal connection metadata such as the request time, source IP address, and user agent. GitHub processes fallback requests under its General Privacy Statement.
By default, each completed check also sends one data-minimized event to the project’s self-hosted Umami instance. The request uses type: event; its fixed payload contains the field website with the dedicated Umami website ID, hostname: nia-todo.homelabdiary.dev, url: /update/stable.json, and name: server-update-check. This product hostname is not the hostname of the self-hosted instance. The event contains no installation ID, server version, user identity, instance hostname, todos, attachments, or other application content.
The receiving server processes the request time, source IP address, and fixed user agent Mozilla/5.0 (X11; Linux x86_64) nia-todo. Umami uses these connection details to generate a pseudonymous, regularly changing session identifier and an approximate location; the full IP address is not stored in the Umami database.
Operators can disable only the analytics event in Admin Panel → Instance Configuration. Update checks and notifications remain enabled. See the privacy policy for the legal basis, retention period, and data-subject rights.
Docker
Docker installations are updated outside the app:
docker compose pull
docker compose up -d
docker compose logs --tail=200 nia-todo
The admin panel can report that a newer version exists, but it does not replace a running container itself. Keep the persistent /data volume attached when recreating the service.
For controlled deployments, pin a version instead of latest:
image: docker.io/weedpump/nia-todo:2.0.0
Debian or Ubuntu
Supported full-package installations can update from /admin. nia-todo downloads the release package, verifies its published SHA256 checksum, creates a pre-upgrade SQLite backup, installs through a restricted root helper and restarts the service.
Manual update remains available:
sudo apt install ./nia-todo-server-vX.Y.Z-full.deb
sudo systemctl status nia-todo
The package preserves runtime data and creates a pre-upgrade database backup when a database exists.
After updating
- Confirm the reported server version.
- Check logs for migration or startup errors.
- Open a project and create a disposable todo.
- Verify attachments and realtime updates.
- Download updated native clients when the release includes them.
Do not downgrade across database migrations unless the release notes explicitly say it is supported. Restore the pre-upgrade backup with the previous application version instead.