finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Upstream: https://github.com/spantaleev/matrix-docker-ansible-deploy Used for deploying https://matrix.finallycoffee.eu/
1,511 Commits 3 Branches 0 Tags 171 MiB
Jinja 99.3%
Just 0.3%
Shell 0.3%
d48d77012d
Go to file
Slavi Pantaleev d48d77012d
Merge pull request #531 from dasTholo/patch-1 
Add Docker Network for matrix-mautrix-telegram-db ...
2020-06-06 14:09:34 +03:00
docs Update components 2020-06-06 08:25:27 +03:00
examples Disable TLSv1.1 by default 2020-01-30 12:56:20 +02:00
group_vars matrix-sms-bridge: 2020-05-23 13:14:24 +02:00
inventory Rename script file 2020-04-08 10:05:43 +03:00
roles Add Docker Network for matrix-mautrix-telegram-db for Telegram Bridge with Postgress 2020-06-06 12:42:25 +02:00
.editorconfig Add comment about trailing whitespace in Markdown 2019-02-01 11:00:25 +02:00
.gitignore update Jitsi, add generate-jitsi-passwords script 2020-04-08 02:07:52 +02:00
ansible.cfg Move pipelining option to proper section 2019-09-01 01:59:41 +02:00
CHANGELOG.md Update changelog 2020-06-05 15:05:48 +03:00
LICENSE Add LICENSE file 2018-08-17 09:01:06 +03:00
README.md matrix-sms-bridge: 2020-05-23 13:14:24 +02:00
setup.yml renamed role matrix-sms-bridge to matrix-bridge-sms 2020-06-05 12:25:41 +02:00

README.md

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

Purpose

This Ansible playbook is meant to easily let you run your own Matrix homeserver.

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

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.

What's different about this Ansible playbook?

This is similar to the EMnify/matrix-synapse-auto-deploy Ansible deployment, but:

  • this one is a complete Ansible playbook (instead of just a role), so it's easier to run - especially for folks not familiar with Ansible

  • this one installs and hooks together a lot more Matrix-related services for you (see above)

  • this one can be re-ran many times without causing trouble

  • works on various distros: CentOS (7.0+), Debian-based distributions (Debian 9/Stretch+, Ubuntu 16.04+), Archlinux

  • this one installs everything in a single directory (/matrix by default) and doesn't "contaminate" your server with files all over the place

  • this one doesn't necessarily take over ports 80 and 443. By default, it sets up nginx for you there, but you can also use your own webserver

  • this one runs everything in Docker containers, so it's likely more predictable and less fragile (see Docker images used by this playbook)

  • this one retrieves and automatically renews free Let's Encrypt SSL certificates for you

  • this one optionally can store the media_store content repository files on Amazon S3 (but defaults to storing files on the server's filesystem)

  • this one optionally allows you to use an external PostgreSQL server for Synapse's database (but defaults to running one in a container)

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.

Docker images used by this playbook

This playbook sets up your server using the following Docker images:

Deficiencies

This Ansible playbook can be improved in the following ways:

  • setting up automatic backups to one or more storage providers

Support