self-hosted/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-12-12 08:43:55 +02:00
Code Issues Releases Activity
69f71f48a6
matrix-docker-ansible-deploy/roles/matrix-bridge-appservice-discord/defaults/main.yml

86 lines
4.1 KiB
YAML
Raw Normal View History

Move matrix-appservice-discord into a separate role
2019-05-17 18:14:12 +02:00
# matrix-appservice-discord is a Matrix <-> Discord bridge
# See: https://github.com/Half-Shot/matrix-appservice-discord
matrix_appservice_discord_enabled: true
Update matrix-appservice-discord to v1.0.0 final
2020-12-03 15:16:26 +02:00
matrix_appservice_discord_docker_image: "docker.io/halfshot/matrix-appservice-discord:v1.0.0"
Automatically force-pull :latest images We do use some `:latest` images by default for the following services: - matrix-dimension - Goofys (in the matrix-synapse role) - matrix-bridge-appservice-irc - matrix-bridge-appservice-discord - matrix-bridge-mautrix-facebook - matrix-bridge-mautrix-whatsapp It's terribly unfortunate that those software projects don't release anything other than `:latest`, but that's how it is for now. Updating that software requires that users manually do `docker pull` on the server. The playbook didn't force-repull images that it already had. With this patch, it starts doing so. Any image tagged `:latest` will be force re-pulled by the playbook every time it's executed. It should be noted that even though we ask the `docker_image` module to force-pull, it only reports "changed" when it actually pulls something new. This is nice, because it lets people know exactly when something gets updated, as opposed to giving the indication that it's always updating the images (even though it isn't).
2019-06-10 13:23:51 +02:00
matrix_appservice_discord_docker_image_force_pull: "{{ matrix_appservice_discord_docker_image.endswith(':latest') }}"
Move matrix-appservice-discord into a separate role
2019-05-17 18:14:12 +02:00
matrix_appservice_discord_base_path: "{{ matrix_base_data_path }}/appservice-discord"
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
matrix_appservice_discord_config_path: "{{ matrix_base_data_path }}/appservice-discord/config"
matrix_appservice_discord_data_path: "{{ matrix_base_data_path }}/appservice-discord/data"
Move matrix-appservice-discord into a separate role
2019-05-17 18:14:12 +02:00
# Get your own keys at https://discordapp.com/developers/applications/me/create
matrix_appservice_discord_client_id: ''
matrix_appservice_discord_bot_token: ''
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
matrix_appservice_discord_appservice_token: ''
matrix_appservice_discord_homeserver_token: ''
Upgrade appservice-discord
2020-11-10 23:10:59 +02:00
matrix_appservice_discord_homeserver_domain: "{{ matrix_domain }}"
Add support for more flexible container port exposing Fixes #171 (Github Issue).
2019-05-25 00:41:04 +02:00
# Controls whether the matrix-appservice-discord container exposes its HTTP port (tcp/9005 in the container).
#
# Takes an "<ip>:<port>" or "<port>" value (e.g. "127.0.0.1:9005"), or empty string to not expose.
matrix_appservice_discord_container_http_host_bind_port: ''
Move matrix-appservice-discord into a separate role
2019-05-17 18:14:12 +02:00
# A list of extra arguments to pass to the container
matrix_appservice_discord_container_extra_arguments: []
# List of systemd services that matrix-appservice-discord.service depends on.
matrix_appservice_discord_systemd_required_services_list: ['docker.service']
# List of systemd services that matrix-appservice-discord.service wants
matrix_appservice_discord_systemd_wanted_services_list: []
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
matrix_appservice_discord_appservice_url: 'http://matrix-appservice-discord:9005'
matrix_appservice_discord_bridge_domain: "{{ matrix_domain }}"
# As of right now, the homeserver URL must be a public URL. See below.
Correct inabillity for appservice-discord to connect After recently updating my matrix-docker-ansible-deploy installation, matrix-appservice-discord would refuse to start, logging ECONNREFUSED to https://matrix.[mydomain]:443, which was resolving to 172.18.0.2 due to the `--hostname` in mailer grabbing that hostname. Curious why the IRC bridge didn't have this issue, I looked into it, and it was connecting to `http://matrix-synapse:8008`. Correcting this one to that URL resolved the issue.
2020-12-10 05:20:06 +02:00
matrix_appservice_discord_bridge_homeserverUrl: "http://matrix-synapse:8008"
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
matrix_appservice_discord_bridge_disablePresence: false
Expose self service bridging in matrix_appservice_discord This allows for users to bridge already existing matrix rooms to discord
2019-12-11 15:47:44 +02:00
matrix_appservice_discord_bridge_enableSelfServiceBridging: false
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
Mention and recommend enabling usePrivilegedIntents
2020-11-13 08:23:40 +02:00
# Tells whether the bot should make use of "Privileged Gateway Intents".
#
# Enabling this means that you need to enable it for the bot (Discord application) as well,
# by triggering all Intent checkboxes on a page like this: `https://discord.com/developers/applications/694448564151123988/bot`
#
# Learn more: https://gist.github.com/advaith1/e69bcc1cdd6d0087322734451f15aa2f
matrix_appservice_discord_auth_usePrivilegedIntents: false
Move configuration templates outside of defaults/main.yml files
2020-06-03 08:33:28 +02:00
matrix_appservice_discord_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}"
Move matrix-appservice-discord into a separate role
2019-05-17 18:14:12 +02:00
matrix_appservice_discord_configuration_extension_yaml: |
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
# Your custom YAML configuration goes here.
# This configuration extends the default starting configuration (`matrix_appservice_discord_configuration_yaml`).
#
# You can override individual variables from the default configuration, or introduce new ones.
#
# If you need something more special, you can take full control by
# completely redefining `matrix_appservice_discord_configuration_yaml`.
Move matrix-appservice-discord into a separate role
2019-05-17 18:14:12 +02:00
Fix undefined variables in mxisd and Dimension configuration
2019-06-07 10:46:35 +02:00
matrix_appservice_discord_configuration_extension: "{{ matrix_appservice_discord_configuration_extension_yaml|from_yaml if matrix_appservice_discord_configuration_extension_yaml|from_yaml is mapping else {} }}"
Move matrix-appservice-discord into a separate role
2019-05-17 18:14:12 +02:00
matrix_appservice_discord_configuration: "{{ matrix_appservice_discord_configuration_yaml|from_yaml|combine(matrix_appservice_discord_configuration_extension, recursive=True) }}"
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
matrix_appservice_discord_registration_yaml: |
#jinja2: lstrip_blocks: "True"
id: appservice-discord
as_token: "{{ matrix_appservice_discord_appservice_token }}"
hs_token: "{{ matrix_appservice_discord_homeserver_token }}"
namespaces:
users:
- exclusive: true
Upgrade appservice-discord
2020-11-10 23:10:59 +02:00
regex: '@_discord_.*:{{ matrix_appservice_discord_homeserver_domain|regex_escape }}'
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
aliases:
- exclusive: true
Upgrade appservice-discord
2020-11-10 23:10:59 +02:00
regex: '#_discord_.*:{{ matrix_appservice_discord_homeserver_domain|regex_escape }}'
Make Discord bridge configuration playbook-managed 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.
2019-06-26 09:30:51 +02:00
url: {{ matrix_appservice_discord_appservice_url }}
sender_localpart: _discord_bot
rate_limited: false
protocols:
- discord
matrix_appservice_discord_registration: "{{ matrix_appservice_discord_registration_yaml|from_yaml }}"
Reference in New Issue Copy Permalink