Mastodon: Cleanup data #78
Labels
No labels
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: data.coop/ansible#78
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There is some concern with mastodon and disk usage. We should figure out a solution - either with btrfs or cronjobs - or both.
From my point of view we should implement both and the priority should be:
Separate btrfs filesystem for mastodon with a max size,
Cronjob for cleaning up old media etc. This can be a bit of a rabbithole because Mastodon only has built-in tools for some cleanup tasks.
Getting the btrfs filesystems set up should in my opinion be a high priority because having one application fill up the disk taking all other services down with it is a maintenance nightmare.