From 53bc7afa660307502c84a08cb227a6a603982b1e Mon Sep 17 00:00:00 2001 From: Julian Foad Date: Mon, 4 Nov 2019 17:07:23 +0000 Subject: [PATCH] Fix --mount syntax in examples s/type-bind/type=bind/g --- docs/howto-server-delegation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/howto-server-delegation.md b/docs/howto-server-delegation.md index 45ef12dc..9fa34326 100644 --- a/docs/howto-server-delegation.md +++ b/docs/howto-server-delegation.md @@ -90,7 +90,7 @@ If your files are not in `/matrix/ssl` but in some other location, you would nee ```yaml matrix_synapse_container_extra_arguments: - - "--mount type-bind,src=/some/path/on/the/host,dst=/some/path/inside/the/container,ro" + - "--mount type=bind,src=/some/path/on/the/host,dst=/some/path/inside/the/container,ro" ``` You then refer to them (for `matrix_nginx_proxy_proxy_matrix_federation_api_ssl_certificate` and `matrix_nginx_proxy_proxy_matrix_federation_api_ssl_certificate_key`) by using `/some/path/inside/the/container`. @@ -117,7 +117,7 @@ To do that, make sure the certificate files are mounted into the Synapse contain ```yaml matrix_synapse_container_extra_arguments: - - "--mount type-bind,src=/some/path/on/the/host,dst=/some/path/inside/the/container,ro" + - "--mount type=bind,src=/some/path/on/the/host,dst=/some/path/inside/the/container,ro" ``` You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`: