Some things are better public. Some are not ...
Some things are better public. Some are not ...
The moment I started syncing dotfiles between my work and personal computers, I know it was an error because very different reasons. Difficulty of maintaining different OS details (Linux vs MacOS). What if leaked a private key or a sensible path. What if a pushed to the wrong place or somebody made public the wrong repository...
When reading your comment something and idea came to mind about using something like sops to encrypt paths, passwords and keys. But I'll check yours first, so to avoid to construct a bunch of stuff that you've already done :D
$ context set universe://work/customer-a/devops --update-dotfiles
will "render" and apply one set of dotfiles $ context set unvierse://work/customer-b --update-dotfiles
another set $ canvas dot apply user.name@remote.id:workspace-foo
Will apply all dotfiles of a workspace-foo (git clone repo, symlink) $ canvas dot apply user.name@remote.id:workspace-bar/shell/bashrc
will apply dotfiles of workspace-bar/shell/bashrcyes, complicated, probably hard to comprehend/reason about, work in progress
same issue of intimacy, the paths aren't encrypted.