docs
examples
group_vars
inventory
roles
matrix-base
matrix-bridge-appservice-discord
matrix-bridge-appservice-irc
matrix-bridge-appservice-slack
matrix-bridge-mautrix-facebook
matrix-bridge-mautrix-hangouts
matrix-bridge-mautrix-telegram
matrix-bridge-mautrix-whatsapp
matrix-common-after
matrix-corporal
matrix-coturn
matrix-dimension
matrix-email2matrix
matrix-mailer
defaults
tasks
init.yml
main.yml
setup_mailer.yml
templates
matrix-mxisd
matrix-nginx-proxy
matrix-postgres
matrix-riot-web
matrix-synapse
.editorconfig
.gitignore
CHANGELOG.md
LICENSE
README.md
ansible.cfg
setup.yml
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).