Mercurial > kallithea
comparison docs/usage/general.rst @ 3335:2d4e1f5e854e beta
docs updates
| author | Marcin Kuzminski <marcin@python-works.com> |
|---|---|
| date | Fri, 08 Feb 2013 19:24:07 +0100 |
| parents | 8b8edfc25856 |
| children | 549c73bfc206 |
comparison
equal
deleted
inserted
replaced
| 3334:968b28545f93 | 3335:2d4e1f5e854e |
|---|---|
| 11 Currently when admin/owner deletes a repository, RhodeCode does not physically | 11 Currently when admin/owner deletes a repository, RhodeCode does not physically |
| 12 delete a repository from filesystem, it renames it in a special way so it's | 12 delete a repository from filesystem, it renames it in a special way so it's |
| 13 not possible to push,clone or access repository. It's worth a notice that, | 13 not possible to push,clone or access repository. It's worth a notice that, |
| 14 even if someone will be given administrative access to RhodeCode and will | 14 even if someone will be given administrative access to RhodeCode and will |
| 15 delete a repository You can easy restore such action by restoring `rm__<date>` | 15 delete a repository You can easy restore such action by restoring `rm__<date>` |
| 16 from the repository name, and internal repository storage (.hg/.git) | 16 from the repository name, and internal repository storage (.hg/.git). There |
| 17 is also a special command for cleaning such archived repos:: | |
| 18 | |
| 19 paster cleanup-repos --older-than=30d production.ini | |
| 20 | |
| 21 This command will scan for archived repositories that are older than 30d, | |
| 22 display them and ask if you want to delete them (there's a --dont-ask flag also) | |
| 23 If you host big amount of repositories with forks that are constantly deleted | |
| 24 it's recommended that you run such command via crontab. | |
| 17 | 25 |
| 18 Follow current branch in file view | 26 Follow current branch in file view |
| 19 ---------------------------------- | 27 ---------------------------------- |
| 20 | 28 |
| 21 In file view when this checkbox is checked the << and >> arrows will jump | 29 In file view when this checkbox is checked the << and >> arrows will jump |
| 29 | 37 |
| 30 Checkboxes in compare view allow users to view combined compare view. You can | 38 Checkboxes in compare view allow users to view combined compare view. You can |
| 31 only show the range between the first and last checkbox (no cherry pick). | 39 only show the range between the first and last checkbox (no cherry pick). |
| 32 Clicking more than one checkbox will activate a link in top saying | 40 Clicking more than one checkbox will activate a link in top saying |
| 33 `Show selected changes <from-rev> -> <to-rev>` clicking this will bring | 41 `Show selected changes <from-rev> -> <to-rev>` clicking this will bring |
| 34 compare view | 42 compare view. In this view also it's possible to switch to combined compare. |
| 35 | 43 |
| 36 Compare view is also available from the journal on pushes having more than | 44 Compare view is also available from the journal on pushes having more than |
| 37 one changeset | 45 one changeset |
| 38 | 46 |
| 39 | 47 |