deploy_adguard

History

Bertrand Lanson 4691dd972c All checks were successful test / Linting (push) Successful in 25s Details test / Molecule tests (default, ubuntu2004) (push) Successful in 1m2s Details test / Molecule tests (default, debian12) (push) Successful in 1m16s Details test / Molecule tests (default, debian11) (push) Successful in 1m27s Details test / Molecule tests (with_extra_sidecars, debian12) (push) Successful in 51s Details test / Molecule tests (default, ubuntu2204) (push) Successful in 1m16s Details test / Molecule tests (with_extra_sidecars, debian11) (push) Successful in 1m7s Details test / Molecule tests (with_extra_sidecars, ubuntu2204) (push) Successful in 45s Details test / Molecule tests (with_extra_sidecars, ubuntu2004) (push) Successful in 1m0s Details nice_yamlify adguard config file		2023-07-27 18:58:35 +02:00
..
adguard-connect-proxy.env.j2	there is a weird bug with adguard in docker, needs investigation	2023-06-04 01:02:00 +02:00
adguard-connect-proxy.service.j2	there is a weird bug with adguard in docker, needs investigation	2023-06-04 01:02:00 +02:00
adguard.consul.json.j2	wrong format and content for consul service file	2023-06-03 14:05:27 +02:00
adguard.service.j2	update service template	2023-06-01 23:02:50 +02:00
AdGuardhome.yaml.j2	nice_yamlify adguard config file	2023-07-27 18:58:35 +02:00
docker-compose.yml.j2	added test for default scenario, and started 2nd scenario	2023-06-06 20:17:04 +02:00