Note: bridging to Discord can also happen via the mx-puppet-discord and matrix-appservice-discord bridges supported by the playbook.
For using as a Bot we are recommend the Appservice Discord, because it supports plumbing.
For personal use with a discord account we recommend the mautrix-discord bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook.
The mautrix-discord bridge (the one being discussed here) is the most fully-featured and stable of the 3 Discord bridges supported by the playbook, so it’s the one we recommend.
The playbook can install and configure mautrix-discord for you.
See the project’s documentation to learn what it does and why it might be useful to you.
For using this bridge, you would need to authenticate by scanning a QR code with the Discord app on your phone.
You can delete the Discord app after the authentication process.
If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: mx-puppet-discord or matrix-appservice-discord. These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible.
To enable the bridge, add this to your vars.yml file:
matrix_mautrix_discord_enabled: true
You may optionally wish to add some Additional configuration, or to prepare for double-puppeting before the initial installation.
After adjusting your vars.yml file, re-run the playbook and restart all services: ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
To make use of the bridge, see Usage below.
There are some additional things you may wish to configure about the bridge.
Take a look at:
roles/matrix-bridge-mautrix-discord/defaults/main.yml for some variables that you can customize via your vars.yml fileroles/matrix-bridge-mautrix-discord/templates/config.yaml.j2 for the bridge’s default configuration. You can override settings (even those that don’t have dedicated playbook variables) using the matrix_mautrix_discord_configuration_extension_yaml variableIf you’d like to use Double Puppeting (hint: you most likely do), you have 2 ways of going about it.
The bridge will automatically perform Double Puppeting if you enable Shared Secret Auth for this playbook.
This is the recommended way of setting up Double Puppeting, as it’s easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
Note: This method for enabling Double Puppeting can be configured only after you’ve already set up bridging (see Usage).
When using this method, each user that wishes to enable Double Puppeting needs to follow the following steps:
curl \
--data '{"identifier": {"type": "m.id.user", "user": "YOUR_MATRIX_USERNAME" }, "password": "YOUR_MATRIX_PASSWORD", "type": "m.login.password", "device_id": "Mautrix-Discord", "initial_device_display_name": "Mautrix-Discord"}' \
https://matrix.DOMAIN/_matrix/client/r0/login
send the access token to the bot. Example: login-matrix MATRIX_ACCESS_TOKEN_HERE
make sure you don’t log out the Mautrix-Discord device some time in the future, as that would break the Double Puppeting feature
@discordbot:YOUR_DOMAIN (where YOUR_DOMAIN is your base domain, not the matrix. domain).login commandhelp command to the bot again, to see additional commands you have access toguilds status to see the list of guildsguilds bridge GUILD_ID --entire