Having an example YAML file is nice, but really we should write down all that's worth knowing about a DTS config file. Where this documentation lives depends on our approach: we could document the whole service in README.md, but we could also use a static site generator to stand up a documentation site for DTS. For example, I've used mkdocs for several projects and it's very simple and expressive.
Having an example YAML file is nice, but really we should write down all that's worth knowing about a DTS config file. Where this documentation lives depends on our approach: we could document the whole service in
README.md, but we could also use a static site generator to stand up a documentation site for DTS. For example, I've used mkdocs for several projects and it's very simple and expressive.