From d70465313b005be530fe498ab67594376aa39b25 Mon Sep 17 00:00:00 2001
From: MadLittleMods <MadLittleMods@users.noreply.github.com>
Date: Wed, 5 Jul 2023 23:54:53 +0000
Subject: deploy: b07b14b494ae1dd564b4c44f844c9a9545b3d08a

---
 develop/workers.html | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

(limited to 'develop/workers.html')

diff --git a/develop/workers.html b/develop/workers.html
index 691d228990..4b896abc35 100644
--- a/develop/workers.html
+++ b/develop/workers.html
@@ -628,6 +628,22 @@ 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
-- 
cgit 1.4.1