Mercurial > kallithea
view docs/upgrade.rst @ 2252:37945c6a7dbd beta
don't use db-repo instance on readme file fetching, use regular scm get_repo that doesn't hide exceptions
author | Marcin Kuzminski <marcin@python-works.com> |
---|---|
date | Wed, 09 May 2012 21:17:51 +0200 |
parents | 8dfb265fc954 |
children | dc2584ba5fbc 008d9c6f7c92 |
line wrap: on
line source
.. _upgrade: ======= Upgrade ======= 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:: easy_install -U rhodecode Or:: pip install --upgrade rhodecode Then make sure you run the following command from the installation directory:: paster make-config RhodeCode production.ini 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 re check the content after the automerge. .. note:: Please always make sure your .ini files are up to date. Often errors are caused by missing params added in new versions. It is also recommended that you rebuild the whoosh index after upgrading since the new whoosh version could introduce some incompatible index changes. Please Read the changelog to see if there were any changes to whoosh. The final step is to upgrade the database. To do this simply run:: 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:: If you're using Celery, make sure you restart all instances of it after upgrade. .. _virtualenv: http://pypi.python.org/pypi/virtualenv .. _python: http://www.python.org/ .. _mercurial: http://mercurial.selenic.com/ .. _celery: http://celeryproject.org/ .. _rabbitmq: http://www.rabbitmq.com/