Mercurial > kallithea
changeset 4227:6de8a139ab07 kallithea-2.2.5-rebrand
readme: instructions for working with RhodeCode database
author | Sean Farley <sean.michael.farley@gmail.com> |
---|---|
date | Fri, 27 Jun 2014 18:50:21 -0500 |
parents | 499c513967a1 |
children | 1af6d3b21e84 |
files | README.rst |
diffstat | 1 files changed, 44 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/README.rst Wed Jul 02 19:08:38 2014 -0400 +++ b/README.rst Fri Jun 27 18:50:21 2014 -0500 @@ -149,6 +149,50 @@ have sphinx_ installed you can install it via the command: ``easy_install sphinx``) + +Converting from RhodeCode +------------------------- + +Currently, you have two options for working with an existing RhodeCode database: + - keep the database unconverted (intended for testing and evaluation) + - convert the database in a one-time step + +Maintaining Interoperability +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Interoperability with RhodeCode 2.2.5 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 via:: + + python setup.py install + +then you will find this location at +``$VIRTUAL_ENV/lib/python2.7/site-packages/Kallithea-2.2.5-py2.7.egg/kallithea`` + +One-time Conversion +~~~~~~~~~~~~~~~~~~~ + +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:: + + cd /path/to/kallithea + cp /path/to/rhodecode/rhodecode.db kallithea.db + pip install sqlalchemy-migrate + python kallithea/bin/rebranddb.py sqlite:///kallithea.db + +.. WARNING:: + + If you used the other method for interoperability, overwrite brand.py with + an empty file (or watch out for stray brand.pyc after removing brand.py). + .. _virtualenv: http://pypi.python.org/pypi/virtualenv .. _python: http://www.python.org/ .. _sphinx: http://sphinx.pocoo.org/