You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Git would be a great storage backend for this because it would save the complete history, you could make changes to the data from the command line and push to the server without using the frontend, it can be easily self-hosted, and there are reliable free git servers like GitHub and GitLab.
There is a javascript implementation of a git client that runs in the browser, which might work for this: https://isomorphic-git.org/
I think it would be good to store each list as a single file in the git repo so that it is convenient to work with lists from the command line. Each non-indented line could be the start of a note and indented lines could be continuations of the same note, which makes it possible for a text editor to fold notes so that each note appears as one line when folded.
Whenever the user makes a change, it would add a change item to a queue in localStorage. Then it would attempt to do: pull, apply all changes in queue, and push.
Dealing with merge conflicts would be a little tricky, but it looks like there is already some progress on that: #63
I don't think the merge conflict handling needs to be too advanced; it could just error on the side of keeping everything and the user can manually resolve by deleting duplicate notes or redoing changes that got messed up by merges.
The text was updated successfully, but these errors were encountered:
Git would be a great storage backend for this because it would save the complete history, you could make changes to the data from the command line and push to the server without using the frontend, it can be easily self-hosted, and there are reliable free git servers like GitHub and GitLab.
There is a javascript implementation of a git client that runs in the browser, which might work for this: https://isomorphic-git.org/
I think it would be good to store each list as a single file in the git repo so that it is convenient to work with lists from the command line. Each non-indented line could be the start of a note and indented lines could be continuations of the same note, which makes it possible for a text editor to fold notes so that each note appears as one line when folded.
Whenever the user makes a change, it would add a change item to a queue in localStorage. Then it would attempt to do: pull, apply all changes in queue, and push.
Dealing with merge conflicts would be a little tricky, but it looks like there is already some progress on that: #63
I don't think the merge conflict handling needs to be too advanced; it could just error on the side of keeping everything and the user can manually resolve by deleting duplicate notes or redoing changes that got messed up by merges.
The text was updated successfully, but these errors were encountered: