1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-26 09:09:36 -05:00
forgejo/routers/web/repo/setting
Gergely Nagy 67fa52dedb
feat(quota): Quota enforcement
The previous commit laid out the foundation of the quota engine, this
one builds on top of it, and implements the actual enforcement.

Enforcement happens at the route decoration level, whenever possible. In
case of the API, when over quota, a 413 error is returned, with an
appropriate JSON payload. In case of web routes, a 413 HTML page is
rendered with similar information.

This implementation is for a **soft quota**: quota usage is checked
before an operation is to be performed, and the operation is *only*
denied if the user is already over quota. This makes it possible to go
over quota, but has the significant advantage of being practically
implementable within the current Forgejo architecture.

The goal of enforcement is to deny actions that can make the user go
over quota, and allow the rest. As such, deleting things should - in
almost all cases - be possible. A prime exemption is deleting files via
the web ui: that creates a new commit, which in turn increases repo
size, thus, is denied if the user is over quota.

Limitations
-----------

Because we generally work at a route decorator level, and rarely
look *into* the operation itself, `size:repos:public` and
`size:repos:private` are not enforced at this level, the engine enforces
against `size:repos:all`. This will be improved in the future.

AGit does not play very well with this system, because AGit PRs count
toward the repo they're opened against, while in the GitHub-style fork +
pull model, it counts against the fork. This too, can be improved in the
future.

There's very little done on the UI side to guard against going over
quota. What this patch implements, is enforcement, not prevention. The
UI will still let you *try* operations that *will* result in a denial.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
2024-08-02 11:10:34 +02:00
..
avatar.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
collaboration.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
default_branch.go [ACTIONS] port scheduled actions from Gitea 2024-03-26 16:51:56 +01:00
deploy_key.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
git_hooks.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
lfs.go [PERFORMANCE] git check-attr on bare repo if supported 2024-03-28 10:52:51 +01:00
main_test.go make writing main test easier (#27270) 2023-09-28 01:38:53 +00:00
protected_branch.go [PORT] gitea#30430: Fix rename branch 500 when the target branch is deleted but exist in database 2024-04-15 16:03:09 +02:00
protected_tag.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
runners.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
secrets.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
setting.go feat(quota): Quota enforcement 2024-08-02 11:10:34 +02:00
settings_test.go Add testifylint to lint checks (#4535) 2024-07-30 19:41:10 +00:00
variables.go Move context from modules to services (#29440) 2024-03-06 12:10:43 +08:00
webhook.go [REFACTOR] webhook shared code to prevent import cycles 2024-04-04 08:24:33 +02:00