mirror docker-ansible-matrix to my gitea instance under the 'mirrors' org name, and then fork the repo under my user! ahaaaa
Go to file
2021-04-05 09:31:32 +02:00
.github
docs - adapted documentation 2021-03-16 11:50:01 +01:00
examples
group_vars - fixed error with generator function 2021-04-05 09:31:32 +02:00
inventory
roles - matrix_postgres_backup_databases now uses more simple structure 2021-04-05 09:05:41 +02:00
.editorconfig
.gitignore
ansible.cfg
CHANGELOG.md
LICENSE
README.md
setup.yml - Added role to setup https://github.com/prodrigestivill/docker-postgres-backup-local container to backup all postgres databases 2021-02-11 17:18:25 +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