8529efcd1c
Well, `config.yaml` has been playbook-managed for a long time. It's now extended to match the default sample config of the Discord bridge. With this patch, we also make `registration.yaml` playbook-managed, which leads us to consistency with all other bridges. Along with that, we introduce `./config` and `./data` separation, like we do for the other bridges.
1.8 KiB
1.8 KiB
Setting up Appservice Discord (optional)
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.
Setup Instructions:
loosely based on this
- Create a Discord Application here.
- Retrieve Client ID and Bot token from this Application.
- Enable the bridge with the following configuration in your
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"
- If you've already installed Matrix services using the playbook before, you'll need to re-run it (
--tags=setup-all,start
). If not, proceed with configuring other playbook services and then with Installing. Get back to this guide once ready. - Retrieve Discord invite link from the
{{ matrix_appservice_discord_config_path }}/invite_link
file on the server (this defaults to/matrix/appservice-discord/config/invite_link
) - Invite the Bot to Discord servers you wish to bridge. Administrator permission is recommended.
- Join the rooms by following this syntax
#_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_id
Other configuration options are available via the matrix_appservice_discord_configuration_extension_yaml
variable.