Expand variables in target paths #190
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #61
Design considerations
Currently I just mix the config variables and environment variables together. For example:
config="~/config_dir_from_env" dotter deploywill results incatbeing~/.config/QuarticCatrather 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_configvs.ENV_VARS)?