-
Notifications
You must be signed in to change notification settings - Fork 404
Full Config Example
Graham Steffaniak edited this page Apr 12, 2025
·
43 revisions
Starting with v0.6.8, a config needs to be validated using a few simple rules:
- invalid fields are no longer supported; this helps spot typos. For example, if you type "userdefaults" instead of "userDefaults", it will let you know rather than ignoring all of your userDefault settings you intended to imply
- required fields, such as
server.sourcesand different keys based on the settings that you add.
This is slightly annoying, because it means a config that worked before may not run anymore. But, once you get your config.yaml validated and working, any future changes should have a much better experience because of this.
Since most configs will probably not work as-is anymore, I decided to take this opportunity to also move some keys into more appropriate locations.
To help with this, I wanted to provide a full config example that works in v0.6.8: