mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-11-07 08:02:30 +00:00
7d3adc4512
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).
56 lines
2.6 KiB
YAML
56 lines
2.6 KiB
YAML
# matrix-corporal is a reconciliator and gateway for a managed Matrix server.
|
|
# See: https://github.com/devture/matrix-corporal
|
|
|
|
matrix_corporal_enabled: true
|
|
|
|
# Controls whether the matrix-corporal container exposes its gateway HTTP port (tcp/41080 in the container).
|
|
#
|
|
# Takes an "<ip>:<port>" or "<port>" value (e.g. "127.0.0.1:41080"), or empty string to not expose.
|
|
matrix_corporal_container_http_gateway_host_bind_port: ''
|
|
|
|
# Controls whether the matrix-corporal container exposes its API HTTP port (tcp/41081 in the container).
|
|
#
|
|
# Takes an "<ip>:<port>" or "<port>" value (e.g. "127.0.0.1:41081"), or empty string to not expose.
|
|
matrix_corporal_container_http_api_host_bind_port: ''
|
|
|
|
# A list of extra arguments to pass to the container
|
|
matrix_corporal_container_extra_arguments: []
|
|
|
|
# List of systemd services that matrix-corporal.service depends on
|
|
matrix_corporal_systemd_required_services_list: ['docker.service']
|
|
|
|
matrix_corporal_docker_image: "devture/matrix-corporal:1.4.0"
|
|
matrix_corporal_docker_image_force_pull: "{{ matrix_corporal_docker_image.endswith(':latest') }}"
|
|
|
|
matrix_corporal_base_path: "{{ matrix_base_data_path }}/corporal"
|
|
matrix_corporal_config_dir_path: "{{ matrix_corporal_base_path }}/config"
|
|
matrix_corporal_cache_dir_path: "{{ matrix_corporal_base_path }}/cache"
|
|
matrix_corporal_var_dir_path: "{{ matrix_corporal_base_path }}/var"
|
|
|
|
matrix_corporal_matrix_homeserver_domain_name: "{{ matrix_domain }}"
|
|
|
|
# Controls where matrix-corporal can reach your Synapse server (e.g. "http://matrix-synapse:8008").
|
|
# If Synapse runs on the same machine, you may need to add its service to `matrix_corporal_systemd_required_services_list`.
|
|
matrix_corporal_matrix_homeserver_api_endpoint: ""
|
|
|
|
# The shared secret between matrix-corporal and Synapse's shared-secret-auth password provider module.
|
|
# To use matrix-corporal, the shared-secret-auth password provider needs to be enabled and the secret needs to be identical.
|
|
matrix_corporal_matrix_auth_shared_secret: ""
|
|
|
|
# The shared secret for registering users with Synapse.
|
|
# Needs to be identical to Synapse's `registration_shared_secret` setting.
|
|
matrix_corporal_matrix_registration_shared_secret: ""
|
|
|
|
matrix_corporal_matrix_timeout_milliseconds: 45000
|
|
|
|
matrix_corporal_reconciliation_retry_interval_milliseconds: 30000
|
|
matrix_corporal_reconciliation_user_id_local_part: "matrix-corporal"
|
|
|
|
matrix_corporal_http_api_enabled: false
|
|
matrix_corporal_http_api_auth_token: ""
|
|
|
|
# Matrix Corporal policy provider configuration (goes directly into the configuration's `PolicyProvider` value)
|
|
matrix_corporal_policy_provider_config: ""
|
|
|
|
matrix_corporal_debug: false
|