Supermemo backup using Git - Revision history

Guillem at 10:00, 9 September 2023

2023-09-09T10:00:21Z

← Older revision		Revision as of 10:00, 9 September 2023
Line 78:		Line 78:
	<youtube>bMBk9h8WPwg</youtube>		<youtube>bMBk9h8WPwg</youtube>

	~~<youtube></youtube>~~


	<youtube>bUduYyYfreo</youtube>		<youtube>bUduYyYfreo</youtube>

Guillem: /* Synching changes made from another computer */

2023-09-09T10:00:01Z

Synching changes made from another computer

← Older revision		Revision as of 10:00, 9 September 2023
Line 53:		Line 53:

	=== Resolving conficts ===		=== Resolving conficts ===
			If you ar eusing multiple computers, it is likely you ma face marge conflicts.

	<youtube>jof8hAk4Ppc</youtube>		<youtube>jof8hAk4Ppc</youtube>
	'''~~resolve~~-conflicts''' neded when different computers used SuperMemo asynchronously.
			'''Resolve-conflicts''' neded when different computers used SuperMemo asynchronously.
	<pre>		<pre>
	git reset --hard		git reset --hard
Line 64:		Line 67:



			If you skip one or a few days, you might forget which computer you used last time. I strongly suggest to use commit naming convention for each computer you use so you know which computer has the current state of your collection, in other words, which computer you used last time with SuperMemo.

	<youtube>X7mghohxYDI</youtube>		<youtube>X7mghohxYDI</youtube>

Guillem at 09:56, 9 September 2023

2023-09-09T09:56:46Z

← Older revision		Revision as of 09:56, 9 September 2023
Line 53:		Line 53:

	=== Resolving conficts ===		=== Resolving conficts ===
			<youtube>jof8hAk4Ppc</youtube>
	'''resolve-conflicts''' neded when different computers used SuperMemo asynchronously.		'''resolve-conflicts''' neded when different computers used SuperMemo asynchronously.
	<pre>		<pre>
Line 63:		Line 64:


	<youtube>~~jof8hAk4Ppc~~</youtube>
			<youtube>X7mghohxYDI</youtube>


Line 70:		Line 72:

	<youtube>bMBk9h8WPwg</youtube>		<youtube>bMBk9h8WPwg</youtube>

			<youtube></youtube>


			<youtube>bUduYyYfreo</youtube>

Guillem at 09:53, 9 September 2023

2023-09-09T09:53:35Z

← Older revision		Revision as of 09:53, 9 September 2023
Line 2:		Line 2:
	== SuperMemo is friendly for GIT ==		== SuperMemo is friendly for GIT ==

	* SuperMemo data structure is spread across many tiny files and folders, instead of one big file like Anki collection database.		* [[File:SM collection file count and size.png\|thumb\|Screenshot of files inside my main SuperMemo collection. There are 23137 HTML files, basically rich text for elements, only need 235.5MB, that means each file has a filesize of 10 KB.]]SuperMemo data structure is spread across many tiny files and folders, instead of one big file like Anki collection database.
	** HTML files are relatively small.		** HTML files are relatively small.
	** Every file change is saved, so if you change a big file often, you would need rediculously huge storage for git. Imagine 20 copies of 100mb file vs 400 copies of a 150kb file.		** Every file change is saved, so if you change a big file often, you would need rediculously huge storage for git. Imagine 20 copies of 100mb file vs 400 copies of a 150kb file.
	[[File:SM collection file count and size.png\|thumb\|border\|Screenshot of files inside my main SuperMemo collection. There are 23137 HTML files, basically rich text for elements, only need 235.5MB, that means each file has a filesize of 10 KB.]]

	* GIT saves every file in one commit (backup), so there are:		* GIT saves every file in one commit (backup), so there are:

Guillem at 09:53, 9 September 2023

2023-09-09T09:53:04Z

← Older revision		Revision as of 09:53, 9 September 2023
Line 5:		Line 5:
	** HTML files are relatively small.		** HTML files are relatively small.
	** Every file change is saved, so if you change a big file often, you would need rediculously huge storage for git. Imagine 20 copies of 100mb file vs 400 copies of a 150kb file.		** Every file change is saved, so if you change a big file often, you would need rediculously huge storage for git. Imagine 20 copies of 100mb file vs 400 copies of a 150kb file.
	[[File:SM collection file count and size.png\|thumb]]		[[File:SM collection file count and size.png\|thumb\|border\|Screenshot of files inside my main SuperMemo collection. There are 23137 HTML files, basically rich text for elements, only need 235.5MB, that means each file has a filesize of 10 KB.]]

	* GIT saves every file in one commit (backup), so there are:		* GIT saves every file in one commit (backup), so there are:

Guillem at 09:51, 9 September 2023

2023-09-09T09:51:55Z

← Older revision		Revision as of 09:51, 9 September 2023
Line 1:		Line 1:
	~~[[File:SM collection file count and size.png\|thumb]]~~

	== SuperMemo is friendly for GIT ==		== SuperMemo is friendly for GIT ==
Line 6:		Line 5:
	** HTML files are relatively small.		** HTML files are relatively small.
	** Every file change is saved, so if you change a big file often, you would need rediculously huge storage for git. Imagine 20 copies of 100mb file vs 400 copies of a 150kb file.		** Every file change is saved, so if you change a big file often, you would need rediculously huge storage for git. Imagine 20 copies of 100mb file vs 400 copies of a 150kb file.
			[[File:SM collection file count and size.png\|thumb]]

	* GIT saves every file in one commit (backup), so there are:		* GIT saves every file in one commit (backup), so there are:
	** No stray files unlike cloud drives, which could leave one or two files hanging; if they happen to be important files, this could corupt your whole collection.		** No stray files unlike cloud drives, which could leave one or two files hanging; if they happen to be important files, this could corupt your whole collection.

Guillem: /* SuperMemo is friendly for GIT */

2023-09-09T09:51:32Z

SuperMemo is friendly for GIT

← Older revision		Revision as of 09:51, 9 September 2023
Line 1:		Line 1:
			[[File:SM collection file count and size.png\|thumb]]

	== SuperMemo is friendly for GIT ==		== SuperMemo is friendly for GIT ==

Guillem: /* Seting up a Git backup using Gitlab */

2023-09-09T09:45:41Z

Seting up a Git backup using Gitlab

← Older revision		Revision as of 09:45, 9 September 2023
Line 31:		Line 31:
	<youtube>4aq_Bo4zcfw</youtube>		<youtube>4aq_Bo4zcfw</youtube>

			I strongly 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.
	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 ===		=== Synching made with current computer i.e. updating backup ===

Guillem at 09:45, 9 September 2023

2023-09-09T09:45:06Z

← Older revision		Revision as of 09:45, 9 September 2023
Line 1:		Line 1:
	~~{{IncrementalWarning}}~~

	== SuperMemo is friendly for GIT ==		== SuperMemo is friendly for GIT ==

Guillem at 09:42, 9 September 2023

2023-09-09T09:42:25Z

← Older revision		Revision as of 09:42, 9 September 2023
Line 1:		Line 1:
	{{IncrementalWarning}}		{{IncrementalWarning}}

			== SuperMemo is friendly for GIT ==

			* SuperMemo data structure is spread across many tiny files and folders, instead of one big file like Anki collection database.
			** HTML files are relatively small.
			** Every file change is saved, so if you change a big file often, you would need rediculously huge storage for git. Imagine 20 copies of 100mb file vs 400 copies of a 150kb file.
			* GIT saves every file in one commit (backup), so there are:
			** No stray files unlike cloud drives, which could leave one or two files hanging; if they happen to be important files, this could corupt your whole collection.
			** You can quickly respore the backup at any point in the past, without having full copies of the whole collection every time.
			** Unlike could drives, ff one file fails to be commited, the entire commit fails. So you ensure the backup is free from corruption.

			=== Pros of using GIT for backup ===

			* Once everyting is set up, you can backup your daily session within a few seconds.
			* You can use the same collection(s) in multiple computers.
			* You have local and cloud backup.
			* You can search in your GIT repository for any deleted file regardless of how long has been deleted, as long as it was after the first commit.

			=== Cons of using GIT for backup ===

			* Git often provides smaller storage spaces for free.
			** Biggest one fore free is Gitlab which provides 10gb which sould be enough for all your SuperMemo files excluding videos.
			** You can skip large files, such as videos, PDF files etc, by using the secondary storage. You may backup the secondary storage with cloud services like Google drive, One drive etc.

			* You need connection to the internet in order to sync changes.
			* It requires an initial set up that may be non-trivial for non-tech savy users.
			** This pages tries to mitigate this fear or aversion.


	== Seting up a Git backup using Gitlab==		== Seting up a Git backup using Gitlab==