@ -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.
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 default 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:
Below is a `radarr` mapping example and the full set of attributes:
```yaml
```yaml
radarr:
radarr:
@ -52,34 +54,48 @@ radarr:
# Other examples:
# 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.
```yaml
```
libraries:
libraries:
Movies:
Library01: # this library uses the default radarr config
metadata_path:
- file: config/Movies.yml
Library02: # this library overrides radarr root path and profile
metadata_path:
metadata_path:
- file: config/Movies.yml
- file: config/Movies.yml
Movies - 4K:
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