You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mjolnir can be run as an appservice, allowing users you trust or on your homeserver to run their own Mjolnir without hosting anything themselves.
2
+
This module is currently alpha quality and is subject to rapid changes,
3
+
it is not recommended currently and support will be limited.
4
+
5
+
# Prerequisites
6
+
7
+
This guide assumes you will be using Docker and that you are able to provide a postgres database for Mjolnir to connect to in application service mode.
8
+
9
+
# Setup
10
+
11
+
1. Create a new Matrix room that will act as a policy list for who can use the appservice.
12
+
FIXME: Currently required to be aliased.
13
+
FIXME: Should really be created and managed by the admin room, but waiting for command refactor before doing that.
14
+
15
+
2. Decide on a spare local TCP port number to use that will listen for messages from the matrix homeserver. Take care to configure firewalls appropriately. This port will be notated as `$MATRIX_PORT` in the remaining instructions.
16
+
17
+
3. Create a config/config.appservice.yaml file that can be copied from the example in `src/appservice/config/config.example.yaml`. Your config file needs to be accessible to the docker container later on.
18
+
19
+
4. Generate the appservice registration file. This will be used by both the appservice and your homeserver.
20
+
Here, you must specify the direct link the Matrix Homserver can use to access the appservice, including the Matrix port it will send messages through (if this bridge runs on the same machine you can use localhost as the $HOST name):
0 commit comments