mirror of
https://github.com/superseriousbusiness/gotosocial.git
synced 2024-11-01 06:50:00 +00:00
da8282081c
The old default of 30d can lead to a lot of media getting cached and significant disk usage, even on small or single person instances. A lot of deployments decrease this value, to 15 or even less. This is less of an issue when using object storage, but for local storage which is the more popular deployment option running out of disk space is unpleasant. With GoToSocial's aim to fit in small places, this changes the default to a much more conservative 7 days. In all likelihood people aren't scrolling that far back in their timeline so this change shouldn't result in any issue. Existing deployments will only be affected by this change if the admin hasn't already configured this value, or didn't bootstrap from the example configuration.
59 lines
2.1 KiB
Markdown
59 lines
2.1 KiB
Markdown
# Media
|
|
|
|
## Settings
|
|
|
|
```yaml
|
|
########################
|
|
##### MEDIA CONFIG #####
|
|
########################
|
|
|
|
# Config pertaining to media uploads (videos, image, image descriptions, emoji).
|
|
|
|
# Int. Maximum allowed image upload size in bytes.
|
|
# Examples: [2097152, 10485760]
|
|
# Default: 10485760 -- aka 10MB
|
|
media-image-max-size: 10485760
|
|
|
|
# Int. Maximum allowed video upload size in bytes.
|
|
# Examples: [2097152, 10485760]
|
|
# Default: 41943040 -- aka 40MB
|
|
media-video-max-size: 41943040
|
|
|
|
# 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: [500, 1000, 1500]
|
|
# Default: 500
|
|
media-description-max-chars: 500
|
|
|
|
# Int. Number of days to cache media from remote instances before they are removed from the cache.
|
|
# A job will run every day at midnight to clean up any remote media older than the given amount of days.
|
|
#
|
|
# 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: 7
|
|
|
|
# Int. 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.
|
|
# Examples: [51200, 102400]
|
|
# Default: 51200
|
|
media-emoji-local-max-size: 51200
|
|
|
|
# Int. 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.
|
|
# Examples: [51200, 102400]
|
|
# Default: 102400
|
|
media-emoji-remote-max-size: 102400
|
|
```
|