MAX_CREATION_LIMIT #724

New Issue

GiteaMirror · 2025-11-02T03:34:11-06:00

GiteaMirror commented

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

Originally created by @ghost on GitHub (May 19, 2017).

Gitea version (or commit ref):25d6e2a
Git version:2.11.2
Operating system:ubuntu/docker
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

I am using the latest docker image for hosting. Have used the Postgresql linking method to setup my docker gitea installation.
After a normal setup, I login with my newly created admin account.
Then I setup SMTP source auth and change my own auth source to the newly created source.
Now I want to limit every new user that logs in to not be able to create any repositories.
Updating each and every user's setting is not feasible.
As per documentation, setting MAX_CREATION_LIMIT to zero should do the trick.

So I went back to the docker image docker exec -it gitea, performed opened the /data/gitea/conf/app.ini and set MAX_CREATION_LIMIT=0 in the repositories section just below the path variable.

Restarting with docker restart gitea though, has no affect on newly logged in users (via the SMTP source)

Originally created by @ghost on GitHub (May 19, 2017). - Gitea version (or commit ref):25d6e2a - Git version:2.11.2 - Operating system:ubuntu/docker - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I am using the latest docker image for hosting. Have used the Postgresql linking method to setup my docker gitea installation. After a normal setup, I login with my newly created admin account. Then I setup SMTP source auth and change my own auth source to the newly created source. Now I want to limit every new user that logs in to not be able to create any repositories. Updating each and every user's setting is not feasible. As per [documentation](https://docs.gitea.io/en-us/config-cheat-sheet/), setting MAX_CREATION_LIMIT to zero should do the trick. So I went back to the docker image `docker exec -it gitea`, performed opened the `/data/gitea/conf/app.ini` and set `MAX_CREATION_LIMIT=0` in the repositories section just below the path variable. Restarting with `docker restart gitea` though, has no affect on newly logged in users (via the SMTP source)

GiteaMirror added the type/bug label 2025-11-02 03:34:11 -06:00

GiteaMirror closed this issue

2025-11-02 03:34:12 -06:00

GiteaMirror commented

2025-11-02 03:34:12 -06:00

@appleboy commented on GitHub (May 19, 2017):

@exp10r3r Please see the PR https://github.com/go-gitea/gitea/issues/1762

@appleboy commented on GitHub (May 19, 2017): @exp10r3r Please see the PR https://github.com/go-gitea/gitea/issues/1762

GiteaMirror referenced this issue

2025-11-02 11:49:00 -06:00

[PR #724] [MERGED] Add option to app.ini to enable local import paths #15542

Sign in to join this conversation.