Chaz Larson
2 years ago
parent
02af08edb0
commit
b011878e3f
@ -1,13 +1,15 @@
|
||||
The commands you've been using in this walkthrough runn Plex-Meta-Manager immediately.
|
||||
The commands you've been using in this walkthrough run Plex-Meta-Manager immediately then quit.
|
||||
|
||||
Plex Meta Manager also features multiple layers of scheduling, which you can leverage to
|
||||
Plex Meta Manager also features multiple layers of scheduling, which you can leverage to control when various activities take place.
|
||||
|
||||
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 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. If you leave the `-r` off the commands you have been using in this walkthrough, that's what will happen.
|
||||
|
||||
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.
|
||||
You can control when PMM wakes up with the [time-to-run](../../../home/environmental.md) env-var/runtime flag.
|
||||
|
||||
Details on setting this up are found [here](../scheduling.md).
|
||||
- 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.
|
||||
|
||||
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 setting this up are found [here](../../../home/guides/scheduling.md).
|
||||
|
||||
Details on this level of scheduling are found [here](../../../metadata/details/schedule.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)
|
||||
|
||||
@ -1,14 +1,9 @@
|
||||
````{tab} Linux
|
||||
<br/>
|
||||
If you're using `nano`, type control-`x`, then `y`, then the enter key.
|
||||
<br/>
|
||||
````
|
||||
````{tab} OS X:
|
||||
<br/>
|
||||
If you're using `nano`, type control-`x`, then `y`, then the enter key.<br/>
|
||||
If you're using `nano`, type control-`x`, then `y`, then the enter key.
|
||||
````
|
||||
````{tab} Windows:
|
||||
<br/>
|
||||
If you're using `notepad`, type control-`s` or choose `Save` from the `File` menu.
|
||||
<br/>
|
||||
````
|
||||
|
||||
@ -0,0 +1,21 @@
|
||||
### Prepare a small test library [optional]
|
||||
|
||||
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 with this walkthrough, your test library will contain:
|
||||
|
||||
- At least two comedy movies released since 2012.
|
||||
- At least two movies from the [IMDB top 250](https://www.imdb.com/chart/top/).
|
||||
- At least two movies from [IMDB's Popular list](https://www.imdb.com/chart/moviemeter).
|
||||
- At least two movies from [IMDB's Lowest Rated](https://www.imdb.com/chart/bottom).
|
||||
- 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.
|
||||
|
||||
The advantage of the small test library is that it will reduce the time needed to see results. Running some of these default collections against a library of a few thousand movies can take hours, and for iterative testing it's useful to have something that will run in a few minutes or seconds.
|
||||
|
||||
You can set up a test library like this using symlinks without copying files.
|
||||
Loading…
Reference in new issue