refactor: some small changes before PR
All checks were successful
ci/woodpecker/pr/docs Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/man Pipeline was successful
ci/woodpecker/pr/docker Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
All checks were successful
ci/woodpecker/pr/docs Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/man Pipeline was successful
ci/woodpecker/pr/docker Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
This commit is contained in:
parent
b66d1161ed
commit
ab81eebd87
7 changed files with 31 additions and 34 deletions
|
|
@ -5,15 +5,15 @@ weight: 20
|
|||
# Cleanup
|
||||
|
||||
Vieter stores the logs of every single package build. While this is great for
|
||||
debugging why builds fails, it also causes an active or long-running Vieter
|
||||
debugging why builds fail, it also causes an active or long-running Vieter
|
||||
instance to accumulate thousands of logs.
|
||||
|
||||
To combat this, a log removal daemon can be enabled that periodically removes
|
||||
old build logs. By starting your server with the `max_log_age` variable (see
|
||||
[Configuration](/configuration#vieter-server) for more info), a daemon will
|
||||
get enabled that periodically removes logs older than this setting. By default,
|
||||
this will happen every day at midnight, but this behavior can be changed using
|
||||
the `log_removal_schedule` variable.
|
||||
[Configuration](/configuration#vieter-server)), a daemon will get enabled that
|
||||
periodically removes logs older than this setting. By default, this will happen
|
||||
every day at midnight, but this behavior can be changed using the
|
||||
`log_removal_schedule` variable.
|
||||
|
||||
{{< hint info >}}
|
||||
**Note**
|
||||
|
|
@ -21,4 +21,3 @@ The daemon will always run a removal of logs on startup. Therefore, it's
|
|||
possible the daemon will be *very* active when first enabling this setting.
|
||||
After the initial surge of logs to remove, it'll calm down again.
|
||||
{{< /hint >}}
|
||||
|
||||
|
|
|
|||
Reference in a new issue