<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Administration on Navidrome</title><link>https://pr-496.navidrome-website.pages.dev/docs/usage/admin/</link><description>Recent content in Administration on Navidrome</description><generator>Hugo</generator><language>en</language><atom:link href="https://pr-496.navidrome-website.pages.dev/docs/usage/admin/index.xml" rel="self" type="application/rss+xml"/><item><title>Automated Backup</title><link>https://pr-496.navidrome-website.pages.dev/docs/usage/admin/backup/</link><pubDate>Sat, 21 Dec 2024 00:00:00 +0000</pubDate><guid>https://pr-496.navidrome-website.pages.dev/docs/usage/admin/backup/</guid><description>&lt;p&gt;Navidrome version 0.54.x introduces a backup feature that allows the music server&amp;rsquo;s data to get periodically exported.&#10;This guide will walk you through configuring backups using both a &lt;a href="https://pr-496.navidrome-website.pages.dev/docs/usage/configuration/options/"&gt;configuration&lt;/a&gt;&#10;file and environment variables, where to locate the backups, and how to restore from a backup.&lt;/p&gt;&#10;&lt;div class="alert alert-primary" role="alert"&gt;&#10;&lt;p&gt;Note: The backup process ONLY backs up the database (users, play counts, etc.). It does NOT back up the music or the config.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="configuring-backup-with-configtoml"&gt;Configuring Backup with config.toml&lt;a class="td-heading-self-link" href="#configuring-backup-with-configtoml" aria-label="Heading self-link"&gt;&lt;/a&gt;&#10;&lt;/h2&gt;&lt;p&gt;To configure backups using the navidrome.toml file, insert the following lines to set up backups:&lt;/p&gt;</description></item><item><title>Security Considerations</title><link>https://pr-496.navidrome-website.pages.dev/docs/usage/admin/security/</link><pubDate>Mon, 02 Jan 2017 00:00:00 +0000</pubDate><guid>https://pr-496.navidrome-website.pages.dev/docs/usage/admin/security/</guid><description>&lt;h2 id="permissions"&gt;Permissions&lt;a class="td-heading-self-link" href="#permissions" aria-label="Heading self-link"&gt;&lt;/a&gt;&#10;&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;You should NOT run Navidrome as &lt;code&gt;root&lt;/code&gt;&lt;/strong&gt;.&#10;Ideally you should have it running under its own user and enable the &lt;code&gt;EnforceNonRootUser&lt;/code&gt; configuration option.&#10;Navidrome only needs read-only access to the Music Folder, and read-write permissions to the Data Folder.&lt;/p&gt;&#10;&lt;h2 id="encrypted-passwords"&gt;Encrypted passwords&lt;a class="td-heading-self-link" href="#encrypted-passwords" aria-label="Heading self-link"&gt;&lt;/a&gt;&#10;&lt;/h2&gt;&lt;p&gt;To be able to keep compatibility with the Subsonic API and its clients, Navidrome needs to store user&amp;rsquo;s passwords in its database. By default, Navidrome&#10;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.&lt;/p&gt;</description></item><item><title>Anonymous Data Collection</title><link>https://pr-496.navidrome-website.pages.dev/docs/usage/admin/insights/</link><pubDate>Sun, 08 Dec 2024 00:00:00 +0000</pubDate><guid>https://pr-496.navidrome-website.pages.dev/docs/usage/admin/insights/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&#10;&lt;/h2&gt;&lt;p&gt;Navidrome includes an &lt;strong&gt;anonymous usage statistics feature&lt;/strong&gt; designed to help improve the project for all users.&#10;This page explains what data is collected, how it is used, and how to opt out if you prefer not to participate.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="key-principles"&gt;Key Principles&lt;a class="td-heading-self-link" href="#key-principles" aria-label="Heading self-link"&gt;&lt;/a&gt;&#10;&lt;/h2&gt;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Anonymous Data Only&lt;/strong&gt;: Navidrome collects only non-personal, anonymous data to guide future improvements.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;What’s Collected&lt;/strong&gt;: See &lt;a href="https://pr-496.navidrome-website.pages.dev/docs/usage/admin/insights/#what-will-be-collected"&gt;Collected Data&lt;/a&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;What’s NOT Collected&lt;/strong&gt;: No emails, IP addresses, usernames, or other identifiable data. See &lt;a href="https://pr-496.navidrome-website.pages.dev/docs/usage/admin/insights/#what-will-not-be-collected"&gt;Excluded Data&lt;/a&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Opt-Out Available&lt;/strong&gt;: Enabled by default, but you can disable it anytime.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;In-House Data Handling&lt;/strong&gt;: Collected data goes to an &lt;a href="https://github.com/navidrome/insights"&gt;open-source server&lt;/a&gt; hosted by the project—no third-party services.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Full Transparency&lt;/strong&gt;: Logs and UI indicators show when data is sent and what it contains.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="what-will-be-collected"&gt;What Will Be Collected?&lt;a class="td-heading-self-link" href="#what-will-be-collected" aria-label="Heading self-link"&gt;&lt;/a&gt;&#10;&lt;/h2&gt;&lt;p&gt;Below is a plain-English explanation of what &lt;a href="https://github.com/navidrome/navidrome/blob/insights/core/metrics/insights/data.go"&gt;each field&lt;/a&gt;&#10;is generally intended to represent. Each field corresponds to a piece of information about the running application or its environment:&lt;/p&gt;</description></item></channel></rss>