kallithea Changeset - 2d4e1f5e854e

Changeset - 2d4e1f5e854e

Parent rev.

Child rev.

[Not reviewed]

beta

0 3 0

Marcin Kuzminski - 13 years ago 2013-02-08 19:24:07
marcin@python-works.com

docs updates

3 files changed with 20 insertions and 4 deletions:

docs/setup.rst

docs/upgrade.rst

docs/usage/general.rst

0 comments (0 inline, 0 general)

docs/setup.rst

➞

Show inline comments

@@ @@ -686,14 +686,14 @@ Here is a sample excerpt from an Apache @@
 .. note::
    when running apache as root please add: `user=www-data group=www-data`
    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::
     import os
     os.environ["HGENCODING"] = "UTF-8"

docs/upgrade.rst

➞

Show inline comments

@@ @@ -72,12 +72,20 @@ The final step is to upgrade the databas @@
  paster upgrade-db production.ini
 This will upgrade the schema and update some of the defaults in the database,
 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::
  echo > rhodecode.log
 Once that is complete, you may now start your upgraded Rhodecode Instance::

docs/usage/general.rst

➞

Show inline comments

@@ @@ -10,13 +10,21 @@ Repository deleting @@
 Currently when admin/owner deletes a repository, RhodeCode does not physically
 delete a repository from filesystem, it renames it in a special way so it's
 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__<date>`
 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
 ----------------------------------
 In file view when this checkbox is checked the << and >> arrows will jump
 to changesets within the same branch currently viewing. So for example
@@ @@ -28,13 +36,13 @@ Compare view from changelog @@
 ---------------------------
 Checkboxes in compare view allow users to view combined compare view. You can
 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 <from-rev> -> <to-rev>` 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
 Non changeable repository urls

0 comments (0 inline, 0 general)