Configuration
Learn about the presets.yaml file structure
Options
Available preset configuration options
Usage
How to use presets in commands
Overrides
Command-line flag precedence
Configuration File (presets.yaml)
Presets are defined in a YAML file named
presets.yaml. mkbrr searches for this file in the following locations, using the first one it finds:Structure
Thepresets.yaml file follows this structure:
Available Options
The following options can be used within thedefault section or any specific preset:
- Core Options
- Piece Settings
- File Control
- Advanced
You can find the formal JSON schema for validation here.
Using Presets
Specify the preset name using the-P (or --preset) flag with the create or modify commands:
Overriding Presets
Command-line flags take precedence over preset settings. Most flags completely override their preset counterparts, but filtering options have special behavior:- Filtering patterns are additive: Command-line patterns combine with preset patterns
Example: Combining Preset and Command-line Filters
Example: Combining Preset and Command-line Filters
Preset Definition
Command with Additional Filters
For complete details on filter processing and pattern syntax, see the Filtering documentation.
Presets with modify
modify gets each setting from the first source in this list that has it:
- The command-line flag.
- The preset.
- The torrent that you modify.
modify keeps the value from the torrent. Tracker defaults do not apply to modify. A tracker default is a value that mkbrr knows for a tracker, such as its source tag.
If the preset sets a key to false, modify uses that value. For example, no_creator: false writes the creator string.
A preset cannot remove the source, the comment, or the private flag. To remove them, use --source "", --comment "", or --no-private.
