``RhodeCode`` (formerly hg-app) is a Pylons framework based Mercurial repository 

browser/management tool with a built in push/pull server and full text search.

It works on http/https and has a built in permission/authentication system with 

the ability to authenticate via LDAP.

RhodeCode is similar in some respects to github or bitbucket, 

however RhodeCode can be run as standalone hosted application on your own server.  It is open source 

and donation ware and focuses more on providing a customized, self administered 

interface for Mercurial(and soon GIT) repositories. RhodeCode is powered by a vcs_ 

library that Lukasz Balcerzak and I created to handle multiple different version 

The default access is anonymous but you can login to an administrative account

using the following credentials:

The latest source for RhodeCode can be obtained from my own RhodeCode instance

Please visit http://packages.python.org/RhodeCode/installation.html

RhodeCode Features

------------------

- Has it's own middleware to handle mercurial_ protocol requests. 

  Each request can be logged and authenticated.

- Runs on threads unlike hgweb. You can make multiple pulls/pushes simultaneous. Supports http/https 

- Mako templates let's you customize the look and feel of the application.

- Beautiful diffs, annotations and source code browsing all colored by pygments.

- Server side forks. It is possible to fork a project and modify it freely without

- Full text search powered by Whoosh on the source files, and file names.

  performance and always up to date data.

- Project grouping

- SSH based authentication with server side key management

- Code review (probably based on hg-review)

- Full git_ support, with push/pull server (currently in beta tests)

- Redmine integration

- Public accessible activity feeds

- Commit based built in wiki system

- Clone points and cloning from remote repositories into RhodeCode

- More statistics and graph (global annotation + some more statistics)

- Other advancements as development continues (or you can of course make additions and or requests)

``RhodeCode`` is released under the GPL_ license.

Join the `Google group <http://groups.google.com/group/rhodecode>`_

Open an issue at `issue tracker <http://bitbucket.org/marcinkuzminski/rhodecode/issues>`_

Join #rhodecode on FreeNode (irc.freenode.net)

Online documentation for the current version of RhodeCode is available at

http://packages.python.org/RhodeCode/.

You may also build the documentation for yourself - go into ``docs/`` and run::

(You need to have sphinx installed to build the documentation. If you don't

have sphinx installed you can install it via the command: ``easy_install sphinx``)

Contributing to RhodeCode

If you would like to contribute to RhodeCode, please contact me, any help is

greatly appreciated!

Could I request that you make your source contributions by first forking the

RhodeCode repository on bitbucket

https://bitbucket.org/marcinkuzminski/rhodecode and then make your changes to

your forked repository. Finally, when you are finished making a change, please

send me a pull request.

To run RhodeCode in a development version you always need to install the tip

version of RhodeCode and the VCS library.

| Thank you for any contributions!

|  Marcin

Git support in RhodeCode 1.1 was disabled due to current instability issues. However,

if you would like to test git support please feel free to re-enable it. To re-enable GIT support just

uncomment the git line in the file rhodecode/__init__.py

   Please note that the git support provided by RhodeCode is not yet fully

   stable and RhodeCode might crash while using git repositories. (That is why

   it is currently disabled.) Thus be careful about enabling git support, and

   certainly don't use it in a production setting!

``RhodeCode`` is written entirely in Python. In order to gain maximum performance

there are some third-party you must install. When RhodeCode is used 

together with celery you have to install some kind of message broker,

Of course RhodeCode works in sync mode also and then you do not have to install

any third party applications. However, using Celery_ will give you a large speed improvement when using

many big repositories. If you plan to use RhodeCode for say 7 to 10 small repositories, RhodeCode

will perform perfectly well without celery running.

If you make the decision to run RhodeCode with celery make sure you run celeryd using paster

Installing RhodeCode from Cheese Shop

Rhodecode requires python version 2.5 or higher.

The easiest way to install ``rhodecode`` is to run::

If you prefer to install RhodeCode manually simply grab latest release from

http://pypi.python.org/pypi/rhodecode, decompress the archive and run::

- Assuming you have installed virtualenv_ create a new virtual environment using virtualenv:: 

   virtualenv is **very important**. This flag provides the necessary

- Activate the virtualenv_ by running::

.. note:: If you're using UNIX, *do not* use ``sudo`` to run the

- Make a folder for rhodecode somewhere on the filesystem for example::

- Run this command to install rhodecode::

- This will install rhodecode together with pylons and all other required python

  libraries

   work perfectly fine without them.

- A possible alternative is `Redis <http://code.google.com/p/redis/>`_

For installation instructions you can visit: 

http://ask.github.com/celery/getting-started/index.html.

This is a very nice tutorial on how to start using celery_ with rabbitmq_

  account. When choosing a root path you can either use a new empty location, or a

- In the admin panel you can toggle ldap, anonymous, permissions settings. As

command ``make-index``. To use ``make-index`` you must specify the configuration

The RhodeCode statistics system makes heavy demands of the server resources, so

in order to keep a balance between usability and performance, the statistics are

cached inside db and are gathered incrementally, this is how RhodeCode does

this:

- On each first visit to the summary page a set of 250 commits are parsed and

  updates statistics cache.

- This happens on each single visit to the statistics page until all commits are

  fetched. Statistics are kept cached until additional commits are added to the

  repository. In such a case RhodeCode will only fetch the new commits when

  updating it's cache.

- On the first visit to the summary page RhodeCode will create tasks that will

  execute on celery workers. This task will gather all of the stats until all

  commits are parsed, each task will parse 250 commits, and run the next task to

  parse next 250 commits, until all of the commits are parsed.

   At any time you can disable statistics on each repository via the repository

   edit form in the admin panel. To do this just uncheck the statistics checkbox.

Upgrading from Cheese Shop

.. note::

   Firstly, it is recommended that you **always** perform a database backup before doing an upgrade.

The easiest way to upgrade ``rhodecode`` is to run::

Then make sure you run the following command from the installation directory::

This will display any changes made by the new version of RhodeCode to your

current configuration. It will try to perform an automerge. It's always better

to make a backup of your configuration file before hand and recheck the content after the automerge.

   not have any database schema changes or whoosh library updates.

It is also recommended that you rebuild the whoosh index after upgrading since the new whoosh 

version could introduce some incompatible index changes.

The final step is to upgrade the database. To do this simply run::

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