Supermemo backup using Git: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 35: | Line 35: | ||
<youtube>jof8hAk4Ppc</youtube> | <youtube>jof8hAk4Ppc</youtube> | ||
=== Resolving 502 HTTP error === | |||
The 502 HTTP error is triggered whent rying to sync your collection to git that is too large. The solution is what I call [[incremental commit & push]]. | |||
<youtube>bMBk9h8WPwg</youtube> |
Revision as of 11:28, 20 October 2021
Seting up a Git backup using Gitlab
I storngly discourage naming the files "pull.bat" and "push.bat" as both will be next to each other, increasing the chances to missclick leading to potential local deletions.
Synching made with current computer i.e. updating backup
sm-push.bat to sync your changes to the cloud
git add -A && git commit -m "Update" git push
Synching changes made from another computer
pull-sm.bat to get the cloud version to your computer.
git pull
Resolving conficts
resolve-conflicts neded when different computers used SuperMemo asynchronously.
git reset --hard git checkout -b temp git branch -D main git fetch git checkout main
Resolving 502 HTTP error
The 502 HTTP error is triggered whent rying to sync your collection to git that is too large. The solution is what I call incremental commit & push.