We've found out that the repository archives for mastodon was taking 89GB (!) of disk space, since it's generating an archive for every tag. There's a task on the admin dashboard to run it, but there's nothing in the docs.
There's no way in the docs to disable generating these archives.
Find out how the task is named, and schedule it in the config file (maybe once a week or even every day?)
We've found out that the repository archives for mastodon was taking 89GB (!) of disk space, since it's generating an archive for every tag. There's a task on the admin dashboard to run it, but there's nothing [in the docs](https://docs.gitea.io/en-us/config-cheat-sheet/#cron-cron).
There's no way in the docs to disable generating these archives.
Find out how the task is named, and schedule it in the config file (maybe once a week or even every day?)
hacky af.
according to that forum thread there's cron.archive_cleanup and cron.delete_repo_archives in app.example.ini, maybe that's a better solution?
hacky af.
according to that forum thread there's `cron.archive_cleanup` and `cron.delete_repo_archives` in `app.example.ini`, maybe that's a better solution?
See #423, which solved this issue by adding the (undocumented) cron job for the latter task.
However, it's still hacky IMO, since Gitea shouldn't create any archives in the first place, when your repo doesn't opt into that.
See #423, which solved this issue by adding the (undocumented) cron job for the latter task.
However, it's still hacky IMO, since Gitea shouldn't create any archives in the first place, when your repo doesn't opt into that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We've found out that the repository archives for mastodon was taking 89GB (!) of disk space, since it's generating an archive for every tag. There's a task on the admin dashboard to run it, but there's nothing in the docs.
There's no way in the docs to disable generating these archives.
Find out how the task is named, and schedule it in the config file (maybe once a week or even every day?)
https://discourse.gitea.io/t/how-to-configure-cron-task-for-delete-all-repositories-archives-zip-tar-gz-etc/4848
As a temporary fix, I added a cron job for root to delete the archive files manually every 15 minutes for now.
hacky af.
according to that forum thread there's
cron.archive_cleanupandcron.delete_repo_archivesinapp.example.ini, maybe that's a better solution?See #423, which solved this issue by adding the (undocumented) cron job for the latter task.
However, it's still hacky IMO, since Gitea shouldn't create any archives in the first place, when your repo doesn't opt into that.