Tech wizards, could you combine a version control system like #git with a markdown based notetaking program like #obsidian to have version control over collaborative documents?
-
@malte if needs are more complex you'd want something that uses a CRDT (Conflict-free Replicated Data Type)
-
-
@malte Doesn't forges like gitlab, forgejo, github, ... already cover that if you rely on markdown or asciidoc? Including webhooks to trigger procedures like compile a new version of a book, work with changes etc=
-
@malte Doesn't forges like gitlab, forgejo, github, ... already cover that if you rely on markdown or asciidoc? Including webhooks to trigger procedures like compile a new version of a book, work with changes etc=
@blub I have no idea, I don't use any of them. Do you know the answer?
-
@malte There is a git plugin for obsidian, so it basically already works. What you would need is a more expansive fronten for git conflicts. It shouldn’t be too hard to either use a regular git tool (there are plenty), or expand/ fork the git plugin.
All the separate parts exist and are mature. The only thing really missing is a dedicated plugin. Might not be to expensive to have somebody code it for you. -
@malte There is a git plugin for obsidian, so it basically already works. What you would need is a more expansive fronten for git conflicts. It shouldn’t be too hard to either use a regular git tool (there are plenty), or expand/ fork the git plugin.
All the separate parts exist and are mature. The only thing really missing is a dedicated plugin. Might not be to expensive to have somebody code it for you.@qwxlea Cool, sounds promising. Is it this plugin you talk about? https://github.com/Vinzent03/obsidian-git
-
@qwxlea Cool, sounds promising. Is it this plugin you talk about? https://github.com/Vinzent03/obsidian-git
@malte Yes, it takes care of the plumbing, if I remember correctly it doesn’t have much of a frontend
-
@malte Yes, it takes care of the plumbing, if I remember correctly it doesn’t have much of a frontend
@qwxlea Does that mean that a non-programmer like me will likely not be able to use it? I barely know what a frontend is. I take that it is some kind of UI
-
@qwxlea Does that mean that a non-programmer like me will likely not be able to use it? I barely know what a frontend is. I take that it is some kind of UI
@malte A lot will depend onthe skill level of the people involved. Also, how confidential is the data? Can it be on a server on the net or must it be local only?
Two good contenders:
- https://github.com/silvanocerza/github-gitless-sync
- https://github.com/Vinzent03/obsidian-git
Both have cooperation, conflict resolution, and work with Obsidian. They use GitHub as server, & can be public or private. Tech level medium. As user friendly as Obsidian. -
@malte A lot will depend onthe skill level of the people involved. Also, how confidential is the data? Can it be on a server on the net or must it be local only?
Two good contenders:
- https://github.com/silvanocerza/github-gitless-sync
- https://github.com/Vinzent03/obsidian-git
Both have cooperation, conflict resolution, and work with Obsidian. They use GitHub as server, & can be public or private. Tech level medium. As user friendly as Obsidian.@qwxlea Thanks that's encouraging to hear. Then logically I should be able to learn with a bit of effort. The best would be that the notes are private and secured.
-
@qwxlea Thanks that's encouraging to hear. Then logically I should be able to learn with a bit of effort. The best would be that the notes are private and secured.
@malte Easiest (imho) would be a shared private GitHub repo, and one of the aforementioned plugins, with obsidian. This would be (afaik) free solution, and the issues can be solved by documentation. Github is well documented with text and video. It will not be hard to find outside guidance as well.
Easy to trail-run:
- subscribe to GitHub, create a private (empty!) repo
- follow the plugin docs you choose, the gitless one is simplest, but research ymmv
- test alone, then add one person, etc -
@malte Easiest (imho) would be a shared private GitHub repo, and one of the aforementioned plugins, with obsidian. This would be (afaik) free solution, and the issues can be solved by documentation. Github is well documented with text and video. It will not be hard to find outside guidance as well.
Easy to trail-run:
- subscribe to GitHub, create a private (empty!) repo
- follow the plugin docs you choose, the gitless one is simplest, but research ymmv
- test alone, then add one person, etc@qwxlea My data cooperative uses forgejo and I have fellow members who might be able to help set it up. Would that work like a private github repo?
