# HG changeset patch # User Marcin Kuzminski # Date 2013-02-08 18:24:07 # Node ID 2d4e1f5e854e473eb0c19f6bca55b744403b5d8c # Parent 968b28545f9366a2451c9106fcc5bd5351adec16 docs updates diff --git a/docs/setup.rst b/docs/setup.rst --- a/docs/setup.rst +++ b/docs/setup.rst @@ -689,8 +689,8 @@ Here is a sample excerpt from an Apache into above configuration .. note:: - RhodeCode cannot be runned in multiprocess mode in apache, make sure - you don't specify `processes=num` directive in the config + Running RhodeCode in multiprocess mode in apache is not supported, + make sure you don't specify `processes=num` directive in the config Example wsgi dispatch script:: diff --git a/docs/upgrade.rst b/docs/upgrade.rst --- a/docs/upgrade.rst +++ b/docs/upgrade.rst @@ -75,6 +75,14 @@ This will upgrade the schema and update and will always recheck the settings of the application, if there are no new options that need to be set. + +.. note:: + DB schema upgrade library has some limitations and can sometimes fail if you try to + upgrade from older major releases. In such case simply run upgrades sequentially, eg. + upgrading from 1.2.X to 1.5.X should be done like that: 1.2.X. > 1.3.X > 1.4.X > 1.5.X + You can always specify what version of RhodeCode you want to install for example in pip + `pip install RhodeCode==1.3.6` + You may find it helpful to clear out your log file so that new errors are readily apparent:: diff --git a/docs/usage/general.rst b/docs/usage/general.rst --- a/docs/usage/general.rst +++ b/docs/usage/general.rst @@ -13,7 +13,15 @@ delete a repository from filesystem, it not possible to push,clone or access repository. It's worth a notice that, even if someone will be given administrative access to RhodeCode and will delete a repository You can easy restore such action by restoring `rm__` -from the repository name, and internal repository storage (.hg/.git) +from the repository name, and internal repository storage (.hg/.git). There +is also a special command for cleaning such archived repos:: + + paster cleanup-repos --older-than=30d production.ini + +This command will scan for archived repositories that are older than 30d, +display them and ask if you want to delete them (there's a --dont-ask flag also) +If you host big amount of repositories with forks that are constantly deleted +it's recommended that you run such command via crontab. Follow current branch in file view ---------------------------------- @@ -31,7 +39,7 @@ Checkboxes in compare view allow users t only show the range between the first and last checkbox (no cherry pick). Clicking more than one checkbox will activate a link in top saying `Show selected changes -> ` clicking this will bring -compare view +compare view. In this view also it's possible to switch to combined compare. Compare view is also available from the journal on pushes having more than one changeset