# HG changeset patch # User Thomas De Schampheleire # Date 1427916679 -7200 # Node ID 35d560f0f842cab98ed6972573addcc2aeeac01c # Parent f4857279cb29f28d6c9f9acf1d8e6e026c2c8c04 docs/usage: English corrections in 'Repository deleting' diff -r f4857279cb29 -r 35d560f0f842 docs/usage/general.rst --- a/docs/usage/general.rst Thu Apr 02 11:01:50 2015 +0200 +++ b/docs/usage/general.rst Wed Apr 01 21:31:19 2015 +0200 @@ -11,20 +11,22 @@ Currently when an admin or owner deletes a repository, Kallithea does not physically delete said repository from the filesystem, but instead renames it in a special way so that it is not possible to push, clone -or access repository. It is worth noting that even if someone will be -given administrative access to Kallithea and will delete a repository, -you can easy restore such an action by removing ``rm__`` from -the repository name. There is also a special command for cleaning such -archived repos:: +or access the repository. + +There is a special command for cleaning up such archived repos:: paster cleanup-repos --older-than=30d my.ini -This command will scan for archived repositories that are older than -30 days, display them, and ask if you want to delete them (there is -a ``--dont-ask`` flag also) If you host a large amount of repositories with -forks that are constantly deleted it is recommended that you run such a +This command scans for archived repositories that are older than +30 days, displays them, and asks if you want to delete them (unless given +the ``--dont-ask`` flag). If you host a large amount of repositories with +forks that are constantly being deleted, it is recommended that you run this command via crontab. +It is worth noting that even if someone is given administrative access to +Kallithea and deletes a repository, you can easily restore such an action by +renaming the repository directory, removing the ``rm__`` prefix. + Follow current branch in file view ----------------------------------