 Forgejo v9.0, which we'll (hopefully!) start using in a few hours, ships with a new quota feature for public and shared Forgejo instances! We explained what this change will mean for you, the user (as well as some background information), in a new announcement titled "More power for you - what a storage quota will bring". https://blog.codeberg.org/more-power-for-you-what-a-storage-quota-will-bring.html 14 comments
 @Codeberg There's a repository to which several MB of video were accidentally committed and pushed. The broken commits have since been rebased away, but the storage isn't going down. Does that mean that there are still references to it in the repository β and if so, is there a way to delete them? @wizzwizz4 That's something that we get asked a lot - I think it is mentioned in our FAQ, but *something something* "wait for the garbage collector to remove the old files first". Not too sure :D ~n @wizzwizz4 No. What you're saying is also something happens sometimes, though. I don't know exactly why, but you should get in touch with ~f / Otto (best done through the Codeberg chat, or on here) and tell him to run it manually. (This is something Otto has had to do before.) ~n  @Codeberg Please don't make us guess how much storage we use by forcing us to go through each repository and manually take note of the used storage and add it up with a calculator (which seems to be the only way, AFAICS at this stage of the implementation ?) :( Give us a simple sum on our profile page with the limits and how much of that we use, please? And upstream that to forgejo :) > We will be careful in adjusting the limits, aiming for zero friction for those who use our service. I'll make sure to pass it on to Otto and let them know so that they can take your feedback into account. ~n EDIT: https://trunk.mad-scientist.club/@algernon/113340641020656961 @Codeberg if you need a developer to assist with some tooling around all these issues let me know. @chrisn We can always make use of contributors for #Forgejo. Even if it's not directly related, you can always start checking out good first issues or picking something else so that the other maintainers can do other things in the meantime. There is currently little planning for the exact feature set of the quota, but you might want to check back in two weeks when there are more concrete todos written down. ~f  @Codeberg Is there somewhere you can look up how much storage you are currently using ? (I have a few docker images in the packages storage used in CI jobs, that get updated a lot on dependency updates. I think I configured the auto-deletion of old versions correctly, but with those muti-arch images it's hard to know if it's working 100% correctly) @JonathanTreffler When viewing a repository, there is a bar that shows you the amount of commits, releases, etc... The rightmost element shows you the storage that a specific repository of yours is taking up! ~n @JonathanTreffler Hi, we don't plan to impose a quota on packages during the initial stages, because packages are... a little bit more complicated, given what you mentioned. ~n |
Gregory's Server
TL;DR: We'll eventually starting enforcing a quota to curb abuse (e.g. people creating repositories full of empty commits taking up more than a GB), nothing drastic will happen immediately, and you will be able to request more space if you do need it.
Don't panic, everything will be fine!
(Feel free to ask us questions if you have any.)