Slavi Pantaleev 7d3adc4512 Automatically force-pull :latest images ... 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).		2019-06-10 14:30:28 +03:00
..
init.yml
main.yml
setup_install.yml	Automatically force-pull :latest images	2019-06-10 14:30:28 +03:00
setup_uninstall.yml
validate_config.yml	Add support for more flexible container port exposing	2019-05-25 07:41:08 +09:00