view docs/upgrade.rst @ 4147:1c8f818787b3 rhodecode-2.2.5-gpl

old style: show the full link box on summary page - no overlap or truncation
author Mads Kiilerich <madski@unity3d.com>
date Wed, 02 Jul 2014 19:03:23 -0400
parents 3563bb7b4b82
children 99ad9d0af1a3
line wrap: on
line source

.. _upgrade:

=======
Upgrade
=======

Upgrading from PyPI (aka "Cheeseshop")
---------------------------------------

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

   (These directions will use '{version}' to note that this is the version of
   Rhodecode that these files were used with.  If backing up your RhodeCode
   instance from version 1.3.6 to 1.4.0, the ``production.ini`` file would be
   backed up to ``production.ini.1-3-6``.)


If using a sqlite database, stop the Rhodecode process/daemon/service, and
then make a copy of the database file::

 service rhodecode stop
 cp rhodecode.db rhodecode.db.{version}


Back up your configuration file::

 cp production.ini production.ini.{version}


Ensure that you are using the Python Virtual Environment that you'd originally
installed Rhodecode in::

 pip freeze

will list all packages installed in the current environment.  If Rhodecode
isn't listed, change virtual environments to your venv location::

 source /opt/rhodecode-venv/bin/activate


Once you have verified the environment you can upgrade ``Rhodecode`` with::

 easy_install -U rhodecode

Or::

 pip install --upgrade rhodecode


Then 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 recommended
that you 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::
   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::

 service rhodecode start

Or::

 paster serve /var/www/rhodecode/production.ini

.. 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/