Slavi Pantaleev af1c9ae59d Do not force firewalld on people ... In most cases, there's not really a need to touch the system firewall, as Docker manages iptables by itself (see https://docs.docker.com/network/iptables/). All ports exposed by Docker containers are automatically whitelisted in iptables and wired to the correct container. This made installing firewalld and whitelisting ports pointless, as far as this playbook's services are concerned. People that wish to install firewalld (for other reasons), can do so manually from now on. This is inspired by and fixes #97 (Github Issue).		2019-04-03 11:37:20 +03:00
..
ssl	Do not force firewalld on people	2019-04-03 11:37:20 +03:00
init.yml	Split playbook into multiple roles	2019-01-12 18:01:10 +02:00
main.yml	Make matrix-nginx-proxy role independent of others	2019-01-17 13:32:46 +02:00
self_check_well_known_file.yml	Make self-check not validate self-signed certificates	2019-03-22 09:41:08 +02:00
self_check_well_known.yml	Make self-check not validate self-signed certificates	2019-03-22 09:41:08 +02:00
setup_nginx_proxy.yml	Do not force firewalld on people	2019-04-03 11:37:20 +03:00
setup_well_known.yml	Split playbook into multiple roles	2019-01-12 18:01:10 +02:00
validate_config.yml	Make matrix-nginx-proxy role independent of others	2019-01-17 13:32:46 +02:00