summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSteven Fuchs <steven.fuchs@dockyard.com>2020-09-18 11:58:22 +0000
committerlain <lain@soykaf.club>2020-09-18 11:58:22 +0000
commitf2ef9735c52c648a03de4af41f19bb4ec857de03 (patch)
tree0c2b3f2ba7b582a2e8ae4a83dbef42e8132c7b47 /docs
parent49584a9928f02b461a0356332440084473ea6b69 (diff)
Federate data through persistent websocket connections
Diffstat (limited to 'docs')
-rw-r--r--docs/configuration/cheatsheet.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/configuration/cheatsheet.md b/docs/configuration/cheatsheet.md
index 054b8fe43..9a275294e 100644
--- a/docs/configuration/cheatsheet.md
+++ b/docs/configuration/cheatsheet.md
@@ -225,6 +225,16 @@ Enables the worker which processes posts scheduled for deletion. Pinned posts ar
* `enabled`: whether expired activities will be sent to the job queue to be deleted
+## FedSockets
+FedSockets is an experimental feature allowing for Pleroma backends to federate using a persistant websocket connection as opposed to making each federation a seperate http connection. This feature is currently off by default. It is configurable throught he following options.
+
+### :fedsockets
+* `enabled`: Enables FedSockets for this instance. `false` by default.
+* `connection_duration`: Time an idle websocket is kept open.
+* `rejection_duration`: Failures to connect via FedSockets will not be retried for this period of time.
+* `fed_socket_fetches` and `fed_socket_rejections`: Settings passed to `cachex` for the fetch registry, and rejection stacks. See `Pleroma.Web.FedSockets` for more details.
+
+
## Frontends
### :frontend_configurations