You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16 lines
1.5 KiB
16 lines
1.5 KiB
2 years ago
|
The commands you've been using in this walkthrough run Plex-Meta-Manager immediately then quit.
|
||
2 years ago
|
|
||
2 years ago
|
Plex Meta Manager also features multiple layers of scheduling, which you can leverage to control when various activities take place.
|
||
2 years ago
|
|
||
2 years ago
|
- 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.
|
||
2 years ago
|
|
||
1 year ago
|
You can control when PMM wakes up with the [time-to-run](../../../essentials/environmental.md) env-var/runtime flag.
|
||
2 years ago
|
|
||
2 years ago
|
- 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.
|
||
2 years ago
|
|
||
1 year ago
|
Details on setting this up are found [here](../scheduling.md).
|
||
2 years ago
|
|
||
2 years ago
|
- 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.
|
||
2 years ago
|
|
||
1 year ago
|
Details on this level of scheduling are found [here](../../../../builders/details/schedule.md)
|