Closed rasa closed 1 year ago
I think I must be missing some detail, but why not simply add $XDG_CONFIG_HOME/yadm/config
to the repo, and have the encryption options stored there?
Because other settings in the config file are specific to each machine, such as class. Hence the need for a "local" config and an all-systems "universal" config.
Because other settings in the config file are specific to each machine, such as class. Hence the need for a "local" config and an all-systems "universal" config.
The config options that are prefaced with local.
(like local.class
) are not stored in the $XDG_CONFIG_HOME/yadm/config
. They're stored in the git config of the local repo.
I'm sure I'm missing something here, but I'm still confused.
This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been labeled as stale for 7 days with no activity.
Is your feature request related to a problem? Please describe.
yadm has to be configured the same on every decrypting system to match the settings on the encrypting system.
Describe the solution you'd like
Add a
--universal
option toyadm config
to direct yadm to store the option in$XDG_CONFIG_HOME/yadm/universal
instead of$XDG_CONFIG_HOME/yadm/config
That way, to easily encrypt/decrypt, one runs:
on the encrypting system, and runs:
on each decrypting system.
--universal
seems better than--global
asgit config
already has this option to store config options in~/.gitconfig
. See https://git-scm.com/docs/git-config#OPTIONSWe could also add support for a
--local
option, which directs yadm to store the option in$XDG_CONFIG_HOME/yadm/config
. This would be the default if neither--local
or--universal
is specified.If there's interest, I'll draft a PR.
Describe alternatives you've considered
Do it manually.
Additional context