Open Infrastructure

h1. The ungleich Matrix infrastructure

*%{color:red}This document concerns the infrastructure side of our MaaS offer and is intended for ungleich staff. See [[Ungleich Matrix-as-a-Service (MaaS)]] page for end-user/customer documentation.%*

h2. Status

This document is *A DRAFT*. This service is not in production.

h2. Environment

Our Matrix deployments make use of the "Synapse (reference) Matrix homeserver":https://github.com/matrix-org/synapse/ and "Riot web client":https://about.riot.im/. We use Debian buster as base Operating system, leveraging the "matrix-synapse package from the buster-backports repository":https://packages.debian.org/buster-backports/matrix-synapse. The riot client (= static files) is directly fetched from "upstream releases on github":https://github.com/vector-im/riot-web/releases.

The matrix deployments run on ipv6only VMs, HTTP(S) traffic - including federation - being proxy by the [[How to use the IPv4-to-IPv6-Proxy|ungleich v4-to-v6 proxy]]. Federation is delegated using a @/.well-known/@ URI as described in [[Ungleich Matrix-as-a-Service (MaaS)|the customer FAQ]].

h2. Tooling

The whole MaaS setup is defined in the *manifest/matrix-as-a-service* of *dot-cdist* file, which wraps the *__ungleich_matrix* type. This type leverages:

* *__matrix_synapse*

* *__matrix_riot*

* *__ungleich_nginx_static_type*

* *__postgres_role* and *__postgres_database* from upstream cdist.

h2. Monitoring

We plan to leverage consul's service discovery to feed system (node exporter) and matrix (synapse) metrics to prometheus/grafana.

h2. Ungleich Deployments

We maintain our own deployments alongside the customer MaaS, both for our own usage and for testing.

h3. matrix-staging.ungleich.ch

Staging instance used to tests the deployment pipeline and Matrix updates.

h3. matrix.ungleich.ch

Production instance for ungleich, will be bridged to "chat.ungleich.ch":https://chat.ungleich.ch at some point.

h2. Application Services

We do not support any application service as of today.