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
..
clean_up_old_files.yml	Split playbook into multiple roles	2019-01-12 18:01:10 +02:00
main.yml	Rename some variables	2019-02-28 11:51:09 +02:00
sanity_check.yml	Ensure systemd services are running when doing --tags=start	2019-04-03 11:19:06 +03:00
self_check_dns_srv.yml	Treat empty string dig lookup responses as "missing record"	2019-02-22 18:02:10 +02:00
self_check_dns.yml	Rename some variables	2019-02-28 11:51:09 +02:00
setup_matrix_base.yml	Make the mode of the base path configurable	2019-01-14 14:40:11 +00:00
setup_server_base.yml	Do not force firewalld on people	2019-04-03 11:37:20 +03:00
setup_well_known.yml	Make /.well-known/matrix/server optional	2019-02-05 12:09:46 +02:00