clarify fail2ban requirements
This commit is contained in:
parent
559efa281f
commit
c69547f2b2
1 changed files with 3 additions and 1 deletions
|
@ -107,7 +107,9 @@ The following have been tested with Debian 8, it should work on Ubuntu as well.
|
||||||
|
|
||||||
### Fail2Ban configuration
|
### Fail2Ban configuration
|
||||||
|
|
||||||
If enabled, this will deploy a fail2ban filter and jail config for Gitea as described in the [Gitea Documentation](https://docs.gitea.io/en-us/fail2ban-setup/). Fail2ban has to be already installed.
|
If enabled, this will deploy a fail2ban filter and jail config for Gitea as described in the [Gitea Documentation](https://docs.gitea.io/en-us/fail2ban-setup/).
|
||||||
|
|
||||||
|
As this will only deploy config files fail2ban has to be already installed, otherwise the role will fail.
|
||||||
|
|
||||||
* `gitea_fail2ban_enabled`: Wether to deploy the fail2ban config snippets
|
* `gitea_fail2ban_enabled`: Wether to deploy the fail2ban config snippets
|
||||||
* `gitea_fail2ban_jail_maxretry`: fail2ban jail `maxretry` setting. Default: `10`
|
* `gitea_fail2ban_jail_maxretry`: fail2ban jail `maxretry` setting. Default: `10`
|
||||||
|
|
Loading…
Reference in a new issue