iartamonov/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-05-02 18:22:23 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs/federation: correct documented default for room directory exposure

Browse Source 
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5178
This commit is contained in:
Slavi Pantaleev
2026-04-30 14:46:49 +03:00
parent 5901f491f4
commit 966368ed06
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuring-playbook-federation.md
+4 -4
View File
@@ -24,14 +24,14 @@ matrix_synapse_federation_domain_whitelist:
If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below).
## Exposing the room directory over federation
## Controlling exposure of the room directory over federation
By default, your server's public rooms directory is not exposed to other servers via federation.
By default, your server's public rooms directory is exposed to other servers via federation, so that public rooms hosted on your server can be discovered by users on other servers. This goes against the Synapse upstream default (which is `false`); see the [2023-10-23 changelog entry](../CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse) for the reasoning behind this choice.
To expose it, add the following configuration to your `vars.yml` file:
To prevent your public rooms directory from being exposed over federation (restoring the Synapse upstream default), add the following configuration to your `vars.yml` file:
```yaml
matrix_synapse_allow_public_rooms_over_federation: true
matrix_synapse_allow_public_rooms_over_federation: false
```
## Disabling federation