32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
# Lidarr
|
|
|
|
Lidarr is a music collection manager that automates monitoring, downloading, importing, organizing, renaming, and
|
|
upgrading music releases.
|
|
|
|
## Deployment layout
|
|
|
|
- **Compose:** `/srv/docker/lidarr/docker-compose.yml`
|
|
- **Static configuration/source:** no additional mounted static configuration or local build source
|
|
- **Non-secret environment:** `PUID=1000`, `PGID=1000`, and `TZ=Etc/UTC` are declared in Compose; there is no
|
|
project-local `.env`
|
|
- **Secrets:** no separate secret file; Lidarr-generated API keys and integration credentials remain inside the
|
|
protected application-managed configuration
|
|
- **NVMe application state:** `/srv/appdata/lidarr/config`
|
|
- **Bulk HDD data:** `/data/Data1/lidarr/recyclebin`
|
|
- **Other mounts:** `/srv/downloads` for shared download processing, `/data/Data1/music/Music` for the read-write
|
|
music library, and `/etc/localtime` read-only
|
|
|
|
Secrets are never committed to this repository. Lidarr-generated API keys and
|
|
integration credentials remain inside the protected application-managed
|
|
configuration at `/srv/appdata/lidarr/config`; no separate secret environment is
|
|
declared.
|
|
|
|
## Dependencies and recovery
|
|
|
|
- **Networks/dependencies:** Lidarr uses the external `npm_proxy` network at `192.168.97.13`, the shared SABnzbd
|
|
download tree at `/srv/downloads`, and the shared music library at `/data/Data1/music/Music`; application-level
|
|
integrations are retained inside its protected configuration
|
|
- **Back up:** `/srv/appdata/lidarr/config` and the authoritative music library at `/data/Data1/music/Music`
|
|
- **Re-creatable:** the Lidarr container, download working data that can be fetched again, and expired recycle-bin
|
|
contents
|