docs
examples
group_vars
inventory
roles
matrix-base
matrix-bridge-appservice-discord
matrix-bridge-appservice-irc
matrix-bridge-mautrix-facebook
matrix-bridge-mautrix-telegram
matrix-bridge-mautrix-whatsapp
matrix-common-after
matrix-corporal
matrix-coturn
matrix-dimension
matrix-mailer
matrix-mxisd
matrix-nginx-proxy
matrix-postgres
matrix-riot-web
matrix-synapse
defaults
tasks
ext
ldap-auth
rest-auth
setup.yml
setup_install.yml
setup_uninstall.yml
shared-secret-auth
setup.yml
goofys
synapse
import_media_store.yml
init.yml
main.yml
register_user.yml
self_check_client_api.yml
self_check_federation_api.yml
setup_synapse.yml
update_user_password.yml
validate_config.yml
templates
vars
.editorconfig
.gitignore
CHANGELOG.md
LICENSE
README.md
ansible.cfg
setup.yml
70487061f4
This doesn't replace all usage of `-v`, but it's a start. People sometimes troubleshoot by deleting files (especially bridge config files). Restarting Synapse with a missing registration.yaml file for a given bridge, causes the `-v /something/registration.yaml:/something/registration.yaml:ro` option to force-create `/something/registration.yaml` as a directory. When a path that's provided to the `-v` option is missing, Docker auto-creates that path as a directory. This causes more breakage and confusion later on. We'd rather fail, instead of magically creating directories. Using `--mount`, instead of `-v` is the solution to this. From Docker's documentation: > When you use --mount with type=bind, the host-path must refer to an existing path on the host. > The path will not be created for you and the service will fail with an error if the path does not exist.