You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://www.codetriage.com/go-gitea/gitea)
13
13
[](https://opencollective.com/gitea)
[](https://opencollective.com/gitea)
@@ -133,8 +134,11 @@ There are multiple things you can combine to prevent spammers.
133
134
2. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY`
134
135
3. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI]({{< relref "doc/usage/command-line.en-us.md" >}}), [API]({{< relref "doc/advanced/api-usage.en-us.md" >}}), or Gitea's Admin UI
135
136
136
-
### Only allow/block certain email domains
137
-
If using OpenID, you can configure `WHITELISTED_URIS` or `BLACKLISTED_URIS` in your `app.ini`
137
+
### Only allow certain email domains
138
+
You can configure `EMAIL_DOMAIN_WHITELIST` in your app.ini under `[service]`
139
+
140
+
### Only allow/block certain OpenID providers
141
+
You can configure `WHITELISTED_URIS` or `BLACKLISTED_URIS` under `[openid]` in your `app.ini`
138
142
**NOTE:** whitelisted takes precedence, so if it is non-blank then blacklisted is ignored
Copy file name to clipboardExpand all lines: docs/content/doc/usage/backup-and-restore.en-us.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -79,3 +79,9 @@ mysql -u$USER -p$PASS $DATABASE <gitea-db.sql
79
79
# or sqlite3 $DATABASE_PATH <gitea-db.sql
80
80
service gitea restart
81
81
```
82
+
83
+
Repository git-hooks should be regenerated if installation method is changed (eg. binary -> Docker), or if Gitea is installed to a different directory than the previous installation.
84
+
85
+
With Gitea running, and from the directory Gitea's binary is located, execute: `./gitea admin regenerate hooks`
86
+
87
+
This ensures that application and configuration file paths in repository git-hooks are consistent and applicable to the current installation. If these paths are not updated, repository `push` actions will fail.
0 commit comments