readme edit
All checks were successful
test / Linting (push) Successful in 32s
test / Molecule tests (default, ubuntu2004) (push) Successful in 1m9s
test / Molecule tests (default, debian11) (push) Successful in 1m23s
test / Molecule tests (default, debian12) (push) Successful in 1m22s
test / Molecule tests (with_extra_sidecars, debian11) (push) Successful in 39s
test / Molecule tests (with_extra_sidecars, debian12) (push) Successful in 45s
test / Molecule tests (default, ubuntu2204) (push) Successful in 59s
test / Molecule tests (with_extra_sidecars, ubuntu2004) (push) Successful in 1m1s
test / Molecule tests (with_extra_sidecars, ubuntu2204) (push) Successful in 1m6s

This commit is contained in:
Bertrand Lanson 2023-08-10 11:31:27 +02:00
parent 4691dd972c
commit ccaa05ffe3

View File

@ -54,7 +54,7 @@ Whether or not this server will use dnscrypt. This manages the port forwarding t
```yaml
deploy_adguard_start_service: false # bydefault, set to false
deploy_adguard_start_service: false # by default, set to false
```
This variable manages whether or not to start the adguard service during the play, or when config files are changed. This can be useful to disable it if you plan on building golden images with this role and you don't want the containers to start during the build process. Please note that the service will ALWAYS be enabled, meaning that it'll automatically start upon reboot of the host.