This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Ability to 100% disable all federation for a synapse #2619
Comments
+1 |
why yes it is :) |
What is the procedure, please? |
@kcsrnd Have you read my comment on issue #2820? |
I thought I had, somehow I missed your comment at the bottom. Got it now. Thanks. |
Is there a Guide how to setup a separate isolated federation cluster? |
As of #2820 you can put the following in your config:
|
d3m3vilurr
added a commit
to d3m3vilurr/matrix-dockers
that referenced
this issue
Jun 26, 2019
this option is stressful & reduce server performance. ref: - matrix-org/synapse#2619 - matrix-org/synapse#2917
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So far we've recommended people who want a non-federated synapse to disable inbound federation by removing the federation listener. However, in practice it seems that the synapse may will emit outbound federated traffic (e.g. for invites) which will never complete. Having a config option to cleanly and completely disable federation seems like a no-brainer. I thought we already had an ancient 2014-vintage bug for this, but can't find it anywhere.
The text was updated successfully, but these errors were encountered: