Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
Go to file
Slavi Pantaleev c4a05b760a Make mautrix bridges not overwrite their config
If they do, our next playbook runs would simply revert it
and report "changed" for that task.

There's no benefit to letting the bridge spew a new config file.

This does not apply to the mautrix whatsapp bridge, because that one
is written in Go (not Python) and takes different flags. There's no
equivalent flag there.
2021-02-03 13:23:18 +02:00
.github Create FUNDING.yml 2020-12-01 15:11:37 +02:00
docs Merge pull request #804 from pushytoxin/matrix-etherpad 2021-01-31 09:55:46 +02:00
examples Clarify hosts file wording 2021-02-01 03:22:04 -06:00
group_vars Etherpad Jitsi integration 2021-01-26 05:04:47 +01:00
inventory Rename script file 2020-04-08 10:05:43 +03:00
roles Make mautrix bridges not overwrite their config 2021-02-03 13:23:18 +02:00
.editorconfig
.gitignore Adding '.python-version' to .gitignore 2020-10-06 11:42:32 +02:00
ansible.cfg
CHANGELOG.md Update docs and changelog 2021-01-31 09:54:12 +02:00
LICENSE
README.md Merge pull request #804 from pushytoxin/matrix-etherpad 2021-01-31 09:55:46 +02:00
setup.yml Etherpad role 2021-01-26 05:04:47 +01:00

Support room on Matrix donate

Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker

Purpose

This Ansible playbook is meant to help you run your own Matrix homeserver, along with the various services related to that.

That is, it lets you join the Matrix network using your own @<username>:<your-domain> identifier, all hosted on your own server (see prerequisites).

We run all services in Docker containers (see the container images we use), which lets us have a predictable and up-to-date setup, across multiple supported distros (see prerequisites) and architectures (x86/amd64 being recommended).

Installation (upgrades) and some maintenance tasks are automated using Ansible (see our Ansible guide).

Supported services

Using this playbook, you can get the following services configured on your server:

Basically, this playbook aims to get you up-and-running with all the basic necessities around Matrix, without you having to do anything else.

Note: the list above is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components.

Installation

To configure and install Matrix on your own server, follow the README in the docs/ directory.

Changes

This playbook evolves over time, sometimes with backward-incompatible changes.

When updating the playbook, refer to the changelog to catch up with what's new.

Support