mirror of
https://github.com/YunoHost-Apps/gotosocial_ynh.git
synced 2024-09-03 19:16:06 +02:00
upgrading config according to v0.11.0
This commit is contained in:
OniriCorpe
parent
f111cdbfb4
commit
36a2a744dc
1 changed files with 30 additions and 107 deletions
137
conf/config.yaml
137
conf/config.yaml
|
|
@ -195,10 +195,6 @@ db-tls-ca-cert: ""
|
|||
#
|
||||
# If you set the multiplier to less than 1, only one open connection will be used regardless of cpu count.
|
||||
#
|
||||
# PLEASE NOTE!!: This setting currently only applies for Postgres. SQLite will always use 1 connection regardless
|
||||
# of what is set here. This behavior will change in future when we implement better SQLITE_BUSY handling.
|
||||
# See https://github.com/superseriousbusiness/gotosocial/issues/1407 for more details.
|
||||
#
|
||||
# Examples: [16, 8, 10, 2]
|
||||
# Default: 8
|
||||
db-max-open-conns-multiplier: 8
|
||||
|
|
@ -236,107 +232,13 @@ db-sqlite-cache-size: "8MiB"
|
|||
db-sqlite-busy-timeout: "30m"
|
||||
|
||||
cache:
|
||||
# Cache configuration options:
|
||||
#
|
||||
# max-size = maximum cached objects count
|
||||
# ttl = cached object lifetime
|
||||
# sweep-freq = frequency to look for stale cache objects
|
||||
# (zero will disable cache sweeping)
|
||||
|
||||
#############################
|
||||
#### VISIBILITY CACHES ######
|
||||
#############################
|
||||
#
|
||||
# Configure Status and account
|
||||
# visibility cache.
|
||||
|
||||
visibility-max-size: 2000
|
||||
visibility-ttl: "30m"
|
||||
visibility-sweep-freq: "1m"
|
||||
|
||||
gts:
|
||||
###########################
|
||||
#### DATABASE CACHES ######
|
||||
###########################
|
||||
#
|
||||
# Configure GTS database
|
||||
# model caches.
|
||||
|
||||
account-max-size: 2000
|
||||
account-ttl: "30m"
|
||||
account-sweep-freq: "1m"
|
||||
|
||||
block-max-size: 1000
|
||||
block-ttl: "30m"
|
||||
block-sweep-freq: "1m"
|
||||
|
||||
domain-block-max-size: 2000
|
||||
domain-block-ttl: "24h"
|
||||
domain-block-sweep-freq: "1m"
|
||||
|
||||
emoji-max-size: 2000
|
||||
emoji-ttl: "30m"
|
||||
emoji-sweep-freq: "1m"
|
||||
|
||||
emoji-category-max-size: 100
|
||||
emoji-category-ttl: "30m"
|
||||
emoji-category-sweep-freq: "1m"
|
||||
|
||||
follow-max-size: 2000
|
||||
follow-ttl: "30m"
|
||||
follow-sweep-freq: "1m"
|
||||
|
||||
follow-request-max-size: 2000
|
||||
follow-request-ttl: "30m"
|
||||
follow-request-sweep-freq: "1m"
|
||||
|
||||
instance-max-size: 2000
|
||||
instance-ttl: "30m"
|
||||
instance-sweep-freq: "1m"
|
||||
|
||||
list-max-size: 2000
|
||||
list-ttl: "30m"
|
||||
list-sweep-freq: "1m"
|
||||
|
||||
list-entry-max-size: 2000
|
||||
list-entry-ttl: "30m"
|
||||
list-entry-sweep-freq: "1m"
|
||||
|
||||
media-max-size: 1000
|
||||
media-ttl: "30m"
|
||||
media-sweep-freq: "1m"
|
||||
|
||||
mention-max-size: 2000
|
||||
mention-ttl: "30m"
|
||||
mention-sweep-freq: "1m"
|
||||
|
||||
notification-max-size: 1000
|
||||
notification-ttl: "30m"
|
||||
notification-sweep-freq: "1m"
|
||||
|
||||
report-max-size: 100
|
||||
report-ttl: "30m"
|
||||
report-sweep-freq: "1m"
|
||||
|
||||
status-max-size: 2000
|
||||
status-ttl: "30m"
|
||||
status-sweep-freq: "1m"
|
||||
|
||||
status-fave-max-size: 2000
|
||||
status-fave-ttl: "30m"
|
||||
status-fave-sweep-freq: "1m"
|
||||
|
||||
tombstone-max-size: 500
|
||||
tombstone-ttl: "30m"
|
||||
tombstone-sweep-freq: "1m"
|
||||
|
||||
user-max-size: 500
|
||||
user-ttl: "30m"
|
||||
user-sweep-freq: "1m"
|
||||
|
||||
webfinger-max-size: 250
|
||||
webfinger-ttl: "24h"
|
||||
webfinger-sweep-freq: "15m"
|
||||
# cache.memory-target sets a target limit that
|
||||
# the application will try to keep it's caches
|
||||
# within. This is based on estimated sizes of
|
||||
# in-memory objects, and so NOT AT ALL EXACT.
|
||||
# Examples: ["100MiB", "200MiB", "500MiB", "1GiB"]
|
||||
# Default: "100MiB"
|
||||
memory-target: "100MiB"
|
||||
|
||||
######################
|
||||
##### WEB CONFIG #####
|
||||
|
|
@ -401,6 +303,15 @@ instance-expose-public-timeline: __INSTANCE_EXPOSE_PUBLIC_TIMELINE__
|
|||
# Default: true
|
||||
instance-deliver-to-shared-inboxes: __INSTANCE_DELIVER_TO_SHARED_INBOXES__
|
||||
|
||||
# Bool. This flag will inject a Mastodon version into the version field that
|
||||
# is included in /api/v1/instance. This version is often used by Mastodon clients
|
||||
# to do API feature detection. By injecting a Mastodon compatible version, it is
|
||||
# possible to cajole those clients to behave correctly with GoToSocial.
|
||||
#
|
||||
# Options: [true, false]
|
||||
# Default: false
|
||||
instance-inject-mastodon-version: false
|
||||
|
||||
###########################
|
||||
##### ACCOUNTS CONFIG #####
|
||||
###########################
|
||||
|
|
@ -478,8 +389,8 @@ media-description-max-chars: __MEDIA_DESCRIPTION_MAX_CHARS__
|
|||
# are kept so that it can be fetched again if requested by a user.
|
||||
#
|
||||
# If this is set to 0, then media from remote instances will be cached indefinitely.
|
||||
# Examples: [30, 60, 7, 0]
|
||||
# Default: 30
|
||||
# Examples: 7
|
||||
# Default: 7
|
||||
media-remote-cache-days: __MEDIA_REMOTE_CACHE_DAYS__
|
||||
|
||||
# Int. Max size in bytes of emojis uploaded to this instance via the admin API.
|
||||
|
|
@ -872,6 +783,18 @@ http-client:
|
|||
allow-ips: []
|
||||
block-ips: []
|
||||
|
||||
# Bool. Disable verification of TLS certificates of remote servers.
|
||||
# With this set to 'true', GoToSocial will not error when a remote
|
||||
# server presents an invalid or self-signed certificate.
|
||||
#
|
||||
# THIS SETTING SHOULD BE USED FOR TESTING ONLY! IF YOU TURN THIS
|
||||
# ON WHILE RUNNING IN PRODUCTION YOU ARE LEAVING YOUR SERVER WIDE
|
||||
# OPEN TO MAN IN THE MIDDLE ATTACKS! DO NOT CHANGE THIS SETTING
|
||||
# UNLESS YOU KNOW EXACTLY WHAT YOU'RE DOING AND WHY YOU'RE DOING IT.
|
||||
#
|
||||
# Default: false
|
||||
tls-insecure-skip-verify: false
|
||||
|
||||
#############################
|
||||
##### ADVANCED SETTINGS #####
|
||||
#############################
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue