Configuration overview
Understand database, recording, subscription, query, rollback, and cleanup settings.
File location
plugins/DominionProtect/config.yml
The plugin generates this file on startup. After changes, run:
/domp admin reload
For database, table-structure, or dependency changes, schedule a restart and check the startup log.
Configuration groups
| Group | Responsibility | Important keys |
|---|---|---|
| language / debug | Language and diagnostics | language, debug |
| database | Pool, storage optimization, compression, and index observation | poolSize, optimizeStorageOnStartup |
| recording | Dual-buffer flushing, batch writes, and action allowlists | flushIntervalSeconds, batchSize |
| subscription | Vault fallback, default plan, and plan list | vaultUnavailableStrategy, plans |
| query | Inspect time range and page size | inspectDefaultTime, pageSize |
| rollback | Limits, preview, confirmation, and execution pacing | maxRecords, previewMaxBlocks |
| cleanup | Grace period, retention, failed files, and reclamation | gracePeriodDays, maxRetentionDays |
Editing principles
- Back up config.yml and do not change version.
- Lowering recording.batchSize or shortening the flush interval changes database pressure.
- A non-empty enabledActions list activates allowlist mode; disabledActions takes precedence.
- rollback.maxRecords is a safety limit; do not raise it simply for convenience.
- Keep optional index drops disabled until the observation period proves the index unused.
- When generated files, docs, and logs disagree, follow the generated file and the installed build.