Rename develop -> development, contribute -> contributing, administer -> administration (#23662)
backport #23629 To make versioned documentation less surprising, 1.19 should have the same technology.
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
---
|
||||
date: "2022-11-01T00:00:00+00:00"
|
||||
title: "Storage"
|
||||
slug: "packages/storage"
|
||||
slug: "usage/packages/storage"
|
||||
draft: false
|
||||
toc: false
|
||||
menu:
|
||||
@@ -31,7 +31,7 @@ Whenever a package gets deleted only the references to the underlaying blobs are
|
||||
The blobs get not removed at this moment, so they still require space on the filesystem.
|
||||
When a new package gets uploaded the existing blobs may get referenced again.
|
||||
|
||||
These unreferenced blobs get deleted by a [clean up job]({{< relref "doc/advanced/config-cheat-sheet.en-us.md#cron---cleanup-expired-packages-croncleanup_packages" >}}).
|
||||
These unreferenced blobs get deleted by a [clean up job]({{< relref "doc/administration/config-cheat-sheet.en-us.md#cron---cleanup-expired-packages-croncleanup_packages" >}}).
|
||||
The config setting `OLDER_THAN` configures how long unreferenced blobs are kept before they get deleted.
|
||||
|
||||
## Cleanup Rules
|
||||
@@ -71,7 +71,7 @@ The patterns are case-insensitive which matches the behaviour of the package reg
|
||||
|
||||
### How the cleanup rules work
|
||||
|
||||
The cleanup rules are part of the [clean up job]({{< relref "doc/advanced/config-cheat-sheet.en-us.md#cron---cleanup-expired-packages-croncleanup_packages" >}}) and run periodically.
|
||||
The cleanup rules are part of the [clean up job]({{< relref "doc/administration/config-cheat-sheet.en-us.md#cron---cleanup-expired-packages-croncleanup_packages" >}}) and run periodically.
|
||||
|
||||
The cleanup rule:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user