Find cron task for "Delete all repositories' archives (ZIP, TAR.GZ, etc..)" #395

Closed
opened 2022-03-10 18:15:28 +00:00 by greg · 4 comments
Owner

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?)
greg added the
service
gitea
label 2022-03-10 18:15:28 +00:00
Owner
https://discourse.gitea.io/t/how-to-configure-cron-task-for-delete-all-repositories-archives-zip-tar-gz-etc/4848
Owner

As a temporary fix, I added a cron job for root to delete the archive files manually every 15 minutes for now.

As a temporary fix, I added a cron job for root to delete the archive files manually every 15 minutes for now.
raucao referenced this issue from a commit 2022-08-08 10:57:32 +00:00
Member

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?
Owner

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.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#395
No description provided.