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
Slavi Pantaleev 4b500ffb43
Merge pull request #1291 from hifi/feature/heisenbridge-1.2.0
Upgrade Heisenbridge (1.1.1 -> 1.2.0)
2021-09-24 09:31:13 +03:00
.github Add Ko-fi donation link 2021-03-02 13:29:04 +02:00
docs Do not advertise Debian 9 support 2021-09-21 10:57:32 +03:00
examples Fix typo 2021-09-14 16:52:57 +02:00
group_vars Merge pull request #1242 from apmechev/add_beeper_linkedin_bridge 2021-08-23 15:15:35 +03:00
inventory jicofo client proxy connection 2021-06-23 23:17:24 +05:30
roles Upgrade Heisenbridge (1.1.1 -> 1.2.0) 2021-09-23 10:18:46 +03:00
.editorconfig
.gitignore
ansible.cfg
CHANGELOG.md Announce LinkedIn Messaging bridging support 2021-08-23 15:27:16 +03:00
LICENSE
README.md Adds Documentation for LinkedIn Bridge 2021-08-21 18:24:30 +02:00
setup.yml add code for LinkedIn Bridge 2021-08-21 17:32:45 +02: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 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

  • GoMatrixHosting - matrix-docker-ansible-deploy "as a service" with Ansible AWX. Members can be assigned a server from DigitalOcean, or they can connect their on-premises server. This AWX system can manage the updates, configuration, import and export, backups, and monitoring on its own. For more information see our GitLab group or come visit us on Matrix.