@ -12,11 +12,15 @@ The path types are outlined as follows:
* `- git:` refers to a metadata file which is hosted on the [Configs Repo](https://github.com/meisnate12/Plex-Meta-Manager-Configs).
* `- git:` refers to a metadata file which is hosted on the [Configs Repo](https://github.com/meisnate12/Plex-Meta-Manager-Configs).
* `- repo:` refers to a metadata file which is hosted on a custom repository specified aby the user with the [`custom_repo` Setting Attribute](settings.md#custom-repo).
* `- repo:` refers to a metadata file which is hosted on a custom repository specified aby the user with the [`custom_repo` Setting Attribute](settings.md#custom-repo).
## Template Variables
## YAML Controls
[Template Variables](../metadata/templates.md#template-variables) can be added to every template in any defined YAML file by adding the `template_variables` attribute to the dictionary defining the file.
You can have some control of yaml files from inside your Configuration file by using YAML Controls.
### Example
### Template Variables
You can define [Template Variables](../metadata/templates.md#template-variables) that will be added to every template in the associated YAML file by adding the `template_variables` attribute to the dictionary defining the file.
#### Example
```yaml
```yaml
libraries:
libraries:
@ -26,6 +30,10 @@ libraries:
template_variables:
template_variables:
schedule_separator: never
schedule_separator: never
collection_mode: hide
collection_mode: hide
- git: PMM/actor # Notice how the `-` starts this "section"
template_variables:
schedule_separator: never
collection_mode: hide
```
```
In this example there will be two template variables added to every template in the git file PMM/genre.
In this example there will be two template variables added to every template in the git file PMM/genre.
@ -34,6 +42,26 @@ In this example there will be two template variables added to every template in
What these variables will do depends on how they're defined in the Metadata File.
What these variables will do depends on how they're defined in the Metadata File.
### Schedule
Each [`metadata_path`](libraries.md#metadata-path), [`overlay_path`](libraries.md#overlay-path), or [`playlist_files`](libraries.md#metadata-path) can be scheduled by adding the `schedule` attribute to the dictionary defining the file.
Below is an example of a scheduled Metadata File, Overlay File, and Playlist File:
```yaml
libraries:
Movies:
schedule: weekly(saturday)
metadata_path:
- file: config/Movies.yml
schedule: weekly(friday)
overlay_path:
- git: PMM/overlays/imdb
playlist_files:
- file: config/Playlists.yml
schedule: weekly(sunday)
```
## Metadata Path
## Metadata Path
The [`metadata_path`](libraries.md#metadata-path) attribute is defined under the [`libraries`](libraries) attribute in your [Configuration File](configuration).
The [`metadata_path`](libraries.md#metadata-path) attribute is defined under the [`libraries`](libraries) attribute in your [Configuration File](configuration).
@ -67,6 +95,39 @@ Within the above example, PMM will:
</details>
</details>
## Overlay Path
The [`overlay_path`](libraries.md#overlay-path) attribute is defined under the [`libraries`](libraries) attribute in your [Configuration File](configuration).
### Example
<details>
<summary>Click to Expand</summary>
<br/>
In this example, multiple overlay file path types are defined for the `"TV Shows"` library:
```yaml
libraries:
TV Shows:
overlay_apth:
- file: config/overlays.yml
- folder: config/overlay configs/
- git: PMM/overlays/imdb
- repo: overlays
- url: https://somewhere.com/Overlays.yml
```
Within the above example, PMM will:
* First, look within the root of the PMM directory (also known as `config/`) for a metadata file named `overlays.yml`. If this file does not exist, PMM will skip the entry and move to the next one in the list.
* Then, look within the root of the PMM directory (also known as `config/`) for a directory called `overlay configs`, and then load any metadata files within that directory.
* Then, look at the [meisnate12 folder](https://github.com/meisnate12/Plex-Meta-Manager-Configs/tree/master/meisnate12) within the GitHub Configs Repo for a file called `PMM/overlays/imdb.yml` which it finds [here](https://github.com/meisnate12/Plex-Meta-Manager-Configs/blob/master/PMM/overlays/imdb.yml).
* Then, look at the within the Custom Defined Repo for a file called `overlays.yml`.
* Finally, load the metadata file located at `https://somewhere.com/Overlays.yml`
</details>
## Playlist Files
## Playlist Files
The [`playlist_files`](libraries.md#playlist-files-attribute) at the top level in your [Configuration File](configuration).
The [`playlist_files`](libraries.md#playlist-files-attribute) at the top level in your [Configuration File](configuration).