Interoperability with RhodeCode 2.2.X installations is provided so you don’t
have to immediately commit to switching to Kallithea. This option will most
likely go away once the two projects have diverged significantly.
To run Kallithea on a RhodeCode database, run:
echo "BRAND = 'rhodecode'" > kallithea/brand.py
This location will depend on where you installed Kallithea. If you installed
python2 setup.py install
then you will find this location at
Alternatively, if you would like to convert the database for good, you can use
a helper script provided by Kallithea. This script will operate directly on the
database, using the database string you can find in your production.ini (or
development.ini) file. For example, if using SQLite:
cp /path/to/rhodecode/rhodecode.db kallithea.db
pip install sqlalchemy-migrate
python2 kallithea/bin/rebranddb.py sqlite:///kallithea.db
If you started out using the branding interoperability approach mentioned
above, watch out for stray brand.pyc after removing brand.py.
After switching to Kallithea, it will be necessary to update the Git hooks in
your repositories. If not, the Git hooks from RhodeCode will still be called,
which will cause git push to fail every time.
If you do not have any custom Git hooks deployed, perform the following steps
(this may take some time depending on the number and size of repositories you
- Log-in as an administrator.
- Open page Admin > Settings > Remap and Rescan.
- Turn on the option Install Git Hooks.
- Turn on the option Overwrite existing Git hooks.
- Click on the button Rescan Repositories.
If you do have custom hooks, you will need to merge those changes manually. In
order to get sample hooks from Kallithea, the easiest way is to create a new Git
repository, and have a look at the hooks deployed there.