forked from clara-j/media_cleaner
-
-
Notifications
You must be signed in to change notification settings - Fork 6
Configuration_File_Examples
terrelsa13 edited this page Jan 3, 2025
·
11 revisions
-
There are serveral configuration variables that can be used to customize MUMC to run exactly the way you want it to.
-
The configuration file holding these variables can be in any of these locations:
../MUMC/mumc_config.yaml
../MUMC/config/mumc_config.yaml
- When using the commandline argument
-c
/some/path/to/your_mumc_config.yaml
-
MUMC v5.8.0-beta and later no longer require having EVERY configuration variable in the
mumc_config.yaml
.- Moving forward MUMC will allow a subset of configuration variables.
- Additional configuration variables can be added individually.
- Any missing configuration variables will assume their default value.
- Setting
DEBUG: 1
will print the full config as MUMC uses it, at the top of the debug file.
- basic_settings > filter_statements
- basic_settings > filter_tags
- advanced_settings > filter_statements
- advanced_settings > behavioral_statements
- advanced_settings > blacktags
- advanced_settings > whitetags
- advanced_settings > behavioral_tags
Configuration Tree - See what each configuration option does and how to use them.
- MUMC wiki
- Install
- Files & Directories
- First Run
- Scheduled Run
- Terminology
- Configuration File Examples
- Configuration Tree
-
Additional Information
- OS Permissions
- User And Library Builder
- Played And Created Filter Statement Breakdown
- Played And Created Filter Tag Breakdown
- Dangerous Filter Statements
- Behavioral Statement Breakdown
- Behavioral Tag Breakdown
- Blacklisting vs Whitelisting
- Blacktagging vs Whitetagging
- Library Matching byId vs byPath vs byNetworkPath
- Minimum Episodes vs Minium Played Episodes
- Conditional Behavior Priorities
- Command-Line Options
- Make MUMC Run FASTERRRRRR!!!
- Known Limitations