titanz
/
matrix-docker-ansible-deploy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0a977ce113'
${ noResults }
matrix-docker-ansible-deploy/docs/prerequisites.md

3.8 KiB
Raw Blame History

Prerequisites

This playbook doesn't support running on ARM (see this issue), however a minimal subset of the tools can be built on the host, which may result in a working configuration, even on a Raspberry pi (see Alternative Architectures). We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there.

  • root access to your server (or a user capable of elevating to root via sudo).

  • Python being installed on the server. Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like apt-get install python3). On some distros, Ansible may incorrectly detect the Python version (2 vs 3) and you may need to explicitly specify the interpreter path in inventory/hosts during installation (e.g. ansible_python_interpreter=/usr/bin/python3)

  • A cron-like tool installed on the server such as cron or anacron to automatically schedule the Let's Encrypt SSL certificates's renewal. This can be ignored if you use your own SSL certificates.

  • The Ansible program being installed on your own computer. It's used to run this playbook and configures your server for you. Take a look at our guide about Ansible for more information, as well as version requirements and alternative ways to run Ansible.

  • Either the dig tool or python-dns installed on your own computer. Used later on, by the playbook's services check feature.

  • An HTTPS-capable web server at the base domain name (<your-domain>) which is capable of serving static files. Unless you decide to Serve the base domain from the Matrix server or alternatively, to use DNS SRV records for Server Delegation.

  • Properly configured DNS records for <your-domain> (details in Configuring DNS).

  • Some TCP/UDP ports open. This playbook configures the server's internal firewall for you. In most cases, you don't need to do anything special. But if your server is running behind another firewall, you'd need to open these ports:

    • 80/tcp: HTTP webserver
    • 443/tcp: HTTPS webserver
    • 3478/tcp: TURN over TCP (used by Coturn)
    • 3478/udp: TURN over UDP (used by Coturn)
    • 5349/tcp: TURN over TCP (used by Coturn)
    • 5349/udp: TURN over UDP (used by Coturn)
    • 8448/tcp: Matrix Federation API HTTPS webserver. In some cases, this may necessary even with federation disabled. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access openid APIs on the federation port.
    • the range 49152-49172/udp: TURN over UDP
    • 4443/tcp: Jitsi Harvester fallback
    • 10000/udp: Jitsi video RTP. Depending on your firewall/NAT setup, incoming RTP packets on port 10000 may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see matrix_jitsi_jvb_stun_servers).

When ready to proceed, continue with Configuring DNS.