Cutting down Forgejo's storage usage #456

fnetX commented 2026年04月12日 16:45:10 +02:00

Hey! This is mostly a discussion aimed at the infrastructure team. As you know, thanks to the AI usage, world has become a worse place and storage prices are going at insane rates. Disks we bought a few years for € 700 are now at € 2600.

While Codeberg has money to invest into storage for the benefit of free/libre software projects, I think that Forgejo is using much more storage than it actually needs. I propose to cut down the storage usage, save money and do our tiny part in making the world a little better (saving e-waste and the SSD market, even if barely noticeable).

Cleaning potential.

• https://codeberg.org/forgejo-experimental is storing experimental releases and packages.
  • Usage: ~ 100 GB
  • Suggestion: Delete as much as possible
• https://codeberg.org/forgejo is also storing release packages and attachments
  • Usage: ~ 80 GB
  • Suggestions:
    • Delete all -rc versions
    • Delete release attachments and packages for long EOL versions (e.g. everything < 7.0, keep v7 and newer for now)
    • for EOL releases (< v11), only keep the compressed binaries (also see #248)
    • do not publish uncompressed binaries going forward

If the main concern is the work in doing the cleanup, I'm sure I can help with that.

Hey! This is mostly a discussion aimed at the infrastructure team. As you know, thanks to the AI usage, world has become a worse place and storage prices are going at insane rates. Disks we bought a few years for € 700 are now at € 2600. While Codeberg has money to invest into storage for the benefit of free/libre software projects, I think that Forgejo is using much more storage than it actually *needs*. I propose to cut down the storage usage, save money and do our tiny part in making the world a little better (saving e-waste and the SSD market, even if barely noticeable). Cleaning potential. * https://codeberg.org/forgejo-experimental is storing experimental releases and packages. * Usage: ~ 100 GB * Suggestion: Delete as much as possible * https://codeberg.org/forgejo is also storing release packages and attachments * Usage: ~ 80 GB * Suggestions: * Delete all -rc versions * Delete release attachments and packages for long EOL versions (e.g. everything < 7.0, keep v7 and newer for now) * for EOL releases (< v11), only keep the compressed binaries (also see https://codeberg.org/forgejo/discussions/issues/248) * do not publish uncompressed binaries going forward If the main concern is the work in doing the cleanup, I'm sure I can help with that.

fnetX commented 2026年04月14日 23:14:57 +02:00

As a first step, I will enable a cleanup rule for packages in forgejo-experimental that keep the maximum values (that is: 180 days and 100 versions). I would have chosen 1 year, but it is not possible apparently for whatever weird reason. At the current speed, 100 versions is about 1 year, though.

As a first step, I will enable a cleanup rule for packages in forgejo-experimental that keep the maximum values (that is: 180 days and 100 versions). I would have chosen 1 year, but it is not possible apparently for whatever weird reason. At the current speed, 100 versions is about 1 year, though.

viceice commented 2026年04月29日 15:23:15 +02:00

will release attachments automatically cleaned when the release is deleted? if not, then we should implement it because the daily snapshot's will contantly delete and recreate the dev releases every day

will release attachments automatically cleaned when the release is deleted? if not, then we should implement it because the daily snapshot's will contantly delete and recreate the dev releases every day