#139 Are mirroring turned off? New mirrors can't be created

Open
opened 1 month ago by Ghost · 6 comments
Ghost commented 1 month ago
There is no content yet.
hunger commented 4 weeks ago

https://codeberg.org/Codeberg/build-deploy-gitea/src/branch/master/local_patches/disable_mirror_view.diff has the patch that removes mirroring.

I do not know the reasoning, but this seams to be intentional;-)

Maybe somebody that knows could add the reasoning and close this issue?

https://codeberg.org/Codeberg/build-deploy-gitea/src/branch/master/local_patches/disable_mirror_view.diff has the patch that removes mirroring. I do not know the reasoning, but this seams to be intentional;-) Maybe somebody that knows could add the reasoning and close this issue?
ashimokawa commented 4 weeks ago
Owner

@hunger

No, the patch you are pointing to is just disabling mirrors from being listed when viewing the most recent repos.

@varsbhat

Mirrors consume most of the disk space on our servers, most of them were created by test accounts who vanished after creating huge mirros of established open source projects, which continue updating and forever. One account even made > 100 mirros, many of them duplicates.

I am talking about auto updating, cron driven mirrors here, everyone can still just push with git push --mirror to codeberg. But the difference is that that person pushes vs forgotten automatic mirrors that update a huge project completely unrelated to the user who created it.

I guess there are still a ferw good reason for having an auto updating mirror (country bans, someone who just wants OWN not yet migrated projects to be also visible and up to date here, without any hassle).

In the end we would like to enable the creation on a per-user basis, but that code is yet to be written.

@hunger No, the patch you are pointing to is just disabling mirrors from being listed when viewing the most recent repos. @varsbhat Mirrors consume most of the disk space on our servers, most of them were created by test accounts who vanished after creating huge mirros of established open source projects, which continue updating and forever. One account even made > 100 mirros, many of them duplicates. I am talking about auto updating, cron driven mirrors here, everyone can still just push with git push --mirror to codeberg. But the difference is that that person pushes vs forgotten automatic mirrors that update a huge project completely unrelated to the user who created it. I guess there are still a ferw good reason for having an auto updating mirror (country bans, someone who just wants OWN not yet migrated projects to be also visible and up to date here, without any hassle). In the end we would like to enable the creation on a per-user basis, but that code is yet to be written.
hunger commented 4 weeks ago

@ashimokawa: I was not able to create mirrors of anything, I would have to test things out:-)

Maybe mirroring could be a members only feature? That would stop those drive-by test accounts from mirroring the world and might motivate a few more people to join?

@ashimokawa: I was not able to create mirrors of anything, I would have to test things out:-) Maybe mirroring could be a members only feature? That would stop those drive-by test accounts from mirroring the world and might motivate a few more people to join?
perflyst commented 2 weeks ago
https://blog.codeberg.org/mirror-repos-easily-created-consuming-resources-forever.html
fnetX commented 2 days ago

Hey everyone,

I see the point that mirroring is nonsense when it's not used.

I know this probably requires many patches in gitea, but isn't it more clever to sync a repository only when accessed, e. g. when a user accesses it or when it is cloned? Thus only active repositories would be mirrored and would consume ressources while inactive ones aren't processed.

Or does the ressource usage refer to the fact that mirrors waste a lot of disk space by cloning huge projects without any benefit for anyone?

Hey everyone, I see the point that mirroring is nonsense when it's not used. I know this probably requires many patches in gitea, but isn't it more clever to sync a repository only when accessed, e. g. when a user accesses it or when it is cloned? Thus only active repositories would be mirrored and would consume ressources while inactive ones aren't processed. Or does the ressource usage refer to the fact that mirrors waste a lot of disk space by cloning huge projects without any benefit for anyone?
hw commented 16 hours ago
Owner

Both disk space and traffic

Both disk space and traffic
Sign in to join this conversation.
No Milestone
No Assignees
6 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.