Servarr · bakerboy448 · Jun 7, 2026 · Jun 7, 2026 · Jun 7, 2026 · Jun 7, 2026
diff --git a/docker-guide.md b/docker-guide.md
@@ -136,7 +136,7 @@ It is also important to remember that you’ll need to setup or re-configure pat
 
 ## Examples
 
-What matters here is the general structure, not the names. You are free to pick folder names that make sense to you. And there are other reasonable ways of arranging things too. We suggest keeping usenet and torrent downloads seperated, since torrents seed it generally isn't safe to just `rm -rf`, but if you know you've already imported all your usenet downloads you can clean up as needed. Keeping 
+What matters here is the general structure, not the names. You are free to pick folder names that make sense to you. And there are other reasonable ways of arranging things too. We suggest keeping usenet and torrent downloads separated, since torrents seed it generally isn't safe to just `rm -rf`, but if you know you've already imported all your usenet downloads you can clean up as needed. Keeping
 
 This example `data` folder has subfolders for torrents and usenet and each of these have subfolders for tv, movie and music downloads to keep things neat. The `media` folder has nicely named `TV`, `Movies`, `Books`, and `Music` subfolders. This `media` folder is your library and what you’d pass to software Plex, Kodi, Emby, Jellyfin, and Bazarr which only need the library.
 

diff --git a/lidarr/activity.md b/lidarr/activity.md
@@ -2,7 +2,7 @@
 title: Lidarr Activity
 description: Monitor download progress, search history, and queue management in Lidarr
 published: true
-date: 2026-06-06T13:48:53.842Z
+date: 2026-06-07T00:00:00.000Z
 tags: lidarr, activity, queue, downloads, history, monitoring
 editor: markdown
 dateCreated: 2021-06-14T21:35:25.390Z
@@ -26,7 +26,7 @@ Lidarr only shows items that are in the download client category configured unde
 
 ### Queue columns
 
-The queue table shows the following columns by default: Status, Artist, Album Title, Quality, Formats, Protocol, Download Client, Output Path, Time Left, Added, and Progress. Use **Options** to show or hide columns or change their order.
+The queue table shows the following columns by default: Status, Artist, Album Title, Quality, Formats, Time Left, and Progress. Use **Options** to show or hide columns or change their order.
 
 ### Queue statuses
 
@@ -54,11 +54,11 @@ Click **Options** in the queue toolbar to open Table Options:
 
 | Option | Default | Description |
 |---|---|---|
-| Page Size | 250 | Number of queue items shown per page. |
+| Page Size | 20 | Number of queue items shown per page. |
 | Show Unknown Artist Items | On | Shows items in Lidarr's download client category that Lidarr can't match to any artist in your library (for example, removed artists or items added to the category manually). |
 | Columns | (see below) | Choose which columns are visible and their display order. |
 
-Available columns: Status, Artist, Album Title, Album Release Date, Quality, Formats, Custom Format Score, Protocol, Indexer, Download Client, Release Title, Size, and Output Path.
+Available columns: Status, Artist, Album Title, Album Release Date, Quality, Formats, Custom Format Score, Protocol, Indexer, Download Client, Release Title, Size, Output Path, Time Left, Added, and Progress.
 
 ## History
 

diff --git a/lidarr/beets-integration.md b/lidarr/beets-integration.md
@@ -1,8 +1,8 @@
 ---
 title: Lidarr and beets Integration
-description: 
+description:
 published: true
-date: 2026-05-29T13:03:01.899Z
+date: 2026-06-07T00:00:00.000Z
 tags: lidarr, beets
 editor: markdown
 dateCreated: 2026-04-26T15:17:29.688Z
@@ -46,7 +46,7 @@ In this pattern, beets runs once per import triggered by a Lidarr Custom Script.
 
 ## How it works
 
-Lidarr fires its **On Import / On Upgrade** event after it has moved and renamed the downloaded files into the library folder. A Custom Script registered in **Settings → Connect** receives the file paths via the `Lidarr_AddedTrackPaths` environment variable (pipe-separated). The script invokes beets against those files with a configuration that writes tags but doesn't move or copy anything.
+Lidarr fires its **On Release Import / On Upgrade** event after it has moved and renamed the downloaded files into the library folder. A Custom Script registered in **Settings → Connect** receives the file paths via the `Lidarr_AddedTrackPaths` environment variable (pipe-separated). The script invokes beets against those files with a configuration that writes tags but doesn't move or copy anything.
 
 ## Required beets configuration
 
@@ -128,7 +128,7 @@ foreach ($dir in $albumDirs) {
 1. Go to **Settings → Connect → + Add Connection → Custom Script**.
 2. Set **Name** to something descriptive, for example, `beets tag enrichment`.
 3. Set **Path** to the full path of the script file.
-4. Enable **On Import** and **On Upgrade**. Leave other triggers disabled unless you specifically want beets to run on those events.
+4. Enable **On Release Import** and **On Upgrade**. Leave other triggers disabled unless you specifically want beets to run on those events.
 5. Click **Test**. The script receives a test event and should exit cleanly without errors.
 
 ## Trade-offs
@@ -201,4 +201,4 @@ Two scenarios where the tools can conflict:
 - [Custom Scripts](/lidarr/custom-scripts): environment variables available to scripts and how to register them
 - [Settings: Metadata](/lidarr/settings#metadata): Write Tags setting and metadata consumer options
 - [beets documentation](https://beets.readthedocs.io/en/stable/)
-- [beets installation guide](https://beets.readthedocs.io/en/stable/guides/installation.html)
+- [beets installation guide](https://beets.readthedocs.io/en/stable/guides/installation.html)
diff --git a/lidarr/calendar.md b/lidarr/calendar.md
@@ -2,7 +2,7 @@
 title: Lidarr Calendar
 description: View upcoming album releases and track music release schedules
 published: true
-date: 2026-05-29T13:10:48.016Z
+date: 2026-06-07T00:00:00.000Z
 tags: lidarr, calendar, releases, schedule, albums, music, planning
 editor: markdown
 dateCreated: 2021-06-14T21:35:03.094Z
@@ -18,9 +18,11 @@ Each release tile is color-coded to show its current status:
 
 | Color | Meaning |
 |---|---|
-| Green | Files on disk; Lidarr has this release. |
+| Green | All tracks downloaded; Lidarr has a complete copy of this release. |
 | Blue | Monitored and upcoming; the release date is in the future. |
-| Yellow/Orange | Monitored, released, and missing; past release date but no files yet. |
+| Purple | Currently downloading; the release is in the queue or was recently grabbed. |
+| Orange/Yellow | Partially downloaded; some but not all tracks are on disk. |
+| Red | Monitored, released, and missing; past release date but no files found. |
 | Grey | Unmonitored; Lidarr isn't looking for this release. |
 
 ## Navigation
@@ -55,8 +57,8 @@ The **Options** button opens the Calendar Options dialog, split into two section
 
 | Option | Default | Description |
 |---|---|---|
-| Collapse Multiple Albums | On | When more than one album from the same artist releases on the same day, collapse them into a single tile instead of showing each one. |
-| Icon for Cutoff Unmet | On | Show a visual indicator on release tiles where files exist but the quality cutoff hasn't been met. |
+| Collapse Multiple Albums | Off | When more than one album from the same artist releases on the same day, collapse them into a single tile instead of showing each one. |
+| Icon for Cutoff Unmet | Off | Show a visual indicator on release tiles where files exist but the quality cutoff hasn't been met. |
 
 **Global** (apply across all browsers and users):
 

diff --git a/lidarr/concepts.md b/lidarr/concepts.md
@@ -2,7 +2,7 @@
 title: Lidarr Concepts
 description: How Lidarr models music, why MusicBrainz metadata matters, and when Lidarr is (and isn't) the right tool for your library
 published: true
-date: 2026-05-29T13:00:43.061Z
+date: 2026-06-07T00:00:00.000Z
 tags: lidarr, releases, metadata, concepts, musicbrainz, artist
 editor: markdown
 dateCreated: 2026-04-18T16:48:08.649Z
@@ -33,10 +33,11 @@ Examples of `Releases`:
 - EP
 - Single
 - Broadcast
+- Other
 
 If something you want to manage doesn't exist as a `Release` in the metadata source, Lidarr can't handle it. Lidarr has no "add it locally only" escape hatch.
 
-Lidarr is audio-only. MusicBrainz marks some recordings as video (music videos, live video streams, etc.). Lidarr skips those entirely and won't search for, grab, or import a release where all tracks carry the video flag.
+Lidarr is audio-only. Releases that are recorded on video-only media formats (DVD, Blu-ray, VHS, etc.) are excluded: Lidarr filters out tracks on those media and will not import or search for a release that contains no audio tracks after that filtering.
 
 > You can only manage `Releases` in Lidarr if they exist in third-party services.
 {.is-info}

diff --git a/lidarr/custom-scripts.md b/lidarr/custom-scripts.md
@@ -2,7 +2,7 @@
 title: Lidarr Custom Scripts
 description: Guide for creating and implementing custom scripts for automation and integration in Lidarr
 published: true
-date: 2026-05-29T13:03:38.922Z
+date: 2026-06-07T00:00:00.000Z
 tags: lidarr, scripts, automation, custom, integration, hooks, api
 editor: markdown
 dateCreated: 2021-11-24T19:22:09.331Z
@@ -21,7 +21,7 @@ Lidarr writes script output to the log files:
 | Output | Log level | Log file |
 |---|---|---|
 | `stdout` | `Debug` | `config/logs/Lidarr.debug.txt` |
-| `stderr` | `Info` | `config/logs/Lidarr.txt` |
+| `stderr` | `Error` | `config/logs/Lidarr.txt` |
 | Script trigger | `Trace` | `config/logs/Lidarr.trace.txt` |
 
 Enable **Debug** or **Trace** logging in **Settings → General → Logging** to see script output in the log files.
@@ -398,4 +398,4 @@ curl -s -X POST "$WEBHOOK_URL" \
 ## See also
 
 - [Settings: Connect](/lidarr/settings#connections): where you register scripts in the Lidarr UI
-- [Beets Integration](/lidarr/beets-integration): using a custom script to invoke beets for tag enrichment after import
+- [Beets Integration](/lidarr/beets-integration): using a custom script to invoke beets for tag enrichment after import
diff --git a/lidarr/environment-variables.md b/lidarr/environment-variables.md
@@ -2,7 +2,7 @@
 title: Lidarr Environment Variables
 description: Complete guide to Lidarr environment variables for configuration management including Docker, database, authentication, and server settings
 published: true
-date: 2026-05-29T13:14:55.964Z
+date: 2026-06-07T00:00:00.000Z
 tags: lidarr, docker, installation, scripts, postgres
 editor: markdown
 dateCreated: 2025-09-06T22:28:37.512Z
@@ -36,6 +36,7 @@ The config namespaces are shared between all Servarr apps and correspond to the
 | `AuthenticationEnabled`  | `AUTH`     | `ENABLED`            | `LIDARR__AUTH__ENABLED`           |
 | `AuthenticationMethod`   | `AUTH`     | `METHOD`             | `LIDARR__AUTH__METHOD`            |
 | `AuthenticationRequired` | `AUTH`     | `REQUIRED`           | `LIDARR__AUTH__REQUIRED`          |
+| `TrustCgnatIpAddresses`  | `AUTH`     | `TRUSTCGNATIPADDRESSES` | `LIDARR__AUTH__TRUSTCGNATIPADDRESSES` |
 | `LogLevel`               | `LOG`      | `LEVEL`              | `LIDARR__LOG__LEVEL`              |
 | `FilterSentryEvents`     | `LOG`      | `FILTERSENTRYEVENTS` | `LIDARR__LOG__FILTERSENTRYEVENTS` |
 | `LogRotate`              | `LOG`      | `ROTATE`             | `LIDARR__LOG__ROTATE`             |
@@ -47,13 +48,15 @@ The config namespaces are shared between all Servarr apps and correspond to the
 | `SyslogServer`           | `LOG`      | `SYSLOGSERVER`       | `LIDARR__LOG__SYSLOGSERVER`       |
 | `SyslogPort`             | `LOG`      | `SYSLOGPORT`         | `LIDARR__LOG__SYSLOGPORT`         |
 | `SyslogLevel`            | `LOG`      | `SYSLOGLEVEL`        | `LIDARR__LOG__SYSLOGLEVEL`        |
-| `DbEnabled`              | `LOG`      | `DBENABLED`          | `LIDARR__LOG__DBENABLED`          |
+| `LogDbEnabled`           | `LOG`      | `DBENABLED`          | `LIDARR__LOG__DBENABLED`          |
 | `PostgresHost`           | `POSTGRES` | `HOST`               | `LIDARR__POSTGRES__HOST`          |
 | `PostgresPort`           | `POSTGRES` | `PORT`               | `LIDARR__POSTGRES__PORT`          |
 | `PostgresUser`           | `POSTGRES` | `USER`               | `LIDARR__POSTGRES__USER`          |
 | `PostgresPassword`       | `POSTGRES` | `PASSWORD`           | `LIDARR__POSTGRES__PASSWORD`      |
 | `PostgresMainDb`         | `POSTGRES` | `MAINDB`             | `LIDARR__POSTGRES__MAINDB`        |
 | `PostgresLogDb`          | `POSTGRES` | `LOGDB`              | `LIDARR__POSTGRES__LOGDB`         |
+| `PostgresMainDbConnectionString` | `POSTGRES` | `MAINDBCONNECTIONSTRING` | `LIDARR__POSTGRES__MAINDBCONNECTIONSTRING` |
+| `PostgresLogDbConnectionString`  | `POSTGRES` | `LOGDBCONNECTIONSTRING`  | `LIDARR__POSTGRES__LOGDBCONNECTIONSTRING`  |
 | `UrlBase`                | `SERVER`   | `URLBASE`            | `LIDARR__SERVER__URLBASE`         |
 | `BindAddress`            | `SERVER`   | `BINDADDRESS`        | `LIDARR__SERVER__BINDADDRESS`     |
 | `Port`                   | `SERVER`   | `PORT`               | `LIDARR__SERVER__PORT`            |