This playbook tries to get you up and running with minimal effort and provided you have followed the example vars.yml file, will install the Traefik reverse-proxy server by default.
Sometimes, you're using a server which already has Traefik. In such cases these are undesirable:
-
the playbook trying to run its own Traefik instance and running into a conflict with your other Traefik instance over ports (
tcp/80andtcp/443) -
multiple playbooks trying to install Docker, etc.
Below, we offer some suggestions for how to make this playbook more interoperable. Feel free to cherry-pick the parts that make sense for your setup.
If you're installing Traefik on your server in another way, you can use your already installed Traefik instance by pointing MASH to your existing Traefik reverse-proxy (see the Traefik managed by you guide).
If you are using the matrix-docker-ansible-deploy playbook against the same server where you'd like MASH services installed, it already runs its own Traefik instance (matrix-traefik). In this case, we recommend following the same Traefik managed by you guide, because matrix-docker-ansible-deploy installs Traefik the same way, but also injects additional configuration for handling the Matrix federation port (8448 on a matrix-federation entrypoint) and internal communication between services (a matrix-internal-matrix-client-api entrypoint).
If you're installing Docker on your server in another way, disable this component from the playbook:
mash_playbook_docker_installation_enabled: falseIf you're installing systemd-timesyncd or ntp on your server in another way, disable this component from the playbook:
devture_timesync_installation_enabled: false