Codeberg/Community
54
325
Fork
You've already forked Community
12

What's the maximum repository size? #113

Closed
opened 2020年01月11日 07:13:30 +01:00 by Ghost · 1 comment

what's the top limit for repository in terms of size in codeberg?

what's the top limit for repository in terms of size in codeberg?
Member
Copy link

Hello @varshitbhat ,

we apply rules as defined in our terms of use, linked in the footer.

There is no fixed number in terms of megabytes or whatever, but use cases that harm other users and projects due to excessive resource impact will get restricted.

The purpose and intent of Codeberg.org is to enable and support original Free and Open Source Content and Software development.

For all we know from the past, human-developed content grows steadily. It took the linux kernel many years to grow to its current size. The vast majority of all Open-Source projects is even after many years only a few megabytes gzip'd source code including all version history and changes in GIT: the average repo size of all Open-Source projects is about 5MB.

Larger repositories are by all means exceptional.

Codeberg's largest repos are without exception falling into the following two categories:

  • no original content (for example we are hosting several plain mirrors from mature projects like the linux kernel or gitlab-ce, even if we are not aware of any kernel or gitlab development happening here -- both projects have dedicated communities using their own infrastructure). These have been often created by users who wanted to "test-drive" codeberg.org and validate that we are operating a mature platform ready for projects of any size. And without doubt we proved we are. Unfortunately these mirrors seem then often "forgotten", continuously getting updated automatically without anybody ever accessing them. We are currently discussing mechanisms to still allow valid use cases of mirroring but avoiding an ever-increasing number of those.
  • Some users are obviously abusing private repos to dump binary backup folders, database dumps etc. We have a whole bunch of several-GB hidden repos that do not contain any content that suggests that any meaningful future FOSS project will get kicked off out of this seed.

None of the above is jeopardizing day-to-day operation, but surely neither case is intended nor compatible with the Terms of Use. Also these are growing faster in resource usage than legitimate ones: without doubt we will have to step in sooner or later in order to ensure fairness and to focus on supporting the intended cause and mission of Codeberg: enable and facilitate development and growth of original Free and Open Source Software and Content.

Hello @varshitbhat , we apply rules as defined in [our terms of use, linked in the footer](https://codeberg.org/codeberg/org/src/branch/master/TermsOfUse.md#repositories-wikis-and-issue-trackers). There is no fixed number in terms of megabytes or whatever, but use cases that harm other users and projects due to excessive resource impact will get restricted. The purpose and intent of Codeberg.org is to enable and support original Free and Open Source Content and Software development. For all we know from the past, human-developed content grows steadily. It took the linux kernel many years to grow to its current size. The vast majority of all Open-Source projects is even after many years only a few megabytes gzip'd source code including all version history and changes in GIT: the average repo size of all Open-Source projects is about 5MB. Larger repositories are by all means exceptional. Codeberg's largest repos are without exception falling into the following two categories: - no original content (for example we are hosting several plain mirrors from mature projects like the linux kernel or gitlab-ce, even if we are not aware of any kernel or gitlab development happening here -- both projects have dedicated communities using their own infrastructure). These have been often created by users who wanted to "test-drive" codeberg.org and validate that we are operating a mature platform ready for projects of any size. And without doubt we proved we are. Unfortunately these mirrors seem then often "forgotten", continuously getting updated automatically without anybody ever accessing them. We are currently discussing mechanisms to still allow valid use cases of mirroring but avoiding an ever-increasing number of those. - Some users are obviously abusing private repos to dump binary backup folders, database dumps etc. We have a whole bunch of several-GB hidden repos that do not contain any content that suggests that any meaningful future FOSS project will get kicked off out of this seed. None of the above is jeopardizing day-to-day operation, but surely neither case is intended nor compatible with the Terms of Use. Also these are growing faster in resource usage than legitimate ones: without doubt we will have to step in sooner or later in order to ensure fairness and to focus on supporting the intended cause and mission of Codeberg: enable and facilitate development and growth of original Free and Open Source Software and Content.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#113
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?