Handling single source of truth + encryption #4455
anthonyma94
started this conversation in
General
Replies: 1 comment
-
By Obsidian, do you mean https://obsidian.md/ ? If so, I don't recommend using chezmoi to manage your Obsidian data, because that data presumably changes regularly. Every change in a file managed by chezmoi is stored in git. This is why you shouldn't use chezmoi to share your shell history across machines. Instead, I would use whatever cross-machine mechanism Obsidian provides for sharing your Obsidian data across machines. If you're talking about Obsidian configuration (e.g. some kind of preferences that you change only occasionally) there is a manual solution with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a fairly advanced use case I'd like some guidance on.
I want to sync my Obsidian settings, which is stored in
<vault_path>/.obsidian/
. The vault path differs per OS, and I would like a single state for them all. I would also like to have 1 encrypted file, in<vault_path>/.obsidian/plugins/obsidian-livesync/data.json
.I read #3828 saying I can't symlink an encrypted file. Ideally I can symlink everything except that file, but I don't think that's possible. I also can't make every file in that directory a template since Obsidian controls it. How should I handle this scenario?
Beta Was this translation helpful? Give feedback.
All reactions