Making such a customer account restricted and granting any needed access using team membership(s) and/or collaboration(s) is a simple way to achieve that without the need to make everything private. Most repos are public (accessible/browsable by all co-workers).Īt some point, a customer or third party needs access to a specific repo and only that repo. Restricted users are limited to a subset of the content based on their organization/team memberships and collaborations, ignoring the public flag on organizations/repos etc._Įxample use case: A company runs a Gitea instance that requires login. 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
The correct path for the template(s) will be relative to the CustomPath Gitea’s custom templates must be added to the correct location or Gitea will not find and use them. Custom Templates not loading or working incorrectly See the reverse proxy guide for a solution with nginx. This error occurs when the reverse proxy limits the file upload size. SSH_EXPOSE_ANONYMOUS: if set to false, SSH links will be hidden for anonymous users File upload fails with: 413 Request Entity Too Large 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