Replace DOMAIN with example.com

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

roles/custom/matrix-alertmanager-receiver/defaults/main.yml

@@ -41,7 +41,7 @@ matrix_alertmanager_receiver_container_additional_networks_default: []
 matrix_alertmanager_receiver_container_additional_networks_auto: []
 matrix_alertmanager_receiver_container_additional_networks_custom: []
 
-# Controls whether matrix-alertmanager-receiver metrics should be proxied (exposed) on `matrix.DOMAIN/metrics/matrix-alertmanager-receiver`
+# Controls whether matrix-alertmanager-receiver metrics should be proxied (exposed) on `matrix.example.com/metrics/matrix-alertmanager-receiver`
 matrix_alertmanager_receiver_metrics_proxying_enabled: false
 matrix_alertmanager_receiver_metrics_proxying_hostname: ''
 matrix_alertmanager_receiver_metrics_proxying_path: /metrics/matrix-alertmanager-receiver

roles/custom/matrix-base/defaults/main.yml

@@ -289,7 +289,7 @@ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_definition:
 # may wish to register their routes with this additional entrypoint and provide their services on it for internal (no-public-network and non-TLS) use.
 #
 # This entrypoint provides local addons (e.g. bridges, bots, etc.) with the ability to easily & quickly communicate with the homeserver and/or related software.
-# Such services can reach the homeserver over the public internet (e.g. https://matrix.DOMAIN), but this is slow due to networking and SSL-termination.
+# Such services can reach the homeserver over the public internet (e.g. https://matrix.example.com), but this is slow due to networking and SSL-termination.
 # Talking directly to the homeserver (e.g. `http://matrix-synapse:8008`) is another option, but does not allow other homeserver-related software
 # (e.g. identity servers like ma1sd, media repository servers like matrix-media-repo, firewalls like matrix-corporal)
 # to register itself for certain homeserver routes.

roles/custom/matrix-base/tasks/validate_config.yml

@@ -30,7 +30,7 @@
 
       If you're observing this error on a new installation, you should ensure that the `matrix_homeserver_generic_secret_key` is defined.
       If you think you've defined it, but are still getting this error, then it's likely that you have a typo
-      in your domain name in `inventory/hosts` or in one of the directories leading up to your `inventory/host_vars/matrix.DOMAIN/vars.yml` file.
+      in your domain name in `inventory/hosts` or in one of the directories leading up to your `inventory/host_vars/matrix.example.com/vars.yml` file.
 
       If you're observing this error on an existing homeserver installation, you can fix it easily and in a backward-compatible way by adding
       `{% raw %}matrix_homeserver_generic_secret_key: "{{ matrix_synapse_macaroon_secret_key }}"{% endraw %}`

roles/custom/matrix-bot-chatgpt/defaults/main.yml

@@ -57,7 +57,7 @@ matrix_bot_chatgpt_keyv_bot_storage: true
 # Matrix Static Settings (required, see notes)
 # Defaults to "https://matrix.org"
 matrix_bot_chatgpt_matrix_homeserver_url: ""  # MATRIX_HOMESERVER_URL=
-# With the @ and :DOMAIN, ie @SOMETHING:DOMAIN, needs to be set, created manually beforehand.
+# With the @ and :example.com, ie @SOMETHING:example.com, needs to be set, created manually beforehand.
 matrix_bot_chatgpt_matrix_bot_username_localpart: 'bot.chatgpt'
 matrix_bot_chatgpt_matrix_bot_username: "@{{ matrix_bot_chatgpt_matrix_bot_username_localpart }}:{{ matrix_domain }}"  # MATRIX_BOT_USERNAME=
 # Set `MATRIX_BOT_PASSWORD` the bot will print an `MATRIX_ACCESS_TOKEN` to the terminal

roles/custom/matrix-bot-chatgpt/templates/env.j2

@@ -10,7 +10,7 @@ KEYV_URL={{ matrix_bot_chatgpt_keyv_url }}
 KEYV_BOT_ENCRYPTION={{ matrix_bot_chatgpt_keyv_bot_encryption|lower }}
 KEYV_BOT_STORAGE={{ matrix_bot_chatgpt_keyv_bot_storage|lower }}
 
-# With the @ and :DOMAIN, ie @SOMETHING:DOMAIN
+# With the @ and :example.com, ie @SOMETHING:example.com
 MATRIX_BOT_USERNAME={{ matrix_bot_chatgpt_matrix_bot_username }}
 MATRIX_BOT_PASSWORD={{ matrix_bot_chatgpt_matrix_bot_password }}
 

roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml

@@ -102,7 +102,7 @@
   ansible.builtin.fail:
     msg: >-
       Your configuration contains a variable (`{{ item }}`), which refers to the old metrics collection system for Hookshot,
-      which exposed metrics on `https://stats.DOMAIN/hookshot/metrics`.
+      which exposed metrics on `https://stats.example.com/hookshot/metrics`.
 
       We now recommend exposing Hookshot metrics in another way, from another URL.
       Refer to the changelog for more details: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#2022-06-22

roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml

@@ -114,10 +114,10 @@ matrix_mautrix_meta_instagram_appservice_address: "http://{{ matrix_mautrix_meta
 
 matrix_mautrix_meta_instagram_appservice_id: "{{ matrix_mautrix_meta_instagram_meta_mode }}"
 
-# For Facebook/Messenger, we use the same `@messengerbot:DOMAIN` username regardless of how bridging happens for multiple reasons:
+# For Facebook/Messenger, we use the same `@messengerbot:example.com` username regardless of how bridging happens for multiple reasons:
 # - it's consistent - regardless of how bridging happens, the bridged service is actually Messenger
-# - it's easy for users - you may change the mode, but the bot is always at `@messengerbot:DOMAIN`
-# - it doesn't conflict with mautrix-facebook which uses `@facebookbot:DOMAIN`
+# - it's easy for users - you may change the mode, but the bot is always at `@messengerbot:example.com`
+# - it doesn't conflict with mautrix-facebook which uses `@facebookbot:example.com`
 # - `matrix_mautrix_meta_instagram_appservice_avatar` only has icons for Messenger and Instagram, not Facebook
 matrix_mautrix_meta_instagram_appservice_username_prefix: |-
   {{

roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml

@@ -114,10 +114,10 @@ matrix_mautrix_meta_messenger_appservice_address: "http://{{ matrix_mautrix_meta
 
 matrix_mautrix_meta_messenger_appservice_id: "{{ matrix_mautrix_meta_messenger_meta_mode }}"
 
-# For Facebook/Messenger, we use the same `@messengerbot:DOMAIN` username regardless of how bridging happens for multiple reasons:
+# For Facebook/Messenger, we use the same `@messengerbot:example.com` username regardless of how bridging happens for multiple reasons:
 # - it's consistent - regardless of how bridging happens, the bridged service is actually Messenger
-# - it's easy for users - you may change the mode, but the bot is always at `@messengerbot:DOMAIN`
-# - it doesn't conflict with mautrix-facebook which uses `@facebookbot:DOMAIN`
+# - it's easy for users - you may change the mode, but the bot is always at `@messengerbot:example.com`
+# - it doesn't conflict with mautrix-facebook which uses `@facebookbot:example.com`
 # - `matrix_mautrix_meta_messenger_appservice_avatar` only has icons for Messenger and Instagram, not Facebook
 matrix_mautrix_meta_messenger_appservice_username_prefix: |-
   {{

roles/custom/matrix-media-repo/defaults/main.yml

@@ -44,7 +44,7 @@ matrix_media_repo_container_network: "{{ matrix_media_repo_identifier }}"
 # Use this to expose this container to another reverse proxy, which runs in a different container network.
 matrix_media_repo_container_additional_networks: []
 
-# Controls whether media repo metrics should be proxied (exposed) on `matrix.DOMAIN/metrics/matrix-media-repo`
+# Controls whether media repo metrics should be proxied (exposed) on `matrix.example.com/metrics/matrix-media-repo`
 matrix_media_repo_metrics_proxying_enabled: false
 matrix_media_repo_metrics_proxying_hostname: ""
 matrix_media_repo_metrics_proxying_path: "/metrics/matrix-media-repo"

roles/custom/matrix-registration/defaults/main.yml

@@ -114,7 +114,7 @@ matrix_registration_api_token_endpoint: "{{ matrix_registration_scheme }}://{{ m
 
 matrix_registration_api_validate_certs: true
 
-# The URL to your homeserver (e.g.: `https://matrix.DOMAIN`).
+# The URL to your homeserver (e.g.: `https://matrix.example.com`).
 # A local (in-container address) is preferable.
 matrix_registration_server_location: ""
 

roles/custom/matrix-sliding-sync/defaults/main.yml

@@ -43,7 +43,7 @@ matrix_sliding_sync_container_additional_networks: []
 matrix_sliding_sync_metrics_enabled: false
 matrix_sliding_sync_metrics_port: 2112
 
-# Controls whether Sliding Sync metrics should be proxied (exposed) on `matrix.DOMAIN/metrics/sliding-sync`
+# Controls whether Sliding Sync metrics should be proxied (exposed) on `matrix.example.com/metrics/sliding-sync`
 matrix_sliding_sync_metrics_proxying_enabled: false
 matrix_sliding_sync_metrics_proxying_hostname: ''
 matrix_sliding_sync_metrics_proxying_path: /metrics/sliding-sync

roles/custom/matrix-static-files/defaults/main.yml

@@ -386,6 +386,6 @@ matrix_static_files_self_check_well_known_matrix_client_follow_redirects: none
 # TODO - review this one
 # Specifies where requests for the root URI (`/`) on the `matrix.` domain should be redirected.
 # If this has an empty value, they're just passed to the homeserver, which serves a static page.
-# If you'd like to make `https://matrix.DOMAIN` redirect to `https://element.DOMAIN` (or something of that sort), specify the domain name here.
-# Example value: `element.DOMAIN` (or `{{ matrix_server_fqn_element }}`).
+# If you'd like to make `https://matrix.example.com` redirect to `https://element.example.com` (or something of that sort), specify the domain name here.
+# Example value: `element.example.com` (or `{{ matrix_server_fqn_element }}`).
 matrix_static_files_client_redirect_root_uri_to_domain: ""

roles/custom/matrix-synapse-usage-exporter/defaults/main.yml

@@ -51,7 +51,7 @@ matrix_synapse_usage_exporter_container_extra_arguments: []
 
 # Controls whether the synapse-usage-exporter's web services should be proxied (exposed publicly).
 #
-# Exposure happens on `matrix.DOMAIN/report-usage-stats/push` by default.
+# Exposure happens on `matrix.example.com/report-usage-stats/push` by default.
 # See: `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix`.
 matrix_synapse_usage_exporter_proxying_enabled: false
 

roles/custom/matrix-synapse/defaults/main.yml

@@ -733,8 +733,8 @@ matrix_synapse_grafana_dashboard_urls:
   - https://raw.githubusercontent.com/element-hq/synapse/master/contrib/grafana/synapse.json
 
 # Controls whether Synapse metrics should be proxied (exposed) on:
-# - `matrix.DOMAIN/metrics/synapse/main-process` for the main process
-# - `matrix.DOMAIN/metrics/synapse/worker/{type}-{id}` for each worker process
+# - `matrix.example.com/metrics/synapse/main-process` for the main process
+# - `matrix.example.com/metrics/synapse/worker/{type}-{id}` for each worker process
 matrix_synapse_metrics_proxying_enabled: false
 matrix_synapse_metrics_proxying_hostname: ''
 matrix_synapse_metrics_proxying_path_prefix: /metrics/synapse