Operations
Cache, storage and retention
Where files live, how long things are kept, and how to clean up.
| Setting (Cache tab) | Default | Meaning |
|---|---|---|
| Keep tarballs on disk | on | Off serves files once without keeping them. |
| Seconds before metadata is refetched | 300 | How fresh npm and PyPI metadata is. |
| Seconds we will serve stale metadata if upstream is down | 604800 | 7 days of outage protection. |
| Days of traffic log to keep | 30 | The audit trail is kept 4 times as long. |
| Days to remember who consumed what | 365 | 0 keeps it forever. |
The Storage tab keeps files on local disk, S3 (or anything that speaks S3), or Azure Blob. Save and test the bucket changes nothing if the test fails. Local copies to keep, in MB keeps a fast local cache in front of the bucket.
The Packages page lists npm packages by default. Pick PyPI or images under Type to search those too. For an image it shows how many tags are held completely, how many times it was pulled, and a link to its files on Artifacts.
Cleaning up (Packages page)
- Purge cache or Forget ticked packages. They download again when next asked.
- Check for drift reports files missing from disk and changes nothing.
- Recache missing restores missing files. Purge blocked removes files the rules now block.
- Empty the entire cache is admin only.