-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Make "gitea dump" respect hardlinks for backup #2682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Gitea does no such thing. |
@bkcsoft Thanks for working on |
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. |
Description
If I understand correctly, Gitea uses hard links for forked repositories which saves considerable amount of space. Unfortunately,
gitea dump
saves each file individually becausezip
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.The text was updated successfully, but these errors were encountered: