The current way to achieve this is to create/modify a user with a max repo creation limit of 0. NOTE: whitelisted takes precedence, so if it is non-blank then blacklisted is ignored Issue only users You can configure WHITELISTED_URIS or BLACKLISTED_URIS under in your app.ini You can configure EMAIL_DOMAIN_WHITELIST or EMAIL_DOMAIN_BLOCKLIST in your app.ini under Only allow/block certain OpenID providers
There are multiple things you can combine to prevent spammers. Swagger Example Adjusting your server for public/private use Preventing spammers In Gitea, an “active” user refers to a user that has activated their account via email.Ī “login prohibited” user is a user that is not allowed to log in to Gitea anymore Setting up loggingĪll Gitea instances have the built-in API, though it can be disabled by setting ENABLE_SWAGGER to false in the api section of your app.iniįor more information, refer to Gitea’s API docs
If certain clone options aren’t showing up (HTTP/S or SSH), the following options can be checked in your app.iniĭISABLE_HTTP_GIT: if set to true, there will be no HTTP/HTTPS linkĭISABLE_SSH: if set to true, there will be no SSH link