Ability to set user limits #569

New Issue

GiteaMirror · 2025-11-02T03:28:26-06:00

GiteaMirror commented

2025-11-02 03:28:26 -06:00

Originally created by @strk on GitHub (Mar 23, 2017).

It would be useful to set per-user (or per user-group) limits, things like:

Allowed disk space occupation for repositories
Number of PR/issues/comments per day/week/month/total

Originally created by @strk on GitHub (Mar 23, 2017). It would be useful to set per-user (or per user-group) limits, things like: - Allowed disk space occupation for repositories - Number of PR/issues/comments per day/week/month/total

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 03:28:26 -06:00

GiteaMirror commented

2025-11-02 03:28:27 -06:00

@bkcsoft commented on GitHub (Apr 18, 2017):

number of issues/comments isn't really useful in any setup, attachment restrictions would be better in that case (I think we have those already). As for disk-space and how many repos one user/org can have, 👍

@bkcsoft commented on GitHub (Apr 18, 2017): number of issues/comments isn't really useful in any setup, attachment restrictions would be better in that case (I think we have those already). As for disk-space and how many repos one user/org can have, 👍

GiteaMirror commented

2025-11-02 03:28:27 -06:00

@strk commented on GitHub (Apr 18, 2017):

Number (and size) of issues/comments affect disk space (think of a
comment flooding attack)

@strk commented on GitHub (Apr 18, 2017): Number (and size) of issues/comments affect disk space (think of a comment flooding attack)

GiteaMirror commented

2025-11-02 03:28:27 -06:00

@bkcsoft commented on GitHub (Apr 19, 2017):

In that case rate-limiting makes more sense, and is IMO out-of-scope for Gitea ;)

@bkcsoft commented on GitHub (Apr 19, 2017): In that case rate-limiting makes more sense, and is IMO out-of-scope for Gitea ;)

GiteaMirror commented

2025-11-02 03:28:28 -06:00

@sbrl commented on GitHub (Apr 19, 2017):

You could protect against a flood attack with something like sshguard or fail2ban. I think that the number of repositories and the size of said repositories is the main thing that we need the option for a limit on.

@sbrl commented on GitHub (Apr 19, 2017): You could protect against a flood attack with something like sshguard or fail2ban. I think that the number of repositories and the size of said repositories is the main thing that we need the option for a limit on.

GiteaMirror commented

2025-11-02 03:28:28 -06:00

@jonasfranz commented on GitHub (Mar 11, 2018):

I've created an issue for the size limit (#3658) to better discuss / organize the design of the size limit.

@jonasfranz commented on GitHub (Mar 11, 2018): I've created an issue for the size limit (#3658) to better discuss / organize the design of the size limit.

GiteaMirror commented

2025-11-02 03:28:28 -06:00

@stale[bot] commented on GitHub (Feb 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:28:28 -06:00

@stale[bot] commented on GitHub (Feb 20, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 20, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 08:14:34 -06:00

Feed Support Overview ( RSS / Atom ) #8689

GiteaMirror referenced this issue

2025-11-02 08:15:00 -06:00

Feed Support for Releases / Tags #8702

Sign in to join this conversation.