jotbe/ansible-selfhosted-services
1
0
Fork 0
Code Issues Pull requests 1 Releases Wiki Activity

Compare commits

base: jotbe:00cd96e3b40b33a1f196c00df0d3595f93348b16
Branches Tags
jotbe:master
jotbe:change/use-community-docker
jotbe:feature/coturn-docker
jotbe:feature/multitenancy
jotbe:feature/dict-vars-and-install-paths
..
compare: jotbe:a271daf1221c6b2da7cdef0d196763bc5f59dfe6
Branches Tags
jotbe:master
jotbe:change/use-community-docker
jotbe:feature/coturn-docker
jotbe:feature/multitenancy
jotbe:feature/dict-vars-and-install-paths

1 commit
00cd96e3b4 ... a271daf122

Author SHA1 Message Date
Jan Beilicke
a271daf122 Adds geerlingguy.firewall 2020-03-31 00:38:45 +02:00
1 changed files with 1 additions and 1 deletions
Show stats Expand all files Collapse all files

2
README.md
View file

@ -135,7 +135,7 @@ Restic assumes untrusted environments, hence backups are always encrypted using
## Firewall <a id="firewall"></a>
The `common` role comes with a firewall based on iptables. If you don't allow SSH (usually port 22) then you might lock yourself out. Have a look at `group_vars/vagrant.yml` for an example config. Add the corresponding firewall parameters to your `host_vars` and adapt them according to your needs.
The `common` role comes with a [firewall](https://galaxy.ansible.com/geerlingguy/firewall) based on iptables. If you don't allow SSH (usually port 22) then you might lock yourself out. Have a look at `group_vars/vagrant.yml` for an example config. Add the corresponding [firewall parameters](https://galaxy.ansible.com/geerlingguy/firewall) to your `host_vars` and adapt them according to your needs.
## Alternatives