Run codespell --write-changes
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This commit is contained in:
Suguru Hirahara
committed by
Slavi Pantaleev
Slavi Pantaleev
parent
0152758f5d
commit
3653f9f89b
@ -50,7 +50,7 @@ matrix_appservice_draupnir_for_all_systemd_wanted_services_list: []
|
||||
# anyone in this room can use the bot - secure your room!
|
||||
# This should be a room alias - not a matrix.to URL.
|
||||
# Note: Draupnir is fairly verbose - expect a lot of messages from it.
|
||||
# This room is diffrent for Appservice Mode compared to normal mode.
|
||||
# This room is different for Appservice Mode compared to normal mode.
|
||||
# In Appservice mode it provides functions like user management.
|
||||
matrix_appservice_draupnir_for_all_config_adminRoom: "" # noqa var-naming
|
||||
|
||||
|
||||
@ -217,7 +217,7 @@ matrix_homeserver_container_url: "http://{{ matrix_homeserver_container_client_a
|
||||
|
||||
# Specifies where the homeserver's Client-Server API is on the container network (matrix_homeserver_container_network).
|
||||
# Where this is depends on whether there's a reverse-proxy in front of the homeserver, which homeserver it is, etc.
|
||||
# This likely gets overriden elsewhere.
|
||||
# This likely gets overridden elsewhere.
|
||||
matrix_homeserver_container_client_api_endpoint: ""
|
||||
|
||||
# Specifies where the homeserver's Federation API is on the container network (matrix_homeserver_container_network).
|
||||
@ -225,7 +225,7 @@ matrix_homeserver_container_federation_url: "http://{{ matrix_homeserver_contain
|
||||
|
||||
# Specifies where the homeserver's Federation API is on the container network (matrix_homeserver_container_network).
|
||||
# Where this is depends on whether there's a reverse-proxy in front of the homeserver, which homeserver it is, etc.
|
||||
# This likely gets overriden elsewhere.
|
||||
# This likely gets overridden elsewhere.
|
||||
matrix_homeserver_container_federation_api_endpoint: ""
|
||||
|
||||
# Specifies the public url of the Sync v3 (sliding-sync) API.
|
||||
|
||||
@ -104,7 +104,7 @@
|
||||
msg: >-
|
||||
Your configuration enables both the old mautrix-instagram bridge and the new mautrix-meta-instagram bridge.
|
||||
By default, both bridges are configured to use the same bridge bot username (`@{{ matrix_mautrix_meta_instagram_appservice_username }}:{{ matrix_domain }}`) which is a conflict.
|
||||
We recommend that you disable at least one of the bridges (preferrably the old mautrix-instagram bridge), or to resolve the conflict in another way.
|
||||
We recommend that you disable at least one of the bridges (preferably the old mautrix-instagram bridge), or to resolve the conflict in another way.
|
||||
To resolve the conflict without disabling a bridge, consider adjusting one of `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username` - they both have a value of {{ matrix_mautrix_meta_instagram_appservice_username }} right now.
|
||||
when:
|
||||
- matrix_mautrix_instagram_enabled | bool
|
||||
|
||||
@ -20,7 +20,7 @@
|
||||
- name: Fail if OpenAI configuration not up-to-date.
|
||||
ansible.builtin.fail:
|
||||
msg: >-
|
||||
Your configuration contains a varible that is no longer used.
|
||||
Your configuration contains a variable that is no longer used.
|
||||
Please change your configuration to remove the variable (`{{ item.name }}`).
|
||||
when: "item.name in vars"
|
||||
with_items:
|
||||
|
||||
@ -63,7 +63,7 @@
|
||||
ansible.builtin.fail:
|
||||
msg: >-
|
||||
Your configuration is trying to enable matrix_bot_draupnir_config_experimentalRustCrypto and matrix_bot_draupnir_pantalaimon_use at the same time.
|
||||
These settings are mutually incompatible and therefore cant be used at the same time.
|
||||
These settings are mutually incompatible and therefore can't be used at the same time.
|
||||
when:
|
||||
- matrix_bot_draupnir_pantalaimon_use
|
||||
- matrix_bot_draupnir_config_experimentalRustCrypto
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
bridge:
|
||||
# Domain part of the bridge, e.g. matrix.org
|
||||
domain: {{ matrix_appservice_discord_bridge_domain|to_json }}
|
||||
# This should be your publically facing URL because Discord may use it to
|
||||
# This should be your publicly facing URL because Discord may use it to
|
||||
# fetch media from the media store.
|
||||
homeserverUrl: {{ matrix_appservice_discord_bridge_homeserverUrl|to_json }}
|
||||
# Interval at which to process users in the 'presence queue'. If you have
|
||||
|
||||
@ -358,7 +358,7 @@ matrix_appservice_irc_ircService_servers: [] # noqa var-naming
|
||||
# # not apply an idle timeout. This value is ignored if this IRC server is
|
||||
# # mirroring Matrix membership lists to IRC. Default: 172800 (48 hours)
|
||||
# idleTimeout: 10800
|
||||
# # The number of millseconds to wait between consecutive reconnections if a
|
||||
# # The number of milliseconds to wait between consecutive reconnections if a
|
||||
# # client gets disconnected. Setting to 0 will cause the scheduling to be
|
||||
# # disabled, i.e. it will be scheduled immediately (with jitter.
|
||||
# # Otherwise, the scheduling interval will be used such that one client
|
||||
|
||||
@ -224,7 +224,7 @@ logging:
|
||||
# The directory for log files. Will be created if not found.
|
||||
directory: ./logs
|
||||
# Available variables: .Date for the file date and .Index for different log files on the same day.
|
||||
# empy/null = journal logging only
|
||||
# empty/null = journal logging only
|
||||
file_name_format:
|
||||
# Date format for file names in the Go time format: https://golang.org/pkg/time/#pkg-constants
|
||||
file_date_format: "2006-01-02"
|
||||
|
||||
@ -22,7 +22,7 @@
|
||||
when: matrix_appservice_slack_enabled | default(False) | bool and matrix_mautrix_slack_appservice_bot_username == matrix_appservice_slack_bot_name | default ('')
|
||||
ansible.builtin.fail:
|
||||
msg: |
|
||||
The appservice-slack and mautrix-slack components are both enabled and use the same bot username ({{ matrix_mautrix_slack_appservice_bot_username }}), as per their default configuration, which causes a conflcit.
|
||||
The appservice-slack and mautrix-slack components are both enabled and use the same bot username ({{ matrix_mautrix_slack_appservice_bot_username }}), as per their default configuration, which causes a conflict.
|
||||
To resolve the conflict, make one of these components use a different username.
|
||||
Consider either changing `matrix_mautrix_slack_appservice_bot_username` (the bot username for the mautrix-slack component) or `matrix_appservice_slack_bot_name` (the bot username for the appservice-slack component).
|
||||
We recommend that you change the username for the newly-added (and yet unused) component.
|
||||
|
||||
@ -586,7 +586,7 @@ trusted_servers = {{ matrix_conduwuit_trusted_servers | to_json }}
|
||||
# specifically on room joins. This option limits the exposure to a
|
||||
# compromised trusted server to room joins only. The join operation
|
||||
# requires gathering keys from many origin servers which can cause
|
||||
# significant delays. Therefor this defaults to true to mitigate
|
||||
# significant delays. Therefore this defaults to true to mitigate
|
||||
# unexpected delays out-of-the-box. The security-paranoid or those willing
|
||||
# to tolerate delays are advised to set this to false. Note that setting
|
||||
# query_trusted_key_servers_first to true causes this option to be
|
||||
@ -597,7 +597,7 @@ trusted_servers = {{ matrix_conduwuit_trusted_servers | to_json }}
|
||||
# Only query trusted servers for keys and never the origin server. This is
|
||||
# intended for clusters or custom deployments using their trusted_servers
|
||||
# as forwarding-agents to cache and deduplicate requests. Notary servers
|
||||
# do not act as forwarding-agents by default, therefor do not enable this
|
||||
# do not act as forwarding-agents by default, therefore do not enable this
|
||||
# unless you know exactly what you are doing.
|
||||
#
|
||||
#only_query_trusted_key_servers = false
|
||||
|
||||
@ -586,7 +586,7 @@ trusted_servers = {{ matrix_continuwuity_trusted_servers | to_json }}
|
||||
# specifically on room joins. This option limits the exposure to a
|
||||
# compromised trusted server to room joins only. The join operation
|
||||
# requires gathering keys from many origin servers which can cause
|
||||
# significant delays. Therefor this defaults to true to mitigate
|
||||
# significant delays. Therefore this defaults to true to mitigate
|
||||
# unexpected delays out-of-the-box. The security-paranoid or those willing
|
||||
# to tolerate delays are advised to set this to false. Note that setting
|
||||
# query_trusted_key_servers_first to true causes this option to be
|
||||
@ -597,7 +597,7 @@ trusted_servers = {{ matrix_continuwuity_trusted_servers | to_json }}
|
||||
# Only query trusted servers for keys and never the origin server. This is
|
||||
# intended for clusters or custom deployments using their trusted_servers
|
||||
# as forwarding-agents to cache and deduplicate requests. Notary servers
|
||||
# do not act as forwarding-agents by default, therefor do not enable this
|
||||
# do not act as forwarding-agents by default, therefore do not enable this
|
||||
# unless you know exactly what you are doing.
|
||||
#
|
||||
#only_query_trusted_key_servers = false
|
||||
|
||||
@ -34,7 +34,7 @@ matrix_coturn_docker_image_force_pull: "{{ matrix_coturn_docker_image.endswith('
|
||||
# The Docker network that coturn would be put into.
|
||||
#
|
||||
# Because coturn relays traffic to unvalidated IP addresses,
|
||||
# using a dedicated network, isolated from other Docker (and local) services is preferrable.
|
||||
# using a dedicated network, isolated from other Docker (and local) services is preferable.
|
||||
#
|
||||
# Setting up deny/allow rules with `matrix_coturn_allowed_peer_ips`/`matrix_coturn_denied_peer_ips` is also
|
||||
# possible for achieving such isolation, but is more complicated due to the dynamic nature of Docker networking.
|
||||
|
||||
@ -355,7 +355,7 @@ matrix_dendrite_user_api_auto_join_rooms: []
|
||||
# name, number of active users and some information on your deployment config.
|
||||
matrix_dendrite_report_stats: false
|
||||
|
||||
# Contorls whether thumbnails for media content are generated dynamically
|
||||
# Controls whether thumbnails for media content are generated dynamically
|
||||
matrix_dendrite_media_api_dynamic_thumbnails: false
|
||||
matrix_dendrite_media_api_max_thumbnail_generators: 10
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ matrix_dynamic_dns_container_additional_networks: "{{ matrix_dynamic_dns_contain
|
||||
matrix_dynamic_dns_container_additional_networks_auto: []
|
||||
matrix_dynamic_dns_container_additional_networks_custom: []
|
||||
|
||||
# List of extra arguments to pass to the ontainer mode
|
||||
# List of extra arguments to pass to the container mode
|
||||
matrix_dynamic_dns_container_extra_arguments: []
|
||||
|
||||
# List of wanted services when running in mode
|
||||
|
||||
@ -150,7 +150,7 @@ matrix_ma1sd_database_name: 'matrix_ma1sd'
|
||||
matrix_ma1sd_database_connection_string: 'postgresql://{{ matrix_ma1sd_database_username }}:{{ matrix_ma1sd_database_password }}@{{ matrix_ma1sd_database_hostname }}:{{ matrix_ma1sd_database_port }}/{{ matrix_ma1sd_database_name }}'
|
||||
|
||||
|
||||
# ma1sd has serveral supported identity stores.
|
||||
# ma1sd has several supported identity stores.
|
||||
# One of them is storing identities directly in Synapse's database.
|
||||
# Learn more here: https://github.com/ma1uta/ma1sd/blob/master/docs/stores/synapse.md
|
||||
matrix_ma1sd_synapsesql_enabled: false
|
||||
|
||||
@ -131,7 +131,7 @@
|
||||
"refId": "B"
|
||||
}
|
||||
],
|
||||
"title": "HTTP Requsts",
|
||||
"title": "HTTP Requests",
|
||||
"type": "timeseries"
|
||||
},
|
||||
{
|
||||
|
||||
@ -16,7 +16,7 @@
|
||||
- {'old': 'matrix_prometheus_nginxlog_exporter_container_hostname', 'new': 'matrix_prometheus_nginxlog_exporter_identifier'}
|
||||
- {'old': 'matrix_prometheus_nginxlog_exporter_docker_image_name_prefix', 'new': 'matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix'}
|
||||
|
||||
- name: Fail if docker image not availble for arch
|
||||
- name: Fail if docker image not available for arch
|
||||
ansible.builtin.fail:
|
||||
msg: >
|
||||
'prometheus-nginxlog-exporter' docker image is not available for your arch '{{ matrix_architecture }}'.
|
||||
|
||||
@ -501,7 +501,7 @@ matrix_synapse_tls_federation_listener_enabled: true
|
||||
matrix_synapse_tls_certificate_path: "/data/{{ matrix_server_fqn_matrix }}.tls.crt"
|
||||
matrix_synapse_tls_private_key_path: "/data/{{ matrix_server_fqn_matrix }}.tls.key"
|
||||
|
||||
# Resource names used by the unsecure HTTP listener. Here only the Client API
|
||||
# Resource names used by the insecure HTTP listener. Here only the Client API
|
||||
# is defined, see the homeserver config for a full list of valid resource
|
||||
# names.
|
||||
matrix_synapse_http_listener_resource_names: ["client"]
|
||||
@ -835,7 +835,7 @@ matrix_synapse_workers_enabled: false
|
||||
|
||||
# Specifies worker configuration that should be used when workers are enabled.
|
||||
#
|
||||
# The posible values (as seen in `matrix_synapse_workers_presets`) are:
|
||||
# The possible values (as seen in `matrix_synapse_workers_presets`) are:
|
||||
# - "little-federation-helper" - a very minimal worker configuration to improve federation performance
|
||||
# - "one-of-each" - one worker of each supported type + a generic worker
|
||||
# - "specialized-workers" - one worker of each supported type + specialized workers
|
||||
@ -1458,7 +1458,7 @@ matrix_synapse_ext_encryption_disabler_deny_encryption_for_rooms_of: ["{{ matrix
|
||||
# Specifies whether the power levels event (setting) provided during room creation should be patched.
|
||||
# This makes it impossible for anybody (locally or over federation) from enabling room encryption
|
||||
# for the lifetime of rooms created while this setting is enabled (irreversible).
|
||||
# Enabling this may have incompatiblity consequences with servers / clients.
|
||||
# Enabling this may have incompatibility consequences with servers / clients.
|
||||
# Familiarize yourself with the caveats upstream: https://github.com/digitalentity/matrix_encryption_disabler
|
||||
matrix_synapse_ext_encryption_disabler_patch_power_levels: false
|
||||
matrix_synapse_ext_encryption_config: "{{ matrix_synapse_ext_encryption_config_yaml | from_yaml }}"
|
||||
|
||||
@ -305,7 +305,7 @@ listeners:
|
||||
compress: false
|
||||
{% endif %}
|
||||
|
||||
# Unsecure HTTP listener (Client API): for when Matrix traffic passes through a reverse proxy
|
||||
# Insecure HTTP listener (Client API): for when Matrix traffic passes through a reverse proxy
|
||||
# that unwraps TLS.
|
||||
- port: {{ matrix_synapse_container_client_api_port|to_json }}
|
||||
tls: false
|
||||
@ -318,7 +318,7 @@ listeners:
|
||||
compress: false
|
||||
|
||||
{% if matrix_synapse_federation_port_enabled %}
|
||||
# Unsecure HTTP listener (Federation API): for when Matrix traffic passes through a reverse proxy
|
||||
# Insecure HTTP listener (Federation API): for when Matrix traffic passes through a reverse proxy
|
||||
# that unwraps TLS.
|
||||
- port: {{ matrix_synapse_container_federation_api_plain_port|to_json }}
|
||||
tls: false
|
||||
@ -1709,7 +1709,7 @@ old_signing_keys:
|
||||
# Additional security can be provided by configuring a `verify key`, which
|
||||
# will make synapse check that the response is signed by that key.
|
||||
#
|
||||
# This setting supercedes an older setting named `perspectives`. The old format
|
||||
# This setting supersedes an older setting named `perspectives`. The old format
|
||||
# is still supported for backwards-compatibility, but it is deprecated.
|
||||
#
|
||||
# 'trusted_key_servers' defaults to matrix.org, but using it will generate a
|
||||
|
||||
@ -7,7 +7,7 @@
|
||||
|
||||
- tags:
|
||||
# This role intentionally doesn't do work on a `setup-all` tag.
|
||||
# If it did, the initial installation (`--tags=setup-all`) would also potentially polute the database with data,
|
||||
# If it did, the initial installation (`--tags=setup-all`) would also potentially pollute the database with data,
|
||||
# which would make importing a database dump problematic.
|
||||
#
|
||||
# See the variable "matrix_user_creator_users_auto" on group_vars/matrix_servers for actual values of users which running these tags can create with this role by default.
|
||||
|
||||
@ -81,7 +81,7 @@ matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks
|
||||
matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: true
|
||||
|
||||
# Controls whether this role will delete old files left over from `matrix-nginx-proxy`.
|
||||
# Regardless of this value, if discovered, a `matrix-nginx-proxy.service` systemd serivce will be stopped and removed.
|
||||
# Regardless of this value, if discovered, a `matrix-nginx-proxy.service` systemd service will be stopped and removed.
|
||||
matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: true
|
||||
|
||||
# Controls whether this role will try to detect and clean up the /matrix/ssl files.
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
# Later, when they stopped setting these options, they were stuck with the configuration file that still retained them.
|
||||
#
|
||||
# Here, we make the file go away of no options are set.
|
||||
# Idealy, this task would be part of the `ansible-role-docker` role, but it's not (yet).
|
||||
# Ideally, this task would be part of the `ansible-role-docker` role, but it's not (yet).
|
||||
# See: https://github.com/geerlingguy/ansible-role-docker/pull/498
|
||||
- name: Ensure the Docker daemon options file is deleted when no longer needed
|
||||
when: matrix_playbook_docker_installation_daemon_options.keys() | length == 0
|
||||
|
||||
Reference in New Issue
Block a user