142 lines
5.1 KiB
YAML
142 lines
5.1 KiB
YAML
###########################
|
|
##### GENERAL CONFIG ######
|
|
###########################
|
|
|
|
# Default: ["127.0.0.1/32", "::1"] (localhost ipv4 + ipv6)
|
|
trusted-proxies:
|
|
- "127.0.0.1/32"
|
|
- "::1"
|
|
# https://docs.gotosocial.org/en/latest/api/ratelimiting/
|
|
# turn off rate limit
|
|
advanced-rate-limit-requests: 0
|
|
|
|
###########################
|
|
##### INSTANCE CONFIG #####
|
|
###########################
|
|
|
|
# https://docs.gotosocial.org/en/latest/configuration/
|
|
instance-languages: ["it", "en-gb"]
|
|
|
|
# String. Federation mode to use for this instance.
|
|
#
|
|
# "blocklist" -- open federation by default. Only instances that are explicitly
|
|
# blocked will be denied (unless they are also explicitly allowed).
|
|
#
|
|
# "allowlist" -- closed federation by default. Only instances that are explicitly
|
|
# allowed will be able to interact with this instance.
|
|
instance-federation-mode: "blocklist"
|
|
|
|
# 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: true
|
|
|
|
###########################
|
|
##### ACCOUNTS CONFIG #####
|
|
###########################
|
|
|
|
accounts-registration-open: false
|
|
|
|
###########################
|
|
##### STATUSES CONFIG #####
|
|
###########################
|
|
|
|
statuses-max-chars: 500
|
|
|
|
########################
|
|
##### MEDIA CONFIG #####
|
|
########################
|
|
|
|
# Config pertaining to media uploads (media, image descriptions, emoji).
|
|
|
|
# Size. Max size in bytes of media uploads via API.
|
|
#
|
|
# Raising this limit may cause other servers to not fetch media
|
|
# attached to a post.
|
|
media-local-max-size: 10MiB
|
|
|
|
# Size. Size in bytes of max image size referred to on /api/v_/instance endpoints,
|
|
# used by applications like Tusky to automatically scale locally uploaded media.
|
|
media-image-size-hint: 5MiB
|
|
|
|
# Size. Size in bytes of max video size referred to on /api/v_/instance endpoints,
|
|
# used by applications like Tusky to automatically scale locally uploaded media.
|
|
#
|
|
# Leaving this unset will default to media-local-max-size.
|
|
media-video-size-hint: 30MiB
|
|
|
|
# Size. Max size in bytes of media to download from other instances.
|
|
#
|
|
# Lowering this limit may cause your instance not to fetch post media.
|
|
media-remote-max-size: 40MiB
|
|
|
|
# Int. Minimum amount of characters required as an image or video description.
|
|
# Examples: [500, 1000, 1500]
|
|
# Default: 0 (not required)
|
|
media-description-min-chars: 0
|
|
|
|
# Int. Maximum amount of characters permitted in an image or video description.
|
|
# Examples: [1000, 1500, 3000]
|
|
# Default: 1500
|
|
media-description-max-chars: 1500
|
|
|
|
# Size. Max size in bytes of emojis uploaded to this instance via the admin API.
|
|
#
|
|
# The default is the same as the Mastodon size limit for emojis (50kb), which allows
|
|
# for good interoperability. Raising this limit may cause issues with federation
|
|
# of your emojis to other instances, so beware.
|
|
media-emoji-local-max-size: 50KiB
|
|
|
|
# Size. Max size in bytes of emojis to download from other instances.
|
|
#
|
|
# By default this is 100kb, or twice the size of the default for media-emoji-local-max-size.
|
|
# This strikes a good balance between decent interoperability with instances that have
|
|
# higher emoji size limits, and not taking up too much space in storage.
|
|
media-emoji-remote-max-size: 100KiB
|
|
|
|
# Int. Number of instances of ffmpeg+ffprobe to add to the media processing pool.
|
|
#
|
|
# Increasing this number will lead to faster concurrent media processing,
|
|
# but at the cost of up to about 250MB of (spiking) memory usage per increment.
|
|
#
|
|
# You'll want to increase this number if you have RAM to spare, and/or if you're
|
|
# hosting an instance for more than 50 or so people who post/view lots of media,
|
|
# but you should leave it at 1 for single-user instances or when running GoToSocial
|
|
# in a constrained (low-memory) environment.
|
|
#
|
|
# If you set this number to 0 or less, then instead of a fixed number of instances,
|
|
# it will scale with GOMAXPROCS x 1, yielding (usually) one ffmpeg instance and one
|
|
# ffprobe instance per CPU core on the host machine.
|
|
#
|
|
# Examples: [1, 2, -1, 8]
|
|
# Default: 1
|
|
media-ffmpeg-pool-size: 1
|
|
|
|
# Int. Number of days to cache media from remote instances before
|
|
# they are removed from the cache. When remote media is removed from
|
|
# the cache, it is deleted from storage but the database entries for
|
|
# the media 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: 7
|
|
media-remote-cache-days: 2
|
|
|
|
# String. 24hr time of day formatted as hh:mm.
|
|
# Examples: ["14:30", "00:00", "04:00"]
|
|
# Default: "00:00" (midnight).
|
|
media-cleanup-from: "22:45"
|
|
|
|
# Duration. Period between media cleanup runs.
|
|
# More than once per 24h is not recommended
|
|
# is likely overkill. Setting this to something
|
|
# very low like once every 10 minutes will probably
|
|
# cause lag and possibly other issues.
|
|
# Examples: ["24h", "72h", "12h"]
|
|
# Default: "24h" (once per day).
|
|
media-cleanup-every: "24h" |