Repository size limit #515
Labels
No labels
accessibility
bug
bug
infrastructure
Codeberg
contributions welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
please chill
we are volunteers
public relations
question
question
user support
s/Forgejo
s/Forgejo/migration
s/Pages
s/Weblate
s/Woodpecker
security
service
upstream
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Codeberg/Community#515
Loading…
Add table
Add a link
Reference in a new issue
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?
Hi!
I'm considering making a mirror of my project on the codeberg pages. The main project is located on another resource, where the limit is 1GB.
The codeberd documentation vaguely says:
That's a bit of a vague answer... Still, what size can I count on to keep me out of anyone's way 100M, 500M, 1GB?
Thank you.
Could you provide a link to your project and its current resource?
I want to avoid a situation where you can say: your project can be useful, here's some more space for you (just for you)!
Don't worry, these are just static pages located on the neocities.org
They raised free space in 2017:
As of the ToS, resource limits are determined on a day-to-day basis with some common sense and considering whether the resource usage is reasonable.
Of course, working on some huge projects with many contributors is fine to use up > 1 GB (have a look at the FreeBSD repos, they use up more space), while we don't really understand why a single-contributor hobby-project needs to eat up so many resources. If it does, this is normally an issue with wrong Git usage (e.g. committing huge binary blobs, using as a personal cloud storage etc).
Please also note: Codeberg Pages is mainly intended to present your coding project, not to replace other Web Hosters. They'll do the job much better than our Git repo here. The intent is not to have everyone commit their web repo into Git, but provide a webhosting for those who are already familiar with Git.
Just adding: We won't work with fixed limits here, because we also want to prevent people from thinking "Okay, the limit is 2.5 GB, so I can go ahead and use up that space". If everyone used the limit, we would have to decrease it. If evenly spread, the limit would be around 50 MB per user I think.
Just use up as little as possible for your use-case. Don't commit binaries directly, use Git LFS instead. Consider whether your use-case fits a Git repo which is mainly a version control for text files and not really suited for sharing video courses etc