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/
4,180 Commits 3 Branches 0 Tags 171 MiB
Jinja 99.3%
Just 0.3%
Shell 0.3%
bab1ee2233
Go to file
Slavi Pantaleev bab1ee2233 Work around mx-puppet-discord failing with "No relay found" after reboot 
Related to https://gitlab.com/mx-puppet/discord/mx-puppet-discord/-/issues/117

Looks like the bridge is too quick to start and fails to initialize
itself by connecting to Synapse. It's mostly observed after a system
reboot, because Synapse (and everything else) is slower to start.

Once mx-puppet-discord fails to initialize itself, a "No relay found"
error will be observed any time you try to relay a Matrix message to
Discord. Relaying messages in the other direction (Discord to Matrix)
also fails.

With this workaround (longer delay on mx-puppet-discord startup), I
observe mx-puppet-discord working well, even after a full reboot.
Of course, a proper fix is preferable, instead of delaying by a magic
number of seconds.
2022-05-17 11:34:00 +03:00
.github Bump actions/checkout from 2.4.0 to 3 2022-03-02 17:20:17 +00:00
collections fix: all praise the allmighty yamllinter 2022-02-05 21:32:54 +01:00
docs Document git as a potential prereq 2022-05-16 04:36:18 +00:00
examples Merge branch 'master' of https://github.com/Arkonos/matrix-docker-ansible-deploy 2022-05-08 21:37:56 +02:00
group_vars Automatically enable admin api access via nginx (#1830) 2022-05-16 10:26:15 +03:00
inventory jicofo client proxy connection 2021-06-23 23:17:24 +05:30
roles Work around mx-puppet-discord failing with "No relay found" after reboot 2022-05-17 11:34:00 +03:00
.editorconfig Add comment about trailing whitespace in Markdown 2019-02-01 11:00:25 +02:00
.gitignore Adding '.python-version' to .gitignore 2020-10-06 11:42:32 +02:00
.yamllint fix: ignore generated file on yamllint 2022-02-09 15:03:39 +01:00
ansible.cfg Use the yaml callback plugin when running ansible-playbook 2021-02-18 15:57:05 +01:00
CHANGELOG.md Announce Buscarron bot support 2022-04-25 10:29:09 +03:00
LICENSE Add LICENSE file 2018-08-17 09:01:06 +03:00
README.md add buscarron to the readme 2022-04-23 17:11:24 +03:00
setup.yml add matrix-bot-buscarron 2022-04-23 16:19:24 +03:00

README.md

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 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

Services by the community

  • etke.cc - matrix-docker-ansible-deploy and system stuff "as a service". That service will create your matrix homeserver on your domain and server (doesn't matter if it's cloud provider or on an old laptop in the corner of your room), (optional) maintains it (server's system updates, cleanup, security adjustments, tuning, etc.; matrix homeserver updates & maintenance) and (optional) provide full-featured email service for your domain