Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] Lower remote media cache config duration #2007

Merged
merged 1 commit into from Jul 21, 2023

Commits on Jul 20, 2023

  1. [feature] Lower remote media cache config duration

    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.
    daenney committed Jul 20, 2023
    Configuration menu
    Copy the full SHA
    577d713 View commit details
    Browse the repository at this point in the history