mirrors/dotdrop
1
0
Fork 0
mirror of https://github.com/deadc0de6/dotdrop.git synced 2026-02-09 07:09:18 +00:00
Code Activity

update doc

Browse Source
This commit is contained in:
deadc0de6
2020-09-18 10:04:00 +02:00
parent 33e02beea4
commit 067f7eea7b
5 changed files with 29 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/config.md
View File

@@ -26,6 +26,7 @@ parametrize following elements of the config:
* `import_actions`
* `import_configs`
* profiles's `import`
* profiles's `include`
`actions` and `transformations` also support the use of variables
but those are resolved when the action/transformation is executed
@@ -40,7 +41,18 @@ Following variables are available in the config files:
* environment variables: `{{@@ env['MY_VAR'] @@}}`
* dotdrop header: `{{@@ header() @@}}` (see [Dotdrop header](templating.md#dotdrop-header))
As well as all template methods (see [Available methods](templating.md#template-methods))
As well as all [template methods](templating.md#template-methods) and [template filters](templating.md#template-filters).
Note that all variables available in the config file will
then be available during [templating](templating.md).
Here are some rules on the use of variables in configs:
* [interpreted variables](config-details.md#entry-dynvariables) are executed in their own file
* [interpreted variables](config-details.md#entry-dynvariables) and
[variables](config-details.md#entry-variables) are templated before
[interpreted variables](config-details.md#entry-dynvariables) are executed
* config files do not have access to variables defined above in the import tree
## Symlink dotfiles