Free Up Storage (Codey)¶

The storage alerts of a Codey instance link to this page. All data of a Codey instance is on one storage volume: Git repositories, Git LFS objects, packages, Actions artifacts and logs, the code search index, and the database. You do not have direct access to the volume. Free up space in the Codey web interface.

Repositories¶

Delete repositories you do not need, for example archived copies of old projects. Open the repository, then Settings. In the Danger zone, click Delete this repository. You need to be an owner of the repository.

The space is free at once.

Packages¶

Delete old versions in the package registry, including container images:

1. Open Packages of the user or organization, and click the package.
2. Select the version you want to delete, then click Settings.
3. Click Delete package. This deletes the selected version.

Codey removes the files in a cleanup job that runs every night. The space is free after this job has run.

To remove old versions automatically, add a cleanup rule. Open the Settings of the user or organization, then Packages, then Add cleanup rule. A rule can for example keep the most recent versions of each package, and remove versions older than a number of days. Use Cleanup rule preview to see which versions the rule removes. The rule runs in the same nightly job.

Actions artifacts and runs¶

Delete old Actions artifacts or whole workflow runs:

• Artifacts: open the workflow run, and delete the artifact in the Artifacts list. You need write access to Actions in the repository. The run must be finished.
• Workflow runs: open the workflow run, and click Delete run. This deletes the run with its logs and artifacts. You need to be an administrator of the repository. The run must be finished.

Codey removes the artifact files in a cleanup job that runs every night. The space is free after this job has run.

Codey keeps workflow logs for 365 days. For repositories with many workflow runs, the logs can use a lot of space. Delete run also removes the logs of a run.

By default, Codey keeps artifacts for 90 days. To keep them for a shorter time, set retention-days in the step that uploads the artifact:

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Git LFS¶

Large files tracked with Git LFS are stored on the same volume. To delete LFS files you do not need anymore:

1. Open the repository, then Settings, then LFS.
2. The list shows the LFS files stored in this repository. Click Find commits to check if a commit still uses a file.
3. Delete the files you do not need.

The space is free at once. If a fork of the repository uses the same LFS file, Codey keeps the file until the fork no longer uses it.

Code search index¶

Codey builds a search index for the code in the repositories, and one for the issues. The indexes are on the same volume. According to the Forgejo documentation, the code index can use about 6 times more space than the repositories. When you add or import a lot of code, the index grows too. Codey also indexes mirrors, so a mirror of a large project needs space for the mirror and for its index.

You cannot change the index yourself. If you think the index uses too much space, contact support.

Temporary archives¶

Codey deletes the temporary archives for repository downloads by itself after 2 hours. See Codey.