From 8d10572f2ed880ee0f2a9565db3bc2de3e62726d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Kruli=C5=A1?= Date: Sun, 29 Nov 2020 17:50:27 +0100 Subject: [PATCH] Updated Installation (markdown) --- Installation.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Installation.md b/Installation.md index d3dc8f4..79ce495 100644 --- a/Installation.md +++ b/Installation.md @@ -285,9 +285,11 @@ The important commands are actually allowed this in their configurations) about approaching deadlines. This is the most important command as it is directly related to ReCodEx operations. It is recommended to run this command every night. +* `fs:cleanup:worker` will remove old files that are exchanged between core api and worker backend * `db:cleanup:uploads` will remove old uploaded files * `db:cleanup:localized-texts` will remove old texts of groups and exercises * `db:cleanup:exercise-configs` will remove old exercise configs +* `db:cleanup:db:cleanup:exercise-files` will remove unused files (attachments and test files) of deleted exercises/assignments and pipelines * `db:cleanup:pipeline-configs` will remove old pipeline configs * `users:remove-inactive` will soft-delete and anonymize users who are deemed inactive (i.e., they have not verified their credentials for a period of time @@ -299,7 +301,8 @@ The important commands are The frequency of cleanup commands depend on your system utilization. In intensively used instances, it might be prudent to call cleanups as often as once a week. In case of mostly idle instances, a cleanup per month or even -per year may be sufficient. +per year may be sufficient. Calling `fs:cleanup:worker` command should be +more frequent (once a day is recommended). One option is to create a script (or multiple scripts) and schedule their execution in crontab. Do not forget to run these commands as `recodex` user.