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).
23 lines
815 B
YAML
23 lines
815 B
YAML
matrix_mailer_enabled: true
|
|
|
|
matrix_mailer_base_path: "{{ matrix_base_data_path }}/mailer"
|
|
|
|
matrix_mailer_docker_image: "devture/exim-relay:4.91-r3-0"
|
|
matrix_mailer_docker_image_force_pull: "{{ matrix_mailer_docker_image.endswith(':latest') }}"
|
|
|
|
# The user/group that the container runs with.
|
|
# These match the `exim` user/group within the container image.
|
|
matrix_mailer_container_user_uid: 100
|
|
matrix_mailer_container_user_gid: 101
|
|
|
|
# A list of extra arguments to pass to the container
|
|
matrix_mailer_container_extra_arguments: []
|
|
|
|
matrix_mailer_sender_address: "matrix@{{ matrix_domain }}"
|
|
matrix_mailer_relay_use: false
|
|
matrix_mailer_relay_host_name: "mail.example.com"
|
|
matrix_mailer_relay_host_port: 587
|
|
matrix_mailer_relay_auth: false
|
|
matrix_mailer_relay_auth_username: ""
|
|
matrix_mailer_relay_auth_password: ""
|