Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to set user limits #1377

Open
strk opened this issue Mar 23, 2017 · 7 comments
Open

Ability to set user limits #1377

strk opened this issue Mar 23, 2017 · 7 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@strk
Copy link
Member

strk commented 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
@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Mar 23, 2017
@lunny lunny added this to the 2.x.x milestone Mar 23, 2017
@bkcsoft
Copy link
Member

bkcsoft commented 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, 👍

@strk
Copy link
Member Author

strk commented Apr 18, 2017 via email

@bkcsoft
Copy link
Member

bkcsoft commented Apr 19, 2017

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

@sbrl
Copy link

sbrl commented 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.

@jonasfranz
Copy link
Member

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

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Feb 6, 2019
@stale
Copy link

stale bot commented Feb 20, 2019

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

@stale stale bot closed this as completed Feb 20, 2019
@lafriks lafriks reopened this Feb 20, 2019
@stale stale bot removed the issue/stale label Feb 20, 2019
@lafriks lafriks added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Feb 20, 2019
@lunny lunny modified the milestones: 2.x.x, 1.x.x Jan 18, 2023
@lunny lunny removed this from the 1.x.x milestone Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

6 participants