This overview lists all configuration files that are filled/changed/generated/overwritten by the yaVDR templating engine. The core of the templating engine is a script called process-template. If called with the appropriate parameters, it generates of new version of a specific configuration file based on the template snippets that are provided for the specific configuration file.

Templates are based on snippets: Fore each configuration file that should be created, there can be an unlimited number of template snippets that are concatenated by the template engine in alphabetical order (based on their filenames). Within template snippets, it is possible to use ClearSilver expressions.

FAQ

• When is the templating engine active? The content of configuration files is not only generated during installation time, but also when you configure yaVDR using the web frontend or when you update packages via apt.

• Are manual changes to a configuration file lost? Yes and no: Before the template engine overwrites a configuration file, the current content will be copied to /var/cache/yavdr/process-template-backup/. This means, if you have lost a quick'n'dirty configuration "tweak", you can look it up there.

• Is customizing of the shipped templates possible? To allow customized content in templated configuration files the concept of custom templates exists. It is explained here in more detail.

Note: There are further configuration files that are changed by yaVDR management scripts without using process-template (for example /etc/vdr/plugins/order.conf) . In some cases, the templating engine doesn't fit the needs of the structure of a specific configuration file. In those cases we have to go an alternative way.

Above you will find one page per yaVDR release or branch. "trunk" is the current developer version. The content of the tables might be outdated in case of development branches, so please check the SVN revision number given below against our SVN repository.