Skip to content

Expand variables in target paths#190

Open
balthild wants to merge 1 commit intoSuperCuber:masterfrom
balthild:master
Open

Expand variables in target paths#190
balthild wants to merge 1 commit intoSuperCuber:masterfrom
balthild:master

Conversation

@balthild
Copy link

@balthild balthild commented Nov 6, 2024

Closes #61

Design considerations

Currently I just mix the config variables and environment variables together. For example:

[vars.variables]
config = "~/.config"

[cat]
depends = ['vars']

[cat.variables]
cat_name = 'QuarticCat'

[cat.files]
cat = '$config/$cat_name'

config="~/config_dir_from_env" dotter deploy will results in cat being ~/.config/QuarticCat rather than ~/config_dir_from_env/QuarticCat.

What do you think? Is this behavior good or it's better to separate them (e.g. config.var_in_config vs. ENV_VARS)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE] Use variables in file paths

1 participant