These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
### Default `include`
```yaml
include:
@ -102,7 +106,7 @@ include:
- km # Central Khmer
- ch # Chamorro
- ce # Chechen
- ny # Chichewa, Chewa, Nyanja
- ny # Chichewa, Chewa, Nyanja
- zh # Chinese
- cu # ChurchSlavic, Old Slavonic, Church Slavonic, Old Bulgarian,OldChurchSlavonic
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
### Default `addons`
```yaml
addons:
@ -114,7 +117,7 @@ addons:
- 453993 # The Wolverine
```
## Default `title_override`
### Default `title_override`
```yaml
title_override:
@ -123,7 +126,7 @@ title_override:
535790: Godzilla (Anime)
```
## Default `movie`
### Default `movie`
```yaml
105995: 336560 # Anaconda: Lake Placid vs. Anaconda
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
### Default `trakt_list`
The below Trakt lists are used to populate the playlists associated with the keys.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
These are lists provided for reference to show what values will be in use if you do no customization. If you want to customize these values, use the methods described above. These do not show how to change a name or a list.
That’s a command you’re going to type or paste into your terminal (OSX or Linux) or Powershell (Windows).
**IMPORTANT NOTES:**
IMPORTANT NOTE:
This walkthrough is going to be pretty pedantic. I’m assuming you’re reading it because you have no idea how to get a Docker container going, so I’m proceeding from the assumption that you want to be walked through every little detail. You’re going to deliberately cause errors and then fix them as you go through it. This is to help you understand what exactly is going on behind the scenes so that when you see these sorts of problems in the wild you will have some background to understand what’s happening. If I only give you the happy path walkthrough, then when you make a typo later on you’ll have no idea where that typo might be or why it’s breaking things.
1. This walkthrough is going to be pretty pedantic. I’m assuming you’re reading it because you have no idea how to get a Docker container going, so I’m proceeding from the assumption that you want to be walked through every little detail. You’re going to deliberately cause errors and then fix them as you go through it. This is to help you understand what exactly is going on behind the scenes so that when you see these sorts of problems in the wild you will have some background to understand what’s happening. If I only give you the happy path walkthrough, then when you make a typo later on you’ll have no idea where that typo might be or why it’s breaking things.
I am assuming you do not have any of these tools already installed. When writing this up I started with a brand new Windows 10 install.
2. I am assuming you do not have any of these tools already installed. When writing this up I started with a brand new Windows 10 install.
I'm also assuming you are doing this on a computer, not through a NAS interface or the like. You can do all this through something like the Synology NAS UI or Portainer or the like, but those aren't documented here. This uses the docker command line because it works the same on all platforms.
3. I'm also assuming you are doing this on a computer, not through a NAS interface or the like. You can do all this through something like the Synology NAS UI or Portainer or the like, but those aren't documented here. This uses the docker command line because it works the same on all platforms.
You may want to take an hour to get familiar with Docker fundamentals with the [official tutorial](https://www.docker.com/101-tutorial/).
4. You may want to take an hour to get familiar with Docker fundamentals with the [official tutorial](https://www.docker.com/101-tutorial/).
5. DO NOT MAKE ANY CHANGES BELOW if you want this to just work. Don't change the docker image [`linuxserver.io` will not work for this, for example]; don't change the paths, etc.
DO NOT MAKE ANY CHANGES BELOW if you want this to just work. Don't change the docker image [`linuxserver.io` will not work for this, for example]; don't change the paths, etc.
### Installing Docker.
@ -57,13 +56,17 @@ The Docker install is discussed here: [Installing Docker](https://docs.docker.co
Once you have Docker installed, test it at the command line with:
[type this into your terminal]
```
docker run --rm hello-world
```
You should see something that starts with:
```
Hello from Docker!
This message shows that your installation appears to be working correctly.
...
```
@ -73,7 +76,7 @@ If that doesn't work, stop here until you fix that. Diagnoing and repairing Doc
#### Important note on Docker images
This tutorial uses the official image, and you should, too. Don't change `meisnate12/plex-meta-manager` to the `linuxserver.io` image or any other; the lsio image specifically has [idiosyncracies](images.md) that will prevent this walkthrough from working. The official image *will* behave exactly as documented below. Others very possibly won't.
This tutorial uses the official image, and you should, too. Don't change `meisnate12/plex-meta-manager` to the `linuxserver.io` image or any other; other images may have [idiosyncracies](images.md) that will prevent this walkthrough from working. The official image *will* behave exactly as documented below. Others very possibly won't.
The great thing about Docker is that all the setup you'd have to do to run PMM is already done inside the docker image.
@ -140,55 +143,82 @@ pwd
This will display a full path:
````{tab} Linux
<br/>
```
/home/YOURUSERNAME/plex-meta-manager
```
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
```
/Users/YOURUSERNAME/plex-meta-manager
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
```
C:\Users\YOURUSERNAME\plex-meta-manager
```
<br/>
````
Add "config" onto the end of that to get the host path to your config directory, for example:
````{tab} Linux
<br/>
```
/home/YOURUSERNAME/plex-meta-manager/config
```
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
```
/Users/YOURUSERNAME/plex-meta-manager/config
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
```
C:\Users\YOURUSERNAME\plex-meta-manager\config
```
<br/>
````
You'll need to add this to the docker command every time you run it, like this:
````{tab} Linux
<br/>
```
docker run --rm -it -v "/home/YOURUSERNAME/plex-meta-manager/config:/config:rw" meisnate12/plex-meta-manager
```
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
```
docker run --rm -it -v "/Users/YOURUSERNAME/plex-meta-manager/config:/config:rw" meisnate12/plex-meta-manager
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
```
docker run --rm -it -v "C:\Users\YOURUSERNAME\plex-meta-manager\config:/config:rw" meisnate12/plex-meta-manager
```
<br/>
````
If you run that command now it will display a similar error to before, but without all the image loading:
@ -202,6 +232,7 @@ Note that I show the example path there.
<details>
<summary>Why did we create that `config' directory?</summary>
<br/>
This was done so that from here on in the instructions match between this walkthrough and the [Local walkthrough](local) are the same.
@ -215,27 +246,36 @@ The default config file contains a reference to a directory that will show an er
We'll create it here so the error doesn't show up later.
````{tab} Linux
<br/>
[type this into your terminal]
```
mkdir config/assets
```
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
[type this into your terminal]
```
mkdir config/assets
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
[type this into your terminal]
```
mkdir config\assets
```
<br/>
````
### Setting up the initial config file
```{include} wt/wt-01.md
```{include} wt/wt-01-basic-config.md
```
#### Editing the config template
@ -243,22 +283,30 @@ mkdir config\assets
First, make a copy of the template:
````{tab} Linux
<br/>
Get a copy of the template to edit [type this into your terminal]:
Go to [this URL](https://raw.githubusercontent.com/meisnate12/Plex-Meta-Manager/master/config/config.yml.template) using a web browser; choose the "Save" command, then save the file at:
@ -266,7 +314,7 @@ Now open the copy in an editor:
```{include} wt/wt-editor.md
```
```{include} wt/wt-02.md
```{include} wt/wt-02-config-bad-library.md
```
#### Testing the config file
@ -281,7 +329,27 @@ Then run the script again:
```{include} wt/wt-run-docker.md
```
```{include} wt/wt-03.md
```{include} wt/wt-03-lib-err-and-fix.md
```
### Creating a few sample collections.
```{include} wt/wt-04-default-intro.md
```
So let's run the script and see this happen:
```{include} wt/wt-run-docker.md
```
```{include} wt/wt-04b-default-after.md
```
### Setting up a metadata file and creating a few sample collections.
```{include} wt/wt-05-local-file.md
```
Save the file:
@ -294,12 +362,12 @@ Then run the script again:
```{include} wt/wt-run-docker.md
```
```{include} wt/wt-04.md
```{include} wt/wt-06-local-after.md
```
### Setting up a metadata file and creating a few sample collections.
### Adding Overlays to movies.
```{include} wt/wt-05.md
```{include} wt/wt-07-overlay-add.md
```
Save the file:
@ -309,27 +377,52 @@ Save the file:
Then run the script again:
```{include} wt/wt-run-docker.md
```{include} wt/wt-run-shell.md
```
```{include} wt/wt-08-overlay-after.md
```
```{include} wt/wt-09-next-steps.md
```
```{include} wt/wt-06.md
## Other Topics
### Scheduling
```{include} wt/wt-10-scheduling.md
```
### Running the container in the background:
### I want to use the develop branch
Add the `develop` tag to the image name in your run command [or wherever you specify the image in your environment]
```
docker run --rm -it -v "PMM_PATH_GOES_HERE:/config:rw" meisnate12/plex-meta-manager:develop --run
^^^^^^^
```
This may not work if you are not using the official image; for example, it does not work with the lsio image.
### I want to use the nightly branch
Add the `nightly` tag to the image name in your run command [or wherever you specify the image in your environment]
```
docker run --rm -it -v "PMM_PATH_GOES_HERE:/config:rw" meisnate12/plex-meta-manager:nightly --run
^^^^^^^
```
The docker commands in this article are creating and deleting containers.
This may not work if you are not using the official image; for example, it does not work with the lsio image.
However, you probably ultimately want a container that runs all the time, even after reboots, and wakes up to do its thing.
### I want to ensure I am using the master branch
This would be the minimal case:
Add the `latest` tag to the image name in your run command [or wherever you specify the image in your environment]
```
docker run -d \
--restart=unless-stopped \
-v PMM_PATH_GOES_HERE:/config:rw \
meisnate12/plex-meta-manager
docker run --rm -it -v "PMM_PATH_GOES_HERE:/config:rw" meisnate12/plex-meta-manager:latest --run
^^^^^^
```
That will create a container that will run in the background until you explicitly stop it, surviving reboots, and waking up every morning at 5AM to process collections.
This is the only version tag supplied by the lsio image.
There are of course [other flags you can add](../environmental), but this is the minimal command to create this container.
@ -45,23 +45,45 @@ This walkthrough involves typing commands into a command window. On Mac OS X or
IMPORTANT:
This walkthrough is assuming you are doing the entire process on the same platform; i.e. you're installing PMM and editing its config files on a single Linux, Windows, or OS X machine. It doesn't account for situations like running PMM on a Linux machine while editing the config files on your Windows box.
### Prepare a small test library
While going through this process, Plex-Meta-Manager is going to load the movies in your library, create some collections, and apply some overlays. If you have a large library, this will be very time-consuming.
For learning and testing, you would be well-advised to create a small test library of a reasonable size, where reasonable it probably below a thousand.
The author has a small library of 10 movies that is used for fast tests.
For best results, your test library will contain:
At least two comedy movies released since 2012.
At least two movies from the IMDB top 250.
At least two movies from IMDB's Popular list.
At least two movies from IMDB's Lowest Rated.
A couple different resolutions among the movies.
That will ensure there's something to go into each of the example collections that will be created.
### Starting up your terminal.
Since most of this is typing commands into a terminal, you'll need to have a terminal open.
````{tab} Linux
<br/>
If your Linux system is remote to your computer, connect to it via SSH. That SSH session is the terminal you will be using, so leave it open.
If you are running this on a desktop Linux machine, start up the Terminal application. That window will be the terminal you will type commands into throughout this walkthrough, so leave it open.
<br/>
````
````{tab} OS X
````{tab} OS X:
Open the Terminal app; this window will be the place you type commands throughout this walkthrough, so leave it open. The Terminal app is in Applications -> Utilities.
You can also use iTerm or some other terminal app if you wish. If you don't know what that means, use Terminal.
<br/>
````
````{tab} Windows
````{tab} Windows:
Use the Start menu to open PowerShell. This will be the window into which you type commands throughout this walkthrough, so leave it open.
<br/>
````
### Installing Python.
@ -72,39 +94,33 @@ First let's check if it's installed already [type this into your terminal]:
```
python3 --version
python --version
```
If one of these doesn't return `3.7.0` or higher, you'll need to get Python 3 installed.
If this doesn't return `3.7.0` or higher, you'll need to get Python 3 installed.
````{tab} Linux
<br/>
Describing a python install for any arbitrary linux is out of scope here, but if you're using Ubuntu, [this](https://techviewleo.com/how-to-install-python-on-ubuntu-linux/) might be useful.
<br/>
````
````{tab} OS X
````{tab} OS X:
Follow the instructions here: [Installing Python 3 on Mac OS X](https://docs.python-guide.org/starting/install3/osx/)
<br/>
````
````{tab} Windows
Go to http://www.python.org/download and download one less than the latest version of Python for Windows in 32 or 64-bit as appropriate for your system [probably 64-bit]. As this is written, that's 3.10. The latest version of Python is 3.11, and there is one piece of PMM that is not ready for 3.11. It will be some time soon, but that isn't under PMM control, so to be safe, grab one back from the latest.
````{tab} Windows:
Go to http://www.python.org/download and download the latest version of Python for Windows in 32 or 64-bit as appropriate for your system [probably 64-bit]. As this is written, that's 3.10.4.
Once downloaded, run the installer. Tick “Add to path” checkbox at the bottom and click “Install Now”.
For Windows 10, you will need to enable scripts in PowerShell. Follow the instructions [here](https://windowsloop.com/enable-powershell-scripts-execution-windows-10) to do so. If you skip this step you're going to hit a hard stop in a little bit.
<br/>
````
Once you've completed the install, verify that will will work on the command line. Close the terminal or Powershell window and open a new one, then type this into your terminal:
```
python3 --version
python --version
```
If one of these doesn't return the version you just downloaded and installed, back up and check your work above.
---
### Installing git
To copy the Plex-Meta-Manager code to your machine, we'll be using git. This may be installed on Mac or Linux, and probably is not in Windows.
To copy the Plex-Meta-Manager code to your machine, we'll be using git. This may be installed on Mac or Linux, and probably isn't in Windows.
First let's check if it's installed already [type this into your terminal]:
@ -115,12 +131,17 @@ git --version
If this doesn't return a version number, you'll need to get git installed.
````{tab} Linux
<br/>
The git install is discussed here: [Download for Linux and Unix](https://git-scm.com/download/linux)
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
The git install is discussed here: [Git - Downloading Package](https://git-scm.com/download/mac)
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
Download the installer from [here](https://git-scm.com/download/windows)
Run the install; you can probably just accept the defaults and click through except for the step that asks you to choose an editor; you probably want to choose something other than the default there:
@ -128,16 +149,9 @@ Run the install; you can probably just accept the defaults and click through exc
This install comes with its own command line interface. **Do not use this interface in this walkthrough**. Continue to do everything here in Powershell.
<br/>
````
Once you've completed the install, verify that will will work on the command line. Close the terminal or Powershell window and open a new one, then type this into your terminal:
```
git --version
```
If that doesn't return the version you just downloaded and installed, back up and check your work above.
---
### Retrieving the Plex-Meta-Manager code
@ -167,38 +181,53 @@ There are parts of the code that are assuming and expecting that you will be in
<details>
<summary>What did that do?</summary>
<br/>
```
cd ~
```
This changes to your home directory, which will be something like `/home/yourname` or `/Users/yourname` or `C:\Users\YourName` depending on the platform.
This uses `git` to make a copy of (`clone`) the PMM code from where it is stored on `github`.
```
cd Plex-Meta-Manager
```
This moves into the directory that was created by the `clone` command.
</details>
Later on you can move it elsewhere if you want, but for now put it there. This will ensure that everything to follow works just like it says here. Presumably you’re reading this because the other docs are unclear to you. Don’t make unilateral changes to my assumptions while doing this.
<details>
<summary>Why use git instead of downloading the release ZIP?</summary>
<br/>
Retrieving the code with `git` makes updating simpler. When you want to update to the newest version, you can go into this directory and type:
```
git pull
```
No need to download a new ZIP, uncompress it, etc.
Also, if you are asked to [or want to] switch to the latest develop or nightly code, you can do so with:
```
git checkout develop
```
```
git checkout nightly
```
</details>
---
@ -208,46 +237,67 @@ Later on you can move it elsewhere if you want, but for now put it there. This
This walkthrough is going to use a "virtual environment", since that provides a simple way to keep the requirements for a given thing self-contained; think of it as a "sandbox" for this script. It also provides a clean way to recover from mistakes, and keeps the host system clean.
````{tab} Linux
<br/>
[type this into your terminal]
```
python3 -m venv pmm-venv
```
If you see an error like:
```
Error: Command '['/home/mroche/Plex-Meta-Manager/pmm-venv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
```
You probably need to make sure the Python 3.9-specific virtualenv support library is installed:
[type this into your terminal]
```
sudo apt-get install python3.9-venv
```
Then try the original venv command above again.
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
[type this into your terminal]
```
python3 -m venv pmm-venv
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
[type this into your terminal]
```
python -m venv pmm-venv
```
If you see:
```
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
```
You apparently didn't check the “Add to path” checkbox above under [installing Python](#installing-python). "Repair" your Python install and check "add python to environment variables".
<br/>
````
<details>
<summary>What did that do?</summary>
<br/>
```
python3 -m venv pmm-venv
```
This tells Python3 to use the `venv` module to create a virtual environment called `pmm-venv`. The only visible effect will be the creation of a `pmm-venv` directory.
</details>
That command will not produce any output if it works; it will display an error if a problem occurs. If everything is fine, you will be looking at something like this:
@ -262,23 +312,32 @@ If you aren't looking at an error, you're ready to move on.
That will create the virtual environment, and then you need to activate it:
````{tab} Linux
<br/>
[type this into your terminal]
```
source pmm-venv/bin/activate
```
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
[type this into your terminal]
```
source pmm-venv/bin/activate
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
[type this into your terminal]
```
.\pmm-venv\Scripts\activate
```
If you see something like this:
```powershell
.\pmm-venv\Scripts\activate : File C:\Users\mroche\Plex-Meta-Manager\pmm-venv\Scripts\Activate.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink LinkID=135170.
You apparently skipped the "enable scripts in Powershell" step above under [installing Python](#installing-python) for Windows.
You will need to take care of that before moving on. Follow the instructions [here](https://windowsloop.com/enable-powershell-scripts-execution-windows-10).
Once you have done that, try the activation step again.
<br/>
````
That command will not produce any output if it works; it will display an error if a problem occurs.
@ -307,8 +368,10 @@ Note that the prompt now shows the name of the virtual environment. You may not
<details>
<summary>What did that do?</summary>
<br/>
This tells Python to make the virtual environment "active", which means to use the copy of python that is available there, install all support libraries there, etc. This keeps the PMM code and its runtime environment totally separate from your host machine's environment.
</details>
An advantage of doing this in a virtual environment is that in the event something goes wrong with this part of the setup, you can delete that pmm-venv directory and do the setup again.
@ -316,22 +379,31 @@ An advantage of doing this in a virtual environment is that in the event somethi
**IMPORTANT: In the future, when you want to run the script, you will need to do this "activation" step every time. Not the venv creation, just the activation**:
````{tab} Linux
<br/>
[type this into your terminal]
```
source pmm-venv/bin/activate
```
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
[type this into your terminal]
```
source pmm-venv/bin/activate
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
[type this into your terminal]
```
.\pmm-venv\Scripts\activate
```
<br/>
````
### Installing requirements
@ -365,8 +437,10 @@ Don't worry about the WARNING about `pip version thus-and-such` if it comes up.
<details>
<summary>What did that do?</summary>
<br/>
This told Python to use the `pip` module to install some libraries that PMM needs.
</details>
Let’s make sure it’s working so far.
@ -391,27 +465,36 @@ The default config file contains a reference to a directory that will show an er
We'll create it here so the error doesn't show up later.
````{tab} Linux
<br/>
[type this into your terminal]
```
mkdir config/assets
```
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
[type this into your terminal]
```
mkdir config/assets
```
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
[type this into your terminal]
```
mkdir config\assets
```
<br/>
````
### Setting up the initial config file
```{include} wt/wt-01.md
```{include} wt/wt-01-basic-config.md
```
#### Editing the config template
@ -419,22 +502,31 @@ mkdir config\assets
First, make a copy of the template. This is going to create a copy of the base template that you can then edit. You only need to do this once.
## This file is a template remove the .template to use the file
libraries: # This is called out once within the config.yml file
Movies: # Each library must match the Plex library name
metadata_path:
- pmm: basic # This is a file within the defaults folder in the Repository
- pmm: imdb # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
overlay_path:
- remove_overlays: false # Set this to true to remove all overlays
- pmm: ribbon # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
TV Shows:
metadata_path:
- pmm: basic # This is a file within the defaults folder in the Repository
- pmm: imdb # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
overlay_path:
- remove_overlays: false # Set this to true to remove all overlays
- pmm: ribbon # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
Anime:
metadata_path:
- pmm: basic # This is a file within the defaults folder in the Repository
- pmm: anilist # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
Music:
metadata_path:
- file: config/Music.yml # This is a local file THAT YOU MIGHT CREATE
```
You will ultimately need an entry here for each of the libraries on which you want PMM to act. Those top-level elements [Movies, TV Shows, Anime, Music] are names of libraries on your Plex server.
For now, delete the “TV Shows”, “Anime”, and "Music" sections and change the name of the “Movies” section to “Movies-NOSUCHLIBRARY":
```yaml
libraries:
Movies-NOSUCHLIBRARY: ## <<<CHANGETHISLINE
metadata_path:
- pmm: basic # This is a file within the defaults folder in the Repository
- pmm: imdb # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
```
This is intended to cause an error for illustration that you will then fix.
## This file is a template remove the .template to use the file
libraries: # This is called out once within the config.yml file
Movies: # Each library must match the Plex library name
metadata_path:
- file: config/Movies.yml # This is a local file on the system
- folder: config/Movies/ # This is a local directory on the system
- pmm: basic # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
- pmm: imdb # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
overlay_path:
- remove_overlays: false # Set this to true to remove all overlays
- file: config/Overlays.yml # This is a local file on the system
- pmm: ribbon # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
TV Shows:
metadata_path:
- file: config/TVShows.yml
- folder: config/TV Shows/
- pmm: basic # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
- pmm: imdb # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
overlay_path:
- remove_overlays: false # Set this to true to remove all overlays
- file: config/Overlays.yml # This is a local file on the system
- pmm: imdb_top_250 # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
Anime:
metadata_path:
- file: config/Anime.yml
- pmm: basic # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
- pmm: anilist # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
Music:
metadata_path:
- file: config/Music.yml
```
You will ultimately need an entry here for each of the libraries on which you want PMM to act. Those top-level elements [Movies, TV Shows, Anime, Music] are names of libraries on your Plex server.
For now, delete the “TV Shows”, “Anime”, and "Music" sections and change the name of the “Movies” section to “Movies-NOSUCHLIBRARY":
```yaml
libraries:
Movies-NOSUCHLIBRARY: ## <<<CHANGETHISLINE
metadata_path:
- file: config/Movies.yml # This is a local file on the system
- folder: config/Movies/ # This is a local directory on the system
- pmm: basic # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
- pmm: imdb # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
overlay_path:
- remove_overlays: false # Set this to true to remove all overlays
- file: config/Overlays.yml # This is a local file on the system
- pmm: imdb_top_250 # This is a file within the https://github.com/meisnate12/Plex-Meta-Manager-Configs Repository
```
This is intended to cause an error for illustration that you will then fix.
@ -24,7 +24,7 @@ I’ve removed some of the lines for space, but have left the important bits:
You can see there that PMM found its config file, was able to connect to TMDb, was able to connect to Plex, and then failed trying to read the “Movies-NOSUCHLIBRARY" library, which of course doesn’t exist.
Open the config file again and change "Movies-NOSUCHLIBRARY" to reflect *your own* Movie library in Plex. Then delete all but the first line under the "metadata_path” heading. A few of them will create sets of collections, and we just want to create a few as examples.
Open the config file again and change "Movies-NOSUCHLIBRARY" to reflect *your own* Movie library in Plex.
My Movies library is called “Main Movies", so mine looks like this:
@ -32,5 +32,7 @@ My Movies library is called “Main Movies", so mine looks like this:
libraries:
Main Movies: ## <<<CHANGETHISLINE
metadata_path:
- file: config/Movies.yml
- pmm: basic # This is a file within the defaults folder in the Repository
- pmm: imdb # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
Depending on the size of the library, this may take a while.
As it builds the collections, you should see a fair amount of logging about which movies are being added and which ones aren’t found. Once it completes, go to Plex, go to your Movies library, and click “Collections” at the top.
On my test library, this created four collections. You may see fewer depending on what specific movies are in that library.
Perhaps you can do everything you want with the defaults. You can investigate what they can provide under the "Defaults" heading at the top.
If the default metadata files do not allow you to create the collections you want, you can define your own collections in your own metadata files to do whatever you like within the capabilities of PMM. We will create a simple collection that will contain 20 comedy movies since 2012.
First, open the metadata file [this will create the file if it doesn't already exist]:
````{tab} Linux
<br/>
[type this into your terminal]
```
nano "config/Movies.yml"
```
<br/>
````
````{tab} OS X:
<br/>
[type this into your terminal]
```
nano "config/Movies.yml"
```
<br/>
````
````{tab} Windows:
<br/>
[type this into your terminal]
```
notepad "config\Movies.yml"
```
<br/>
````
In this file, add the following, exactly as it is shown here:
```yaml
collections:
Recent Comedy:
plex_search:
all:
genre: Comedy
year.gte: 2012
limit: 20
```
Save the file:
```{include} wt/wt-save.md
```
Next, add a reference to this file to your config file.
Open the config file again and add the last line shown below:
```yaml
libraries:
Main Movies: ## <<<CHANGETHISLINE
metadata_path:
- pmm: basic # This is a file within the defaults folder in the Repository
- pmm: imdb # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
- file: config/Movies.yml
```
That line needs to match the path you used when you created the file a moment ago.
Now we have to set up that metadata file that PMM just complained about.
This metadata file contains definitions of the actions you want PMM to take; these can be things like creating collections or playlists, adding overlays, changing things like posters, etc. You can find lots of examples [here](https://github.com/meisnate12/Plex-Meta-Manager-Configs) and throughout the wiki.
For now we’re going to create a few collections so you can watch the process work, then you’re on your own to create whatever others you want.
First, open the metadata file [this will create the file if it doesn't already exist]:
````{tab} Linux
[type this into your terminal]
```
nano "config/Movies.yml"
```
````
````{tab} OS X
[type this into your terminal]
```
nano "config/Movies.yml"
```
````
````{tab} Windows
[type this into your terminal]
```
notepad "config\Movies.yml"
```
````
In this file, add the following, exactly as it is shown here:
```yaml
templates:
Actor:
actor: tmdb
tmdb_person: <<person>>
tmdb_actor_details: <<person>>
sort_title: +_<<collection_name>>
sync_mode: sync
collection_order: release
collection_mode: hide
collections:
Bill Murray:
template: {name: Actor, person: 1532}
Best of the 1980s:
tmdb_discover:
primary_release_date.gte: 01/01/1980
primary_release_date.lte: 12/31/1989
with_original_language: en
sort_by: popularity.desc
limit: 100
summary: A collection of the Top Content of the 1980s
I chose a letterboxd list for the last one since trakt requires authentication and again, I didn’t want to complicate this walkthrough.
This is going to create three collections. One contains movies that feature Bill Murray. One is up to 100 movies that came out in the 1980s sorted by popularity. The last are movies that appear on a list of good endings according to Vulture.
The first one is based on a template to illustrate that concept. If you wanted to create a collection for another actor you just have to copy and edit those two lines [the ID comes from TMDb]. All the other config details come from the template.
You should see that the metadata file gets loaded:
```
| Loading Metadata File: config/Movies.yml
| Metadata File Loaded Successfully
```
As it builds the collection, you should see a fair amount of logging about which movies are being added and which ones aren’t found. Once it completes, go to Plex, go to your Movies library, and click “Collections” at the top.
You should see the new collection:
When you click into each, you’ll see the movies that PMM added to each collection.
Each time you run the script, new movies that match the collection definitions will be added. For example, if you don’t have “The ShawShank Redemption” now, when you download it and run PMM again it will be added to the IMDB 250 collection.
This time you should see that the metadata file gets loaded:
```
| Loading Metadata File: config/Movies.yml
| Metadata File Loaded Successfully
```
And this time it will catalog all your movies. This could take a while depending on how many movies are in that library.
Once this mapping is complete it will move on to build those three collections.
As it builds the collections, you should see a fair amount of logging about which movies are being added and which ones aren’t found. Once it completes, go to Plex, go to your Movies library, and click “Collections” at the top.
You should see the three new collections:
When you click into each, you’ll see the movies that PMM added to each collection.
Each time you run the script, new movies that match the collection definition will be added. For example, if you don’t have “The Razors’ Edge” now, when you download it and run PMM again it will be added to the Bill Murray collection.
If you download any of the missing 22 movies on the Vulture list, running PMM would add them to that collection. And so on.
### What comes next:
Delete these three collections if you want, from both Plex and the metadata file [`config/Movies.yml`].
Edit `Movies.yml` to reflect the actions you want PMM to perform on *your* libraries.
TV Shows and other libraries work the same way as you've seen above. Create a section under `Libraries:` in the config.yml, create a metadata file, define collections, run the script.
Investigate the rest of the wiki to learn about everything Plex-Meta-Manager can do for you.
While it runs this time you should see the previous collections go by pretty quickly, since they aren't changing, and then a lot of logging as PMM decides which overlays apply to which movies.
This may take quite a while depending on the size of this library.
Eventually, you'll see it start applying overlays to all your movies:
If you want to remove those overlays, open the config file, change the value of `remove_overlays` to `true`, and rerun PMM.
```
overlay_path:
- remove_overlays: true
- pmm: resolution
```
If you want to remove those collections, open the config file, remove or comment out [add `#` to the beginning] any or all of those lines under `metadata_path`, and delete the collections manually from Plex.
```yaml
libraries:
Main Movies:
metadata_path:
# - pmm: basic # This is a file within the defaults folder in the Repository
# - pmm: imdb # This is a file within the defaults folder in the Repository
# see the wiki for how to use local files, folders, URLs, or files from git
# - file: config/Movies.yml
overlay_path:
- remove_overlays: false
- pmm: resolution
```
Edit `Movies.yml` to reflect the actions you want PMM to perform on *your* libraries.
TV Shows and other libraries work the same way as you've seen above. Create a section under `Libraries:` in the config.yml, refer to default files or create a metadata file, define collections, run the script.
Investigate the rest of the wiki to learn about everything Plex-Meta-Manager can do for you.
### Runtime and Environment Flags
The command in this walkthrough will run all collections and libraries immediately. If you want to modify that behavior to run just one or some collections, or just one library, or just overlays or the like, review the [Run Commands & Environment Variables](../../environmental.md).
### Creating Collections, Overlays, Playlists, etc.
These things are all generally defined in metadata files that are referred to in the config file. The starting point for creating these files is [here](../../../metadata/metadata.md).
The commands you've been using in this walkthrough runn Plex-Meta-Manager immediately.
Plex Meta Manager also features multiple layers of scheduling, which you can leverage to
You can run PMM in the background, telling it to wake up and process your libraries at fixed times during the day. The default behavior in this regard is to wake up at 5AM and process the config.
You can skip using that internal schedule and just do manual runs as you have been doing throughout this walkthrough using standard tools available in your OS.
Details on setting this up are found [here](../scheduling.md).
In addition, individual items *within* the configuration can be scheduled to take place at certain times *provided PMM is running at that time*. For example, you can tell PMM only to apply overlays on Tuesdays or the like. YOu can then schedule manual runs every day at noon and overlays will only get processed when it runs on Tuesday. This sort of schedule *will not* make PMM start up if it is not already running. If you don't arrange for PMM to be run on Tuesday, your overlays would never be processed in this example.
Details on this level of scheduling are found [here](../../../metadata/details/schedule.md)
You can use any other text editor you wish, provided it saves files as PLAIN TEXT. `vi`, `emacs`, etc.
<br/>
````
````{tab} OS X
````{tab} OS X:
<br/>
[type this into your terminal]
```
@ -33,14 +36,17 @@ nano config/config.yml
I’m using `nano` here simply because it’s built into OSX. You can use any other text editor you wish, provided it saves files as PLAIN TEXT. BBedit, TextMate, VSCode, etc.
A common mistake is using TextEdit.app, which saves files as RTF by default.
<br/>
````
````{tab} Windows
````{tab} Windows:
<br/>
[type this into your terminal]
```
notepad .\config\config.yml
```
I’m using `notepad` here simply because it’s built into Windows. You can use any other text editor you wish, provided it saves files as PLAIN TEXT.
<br/>
````
From here on in, when this walkthrough says "open the config file", I mean this `nano` or `notepad` command. **Don't copy the template again**.
meisnate12
2 years ago
