Matrix: Difference between revisions

</syntaxhighlight>

<syntaxhighlight lang="nixos">

{

</syntaxhighlight>

[https://element-hq.github.io/synapse/latest/welcome_and_overview.html Synapse] has an associated module exposing the [https://search.nixos.org/options?query=services.matrix-synapse services.matrix-synapse.* options]. See [https://nixos.org/nixos/manual/index.html#module-services-matrix-synapse the NixOS manual entry] for a complete configuration example.

For WebRTC calls to work when both callers are behind a NAT, you need to provide a turn server for clients to use. Here is an example configuration, inspired from [https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-coturn/templates/turnserver.conf.j2 this configuration file].

</syntaxhighlight>

There's an external module to automatically set up synapse and configure nginx with workers:

https://github.com/dali99/nixos-matrix-modules

Bridges allow you to connect Matrix to a third-party platform (like Discord, Telegram, etc.), and interact seamlessly. See [https://matrix.org/ecosystem/bridges/ here] for a list of currently supported bridges.

Full configuration reference:

https://github.com/tulir/mautrix-telegram/blob/master/mautrix_telegram/example-config.yaml

</syntaxhighlight>

Packaged as [https://search.nixos.org/packages?query=mautrix-whatsapp mautrix-whatsapp].

Module implemented in this [https://github.com/NixOS/nixpkgs/pull/246842 PR].

NixOS-specific module options: TODO link to the search results once it's landed

The appservice automatically creates a registration file under <code>/var/lib/matrix-appservice-irc/registration.yml</code> and keeps it up to date. If your homeserver is not located on the same machine and NixOS installation, you must absolutely make sure to synchronize that file over to the home server after each modification and keep both in sync.

Full configuration reference:

https://github.com/Half-Shot/matrix-appservice-discord/blob/master/config/config.sample.yaml