If I understand correctly, Gitea uses hard links for forked repositories which saves considerable amount of space. Unfortunately, gitea dump
saves each file individually because zip
cannot work with hard links and dereferences them. By that, large repositories which are forked multiple times take up a lot of space in the backup.
I propose to use tar
instead which can cope with hard links. However, I'm not sure whether this is compatible with Gitea on other systems than GNU/Linux, or how hard links work on such operating systems.
Gitea does no such thing. git clone
however does that. And it's nothing Gitea can keep track of and is just "random git magic" that we can't handle efficently in gitea dump
. And while it's not explicitly stated, gitea dump
is sort-of depricated and unmaintained in favour of #1637
@bkcsoft Thanks for working on backup
. However, I wonder why you cannot use tar instead of zip. This would preserve the magic git created while zip breaks these hard links AFAIK.
Baiscally because Windows compatibility :/
what "windows compability" ? pretty much any popular archive manager supports .tar.gz
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
This issue has been automatically closed because of inactivity. You can re-open it if needed.
Most helpful comment
what "windows compability" ? pretty much any popular archive manager supports .tar.gz