Administration on Navidrome

Automated Backup

Sat, 21 Dec 2024 00:00:00 +0000

Navidrome version 0.54.x introduces a backup feature that allows the music server’s data to get periodically exported. This guide will walk you through configuring backups using both a configuration file and environment variables, where to locate the backups, and how to restore from a backup.

Note: The backup process ONLY backs up the database (users, play counts, etc.). It does NOT back up the music or the config.

Configuring Backup with config.toml

To configure backups using the navidrome.toml file, insert the following lines to set up backups:

Security Considerations

Mon, 02 Jan 2017 00:00:00 +0000

Permissions

You should NOT run Navidrome as root. Ideally you should have it running under its own user. Navidrome only needs read-only access to the Music Folder, and read-write permissions to the Data Folder.

Encrypted passwords

To be able to keep compatibility with the Subsonic API and its clients, Navidrome needs to store user’s passwords in its database. By default, Navidrome encrypts the passwords in the DB with a shared encryption key, just for the sake of obfuscation as this key can be easily found in the codebase.

Anonymous Data Collection

Sun, 08 Dec 2024 00:00:00 +0000

Overview

Navidrome includes an anonymous usage statistics feature designed to help improve the project for all users. This page explains what data is collected, how it is used, and how to opt out if you prefer not to participate.

Key Principles

Anonymous Data Only: Navidrome collects only non-personal, anonymous data to guide future improvements.
What’s Collected: See Collected Data.
What’s NOT Collected: No emails, IP addresses, usernames, or other identifiable data. See Excluded Data.
Opt-Out Available: Enabled by default, but you can disable it anytime.
In-House Data Handling: Collected data goes to an open-source server hosted by the project—no third-party services.
Full Transparency: Logs and UI indicators show when data is sent and what it contains.

What Will Be Collected?

Below is a plain-English explanation of what each field is generally intended to represent. Each field corresponds to a piece of information about the running application or its environment: