The playbook can install and configure matrix-appservice-discord for you.
See the project’s documentation to learn what it does and why it might be useful to you.
Instructions loosely based on this.
vars.yml file:matrix_appservice_discord_enabled: true
matrix_appservice_discord_client_id: "YOUR DISCORD APP CLIENT ID"
matrix_appservice_discord_bot_token: "YOUR DISCORD APP BOT TOKEN"
--tags=setup-all,start). If not, proceed with configuring other playbook services and then with Installing. Get back to this guide once ready.{{ matrix_appservice_discord_config_path }}/invite_link file on the server (this defaults to /matrix/appservice-discord/config/invite_link)#_discord_guildid_channelid - can be easily retrieved by logging into Discord in a browser and opening the desired channel. URL will have this format: discordapp.com/channels/guild_id/channel_idOther configuration options are available via the matrix_appservice_discord_configuration_extension_yaml variable.
By default, you won’t have Administrator access in rooms created by the bridge.
To adjust room access privileges or do various other things (change the room name subsequently, etc.), you’d wish to become an Administrator.
There’s the Discord bridge’s guide for setting privileges on bridge managed rooms. To do the same with our container setup, run the following command on the server:
docker exec -it matrix-appservice-discord /bin/sh -c 'cp /build/tools/adminme.js /tmp/adminme.js && cp /cfg/registration.yaml /tmp/discord-registration.yaml && cd /tmp && node /tmp/adminme.js -c /cfg/config.yaml -r "!ROOM_ID:SERVER" -u "@USER:SERVER" -p 100'
All rooms created by the bridge are listed publicly in your server’s directory and joinable by everyone by default.
To get more control of them, make yourself a room Administrator first.
You can then unlist the room from the directory and change the join rules.