Fix minor typos in the doc

This commit is contained in:
TheophileDiot 2022-09-29 15:12:00 +02:00
parent de0954fac3
commit e3d0120a0c
3 changed files with 8 additions and 8 deletions

View file

@ -849,7 +849,7 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt
chown -R root:nginx /opt/bunkerweb
```
Last but not least, you will need to set up system unit files :
Last but not least, you will need to set up systemd unit files :
```shell
cp /tmp/bunkerweb/linux/*.service /etc/systemd/system && \
systemctl daemon-reload && \

View file

@ -21,7 +21,7 @@ Instead of supporting only Authelia, we decided to support generic auth request
## Replaced BLOCK_\*, WHITELIST_\* and BLACKLIST_\* settings
The blocking mechanisms have been completely redesigned. We have detected that a lot of false positives came from the default blacklists hardcoded into bunkerized. That's why we now give users the possibility of choosing their own blacklists (and also whitelists). For IP address, reverse DNS, user-agent, URI and ASN, see the [Blacklisting and whitelisting](/1.4/security-tuning/#blacklisting-and-whitelisting) section of the [security tuning](/1.4/security-tuning).
The blocking mechanisms have been completely redesigned. We have detected that a lot of false positives came from the default blacklists hardcoded into bunkerized. That's why we now give users the possibility of choosing their own blacklists (and also whitelists) for IP address, reverse DNS, user-agent, URI and ASN, see the [Blacklisting and whitelisting](/1.4/security-tuning/#blacklisting-and-whitelisting) section of the [security tuning](/1.4/security-tuning).
## Changed WHITELIST_USER_AGENT setting behavior

View file

@ -275,7 +275,7 @@ You will find more settings about reverse proxy in the [settings section](/1.4/s
=== "Ansible"
We will assume that you already have a service running and you want to use Bunkerweb as a reverse-proxy.
We will assume that you already have a service running and you want to use BunkerWeb as a reverse-proxy.
The following command will run a basic HTTP server on the port 8000 and deliver the files in the current directory :
```shell
@ -1048,7 +1048,7 @@ REAL_IP_HEADER=X-Forwarded-For
=== "Kubernetes"
You will need to add the settings to the environment variables of the Bunkerweb containers (doing it using the ingress is not supported because you will get into trouble when using things like Let's Encrypt) :
You will need to add the settings to the environment variables of the BunkerWeb containers (doing it using the ingress is not supported because you will get into trouble when using things like Let's Encrypt) :
```yaml
apiVersion: apps/v1
kind: DaemonSet
@ -1085,7 +1085,7 @@ REAL_IP_HEADER=X-Forwarded-For
...
```
Don't forget to restart the Bunkerweb service once it's done.
Don't forget to restart the BunkerWeb service once it's done.
=== "Ansible"
@ -1218,7 +1218,7 @@ REAL_IP_HEADER=proxy_protocol
=== "Kubernetes"
You will need to add the settings to the environment variables of the Bunkerweb containers (doing it using the ingress is not supported because you will get into trouble when using things like Let's Encrypt) :
You will need to add the settings to the environment variables of the BunkerWeb containers (doing it using the ingress is not supported because you will get into trouble when using things like Let's Encrypt) :
```yaml
apiVersion: apps/v1
kind: DaemonSet
@ -1258,7 +1258,7 @@ REAL_IP_HEADER=proxy_protocol
...
```
Don't forget to restart the Bunkerweb service once it's done.
Don't forget to restart the BunkerWeb service once it's done.
=== "Ansible"
@ -1520,7 +1520,7 @@ Some integrations offer a more convenient way of applying configurations such as
chmod -R 770 /opt/bunkerweb/configs
```
Don't forget to restart the Bunkerweb service once it's done.
Don't forget to restart the BunkerWeb service once it's done.
=== "Ansible"