From f262065ee3d1f479a2b6a17b5bff7ae13d82e218 Mon Sep 17 00:00:00 2001 From: Dan Anglin Date: Mon, 17 Jun 2024 22:55:11 +0100 Subject: [PATCH] fix: update GTS config template Update the GTS config template for the 0.16.0 release. --- templates/gotosocial/config.yaml.gotmpl | 26 ++++++++++--------------- 1 file changed, 10 insertions(+), 16 deletions(-) diff --git a/templates/gotosocial/config.yaml.gotmpl b/templates/gotosocial/config.yaml.gotmpl index bb455be..68b66d9 100644 --- a/templates/gotosocial/config.yaml.gotmpl +++ b/templates/gotosocial/config.yaml.gotmpl @@ -122,6 +122,7 @@ port: {{ .GoToSocial.Port }} # Example: ["127.0.0.1/32", "172.20.0.1"] # Default: ["127.0.0.1/32", "::1"] (localhost ipv4 + ipv6) trusted-proxies: +- "127.0.0.1/32" - "{{ .Docker.Network.Subnet }}" ############################ @@ -405,16 +406,12 @@ instance-inject-mastodon-version: false # Config pertaining to creation and maintenance of accounts on the server, as well as defaults for new accounts. -# Bool. Do we want people to be able to just submit sign up requests, or do we want invite only? +# Bool. Allow people to submit new sign-up / registration requests via the form at /signup. +# # Options: [true, false] -# Default: true +# Default: false accounts-registration-open: {{ .GoToSocial.AccountsRegistrationOpen }} -# Bool. Do sign up requests require approval from an admin/moderator before an account can sign in/use the server? -# Options: [true, false] -# Default: true -accounts-approval-required: true - # Bool. Are sign up requests required to submit a reason for the request (eg., an explanation of why they want to join the instance)? # Options: [true, false] # Default: true @@ -1041,15 +1038,10 @@ advanced-throttling-multiplier: 8 # Default: "30s" advanced-throttling-retry-after: "30s" -# Int. CPU multiplier for the amount of goroutines to spawn in order to send messages via ActivityPub. -# Messages will be batched so that at most multiplier * CPU count messages will be sent out at once. -# This can be tuned to limit concurrent POSTing to remote inboxes, preventing your instance CPU -# usage from skyrocketing when an account with many followers posts a new status. -# -# Messages are split among available senders, and each sender processes its assigned messages in serial. -# For example, say a user with 1000 followers is on an instance with 2 CPUs. With the default multiplier -# of 2, this means 4 senders would be in process at once on this instance. When the user creates a new post, -# each sender would end up iterating through about 250 Create messages + delivering them to remote instances. +# Int. CPU multiplier for the fixed number of goroutines to spawn in order to send messages via ActivityPub. +# Messages will be batched and pushed to a singular queue, from which multiplier * CPU count goroutines will +# pull and attempt deliveries. This can be tuned to limit concurrent posting to remote inboxes, preventing +# your instance CPU usage skyrocketing when accounts with many followers post statuses. # # If you set this to 0 or less, only 1 sender will be used regardless of CPU count. This may be # useful in cases where you are working with very tight network or CPU constraints. @@ -1098,6 +1090,8 @@ advanced-csp-extra-uris: [] # # "allow" -- only requests that are explicitly allowed by header filters # will be accepted (unless they are also explicitly blocked). +# This mode is considered experimental and will almost certainly +# break access to your instance unless you are very careful. # # "" -- request header filtering disabled. #