Currently, we have a builtin application.yaml config with example data - while it is doable to override it, it would be cleaner to actually provide just an example of it and the user will be forced to create his own - they made decisions that the example content is acceptable for some simple usages, but they will have to take action and possibly will be forced to put a thought to the fact whether the content they have been exposed to fits their need.
Feature
Rename the current config file to indicate it is not a default for normal usage
Provide or document ways to provide user config externally.
Background
Currently, we have a builtin
application.yamlconfig with example data - while it is doable to override it, it would be cleaner to actually provide just an example of it and the user will be forced to create his own - they made decisions that the example content is acceptable for some simple usages, but they will have to take action and possibly will be forced to put a thought to the fact whether the content they have been exposed to fits their need.Feature
Rename the current config file to indicate it is not a default for normal usage Provide or document ways to provide user config externally.