mirror of https://github.com/nickyeoman/docker-compose-cookbooks.git synced 2026-09-03 18:36:22 +00:00

Files

T

History

codeandClaude Fable 5 340866f9f4 complete all stack READMEs to the 9-section template

Existing content preserved and reordered to the canonical section order;
missing sections generated from each stack's compose data (ports, volumes,
env vars, image links). Fixes copy-paste errors in Dockhand sections
(qbittorrent pointed at archivebox; invokeai/thunderbird said SERVICENAME)
and persistant->persistent typos in gatus.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-16 06:25:05 +00:00

compose.yaml

feat: add lidarr_dev stack, rewrite prowlarr_dev, align template conventions

2026-07-02 21:23:02 -07:00

README.md

complete all stack READMEs to the 9-section template

2026-07-16 06:25:05 +00:00

sample.env

normalize all stacks to conventions

2026-07-16 06:24:54 +00:00

README.md

Lidarr

Overview

Lidarr is a music collection manager for Usenet and BitTorrent users. It automatically monitors specified artists, searches for new releases (or upgrades to existing tracks), and sends them to your download client. After download, Lidarr renames and organizes the files into your music library and can notify your media server of the new content.

Project Details

Project Repository: https://lidarr.audio/
Container Image: ghcr.io/hotio/lidarr
Reverse Proxy Port: 8686

Getting Started

Open http://localhost:8686 in your browser and complete the initial setup wizard:

Choose your UI language
Add a download client — select qBittorrent, enter its host/port/credentials
Add an indexer — or connect to Prowlarr for automatic indexer sync

Once the wizard finishes, Lidarr displays "No artists found". To populate your library:

Go to Settings → Media Management and add a Root Folder (e.g., /music) — this is where your organized music library will live
Click Add an artist and search by name — Lidarr fetches metadata, discography, and album art
Lidarr cross-references your Root Folder for any existing files and matches them to the artist's catalog

Download flow

qBittorrent downloads to its own directory → Lidarr picks it up, renames/tags the files, and moves them into <Root Folder>/Artist Name/Album/

Spotify playlist import

Lidarr doesn't natively import Spotify playlists. Use a community tool like SpotifyToLidarr or set up a List (Settings → Lists) from Last.fm or MusicBrainz to auto-add artists based on your listening habits.

Environment Variable Notes

Variable	Description
`LIDARR_IMAGE`	Container image (default: `ghcr.io/hotio/lidarr:release`)
`LIDARR_RESTART`	Restart policy (default: `unless-stopped`)
`LIDARR_PORT`	Published port for the web UI (default: `8686`)
`VOL_PATH`	Base path for persistent data volumes (default: `/data`)
`TZ`	Container timezone (default: `America/Vancouver`)

Volume Notes

Volume	Purpose
`${VOL_PATH:-/data}/lidarr/config`	Application configuration and database
`${VOL_PATH:-/data}/lidarr/data`	Download client data and working directory

Network Notes

Requires an external proxy network. Create it once with:

docker network create proxy

Docker Run

docker run -d \
  --name=lidarr \
  -e PUID=1000 \
  -e PGID=1000 \
  -e UMASK=002 \
  -e TZ=America/Vancouver \
  -p 8686:8686 \
  -v ${VOL_PATH:-/data}/lidarr/config:/config \
  -v ${VOL_PATH:-/data}/lidarr/data:/data \
  --network proxy \
  --restart unless-stopped \
  ghcr.io/hotio/lidarr:release

Additional Notes / Gotchas

Nothing specific to this stack so far.

Dockhand Stack, Deploy from Git

Cookbooks Repository
stackname: lidarr_dev
Compose file path: lidarr_dev/compose.yaml
Additional env file (optional): lidarr_dev/sample.env

Load lidarr_dev/sample.env into the Environment variables in Dockhand, then create the Stack.