@ -8,6 +8,8 @@ Items in your List Exclusions will be ignored by PMM.
A `radarr` mapping can be either in the root of the config file as global mapping for all libraries, or you can specify the `radarr` mapping individually per library.
At the library level, only those settings which are different to the global settings need to be specified; there is an example of this at the end of the page.
Below is a `radarr` mapping example and the full set of attributes:
```yaml
radarr:
@ -52,34 +54,61 @@ radarr:
# Other examples:
Specifying a second Radarr instance for a specific library:
Specifying different options for specific libraries:
In this example we have two Radarr instances, standard and 4K. We want to add 4K movies to the 4K Radarr instance with a different root folder and availability.
In this example we have two Radarr instances, standard and 4K, and four libraries showing how one can override individual settings at the library level. Also, movies are being added to the "Library05" library outside Radarr via a custom script and I want those new movies added to Radarr for tracking.
```yaml
```
libraries:
Movies:
Library01: # this library uses the default radarr config
metadata_path:
- file: config/Movies.yml
Movies - 4K:
Library02: # this library overrides radarr root path and profile
metadata_path:
- file: config/Movies.yml
radarr:
root_folder_path: /data/media/movies/tony
quality_profile: Better
Library03: # this library overrides radarr quality profile
metadata_path:
- file: config/Movies.yml
radarr:
quality_profile: Best
Library04: # this library uses the 4K radarr instance
metadata_path:
- file: config/Movies.yml
radarr:
url: https://radarr-4k.bing.bang
token: SOME_OTHER_TOKEN
root_folder_path: /data/media/movies/geezer
quality_profile: Bestest
Library05: # movies get added by a custom script so they should get added to radarr-4k
@ -8,6 +8,9 @@ Items in your List Exclusions will be ignored by PMM.
A `sonarr` mapping can be either in the root of the config file as global mapping for all libraries, or you can specify the `sonarr` mapping individually per library.
At the library level, only those settings which are different to the global settings need to be specified; there is an example of this at the end of the page.
Below is a `sonarr` mapping example and the full set of attributes:
```YAML
sonarr:
@ -59,24 +62,48 @@ sonarr:
Specifying a second Sonarr instance for a specific library:
In this example we have two Sonarr instances, standard and 4K. We want to add 4K shows to the 4K Sonarr instance with a different root folder and quality profile. Also, shows are being added to the "TV Shows - 4K" library outside Sonarr via a custom script and I want those new shows added to Sonarr for tracking.
In this example we have two Sonarr instances, standard and 4K, with five libraries that override various details. Also, shows are being added to the "Library05" library outside Sonarr via a custom script and I want those new shows added to Sonarr for tracking.
```yaml
```
libraries:
TV Shows:
Library01: # this library uses the default sonarr config
metadata_path:
- file: config/TV.yml
Library02: # this library overrides sonarr root path and profile
metadata_path:
- file: config/TV.yml
radarr:
root_folder_path: /data/media/shows/tony
quality_profile: Better
Library03: # this library overrides sonarr quality profile
metadata_path:
- file: config/TV.yml
TV Shows - 4K:
radarr:
quality_profile: Best
Library04: # this library uses the 4K sonarr instance
metadata_path:
- file: config/TV.yml
sonarr:
url: https://sonarr-4K.bing.bang
token: SOME_TOKEN
root_folder_path: /shows-4K
quality_profile: 4K
radarr:
url: https://sonarr-4k.bing.bang
token: SOME_OTHER_TOKEN
root_folder_path: /data/media/shows/geezer
quality_profile: Bestest
Library05: # shows get added by a custom script so they should get added to sonarr-4k
@ -145,7 +145,7 @@ There are some attributes unique to `templates`; `default`, `optional`, `conditi
* `optional` can specify variables that if not specified on the template call will cause any attribute using one of those variables to be ignored in the template. You can make any template variable optional per collection by setting it to `null`.
* `conditionals` can specify variables based on conditions set by the user. See more [here](#conditionals)
* `move_prefix` can be given a list or comma-separated string of prefixes to move to the end of the collection/playlist name for sorting.
i.e. If you have `move_prefix: The` and a collection is called `The Avengers` then `<<collection_name>>` is replaced with `Avengers, The` instead of `The Avengers` for that collection.
i.e. If you have `move_prefix: The` and a collection is called `The Avengers` then `<<collection_sort>>` is replaced with `Avengers, The` instead of `The Avengers` for that collection.
Every template call is given these template variables.