deploy: c9bf644fa0c2c06f8143b14ccdb655feebed97df

1 files changed, 0 insertions, 16 deletions

diff --git a/develop/workers.html b/develop/workers.html

index 415e722bea..69b16be88e 100644
--- a/develop/workers.html
+++ b/develop/workers.html
@@ -621,22 +621,6 @@ the stream writer for the <code>receipts</code> stream:</p>
 the stream writer for the <code>presence</code> stream:</p>
 <pre><code>^/_matrix/client/(api/v1|r0|v3|unstable)/presence/
 </code></pre>
-<h4 id="restrict-outbound-federation-traffic-to-a-specific-set-of-workers"><a class="header" href="#restrict-outbound-federation-traffic-to-a-specific-set-of-workers">Restrict outbound federation traffic to a specific set of workers</a></h4>
-<p>The <code>outbound_federation_restricted_to</code> configuration is useful to make sure outbound
-federation traffic only goes through a specified subset of workers. This allows you to
-set more strict access controls (like a firewall) for all workers and only allow the
-<code>federation_sender</code>'s to contact the outside world.</p>
-<pre><code class="language-yaml">instance_map:
-    main:
-        host: localhost
-        port: 8030
-    federation_sender1:
-        host: localhost
-        port: 8034
-
-outbound_federation_restricted_to:
-  - federation_sender1
-</code></pre>
 <h4 id="background-tasks"><a class="header" href="#background-tasks">Background tasks</a></h4>
 <p>There is also support for moving background tasks to a separate
 worker. Background tasks are run periodically or started via replication. Exactly