Hacker News Reader

Comment by giancarlostoro | Hacker News Reader

I'm assuming this is only for the ones they host and not the self-hosted solution. That is insane that anyone uploads terrabytes of data into gitlab, is there an actual valid non-illegal / weird backup choice use case? Is there some big ass GIS open source project out there that could use the attention of GitLab before they nuke some vital data somehow?

View on HN

The quota includes not just the git repo, but also other services that gitlab offers. In particular the container and package registries are easy to setup in a way that accumulates a lot of data (e.g. by building and tagging a docker image in every commit and not cleaning up old images). In most cases this will be a misconfiguration and all the quota enforcement is doing is to force people to configure their projects a bit more considerate.

As far as I know, the quota itself isn't new, it just wasn't enforced in the past.

GitHub limits the package registry to 500M for free accounts, so 5G doesn't seem so bad. Git repos themselves usually don't take up that much space; all my 135 projects on GitHub are ~250M combined (quick count, could be off a bit, but roughly on that order). Even larger repos at $dayjob with daily commits typically take up a few hundred M at the most.

Basically you need to either be in the top 0.1% of highly active accounts or do something specific that requires a lot of disk space, but for most people 5G doesn't seem so unreasonable.

I'm actually somewhat curious how much of an impact this will actually have - I think I've only seen a 5 GB+ repo once or twice and they were not really source code, but mildly "abusing" github CDN/releases for downloads.

At least gitlab is not deleting any data, just rejecting pushes if you're over the limit.

You are correct in your assumption - the storage limit impacts SaaS only. I added some context on the rollout in a previous comment. https://news.ycombinator.com/item?id=32387597

Reply on news.ycombinator.com