mirrors/dotdrop
1
0
Fork 0
mirror of https://github.com/deadc0de6/dotdrop.git synced 2026-02-08 16:04:16 +00:00
Code Activity

add meta profiles doc

Browse Source
This commit is contained in:
deadc0de6
2022-08-25 23:19:30 +02:00
parent 0113708d2e
commit 348823eec7
3 changed files with 62 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/config-profiles.md vendored
View File

@@ -6,7 +6,7 @@ Entry | Description
-------- | -------------
`dotfiles` | The dotfiles associated with this profile
`import` | List of paths containing dotfile keys for this profile (absolute path or relative to the config file location; see [Import profile dotfiles from file](config-profiles.md#profile-import-entry)).
`include` | Include all elements (dotfiles, actions, (dyn)variables, etc) from another profile (See [Include dotfiles from another profile](config-profiles.md#profile-include-entry))
`include` | Include all elements (dotfiles, actions, (dyn)variables, etc) from another profile (See [Include dotfiles from another profile](config-profiles.md#profile-include-entry) and [meta profiles](howto/group-hosts.md))
`variables` | Profile-specific variables (See [Variables](config-file.md#variables))
`dynvariables` | Profile-specific interpreted variables (See [Interpreted variables](config-dynvars.md))
`actions` | List of action keys that need to be defined in the **actions** entry below (See [actions](config-actions.md))
@@ -39,7 +39,8 @@ If one profile is using the entire set of another profile, one can use
the `include` entry to avoid redundancy.
Note that everything from the included profile is made available
(actions, variables/dynvariables, etc).
(actions, variables/dynvariables, etc). See also an example in
[meta profiles](howto/group-hosts.md).
For example:
```yaml