Files @ e36bc85e3ecb
Branch filter:

Location: kallithea/docs/upgrade.rst - annotation

e36bc85e3ecb 3.8 KiB text/prs.fallenstein.rst Show Source Show as Raw Download as Raw
Søren Løvborg
db: remove SQLAlchemy Migrate database table

Use Alembic to migrate database away from SQLAlchemy Migrate. This
eliminates the last vestiges of SQLAlchemy Migrate. Since we drop
the Migrate table (and its contents), it is not possible to revert
this database change; however, downgrading to this Alembic schema
revision (9358dc3d6828) will in practice be enough to ensure
compatibility with all previous Kallithea versions.

(As always, the Alembic migration script is committed in the same
revision as the database schema changes.)
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
0b6d2ca7175f
0b6d2ca7175f
0b6d2ca7175f
0b6d2ca7175f
0b6d2ca7175f
0b6d2ca7175f
0b6d2ca7175f
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
c7ef77ab2f95
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
8075ec3d0233
.. _upgrade:

===================
Upgrading Kallithea
===================

This describes the process for upgrading Kallithea, independently of the
Kallithea installation method.

.. note::
    If you are upgrading from a RhodeCode installation, you must first
    install Kallithea 0.3.2 and follow the instructions in the 0.3.2
    README to perform a one-time conversion of the database from
    RhodeCode to Kallithea, before upgrading to the latest version
    of Kallithea.


1. Stop the Kallithea web application
-------------------------------------

This step depends entirely on the web server software used to serve
Kallithea, but in any case, Kallithea should not be running during
the upgrade.

.. note::
    If you're using Celery, make sure you stop all instances during the
    upgrade.


2. Create a backup of both database and configuration
-----------------------------------------------------

You are of course strongly recommended to make backups regularly, but it
is *especially* important to make a full database and configuration
backup before performing a Kallithea upgrade.

Back up your configuration
^^^^^^^^^^^^^^^^^^^^^^^^^^

Make a copy of your Kallithea configuration (``.ini``) file.

If you are using :ref:`rcextensions <customization>`, you should also
make a copy of the entire ``rcextensions`` directory.

Back up your database
^^^^^^^^^^^^^^^^^^^^^

If using SQLite, simply make a copy of the Kallithea database (``.db``)
file.

If using PostgreSQL, please consult the documentation for the ``pg_dump``
utility.

If using MySQL, please consult the documentation for the ``mysqldump``
utility.

Look for ``sqlalchemy.db1.url`` in your configuration file to determine
database type, settings, location, etc.


3. Activate the Kallithea virtual environment (if any)
------------------------------------------------------

Verify that you are using the Python environment that you originally
installed Kallithea in by running::

    pip freeze

This will list all packages installed in the current environment. If
Kallithea isn't listed, activate the correct virtual environment.
See the appropriate installation page for details.


4. Install new version of Kallithea
-----------------------------------

Please refer to the instructions for the installation method you
originally used to install Kallithea.

If you originally installed using pip, it is as simple as::

    pip install --upgrade kallithea

If you originally installed from version control, it is as simple as::

    cd my-kallithea-clone
    hg pull -u
    pip install -e .


5. Upgrade your configuration
-----------------------------

Run the following command to upgrade your configuration (``.ini``) file::

    paster make-config Kallithea my.ini

This will display any changes made by the new version of Kallithea to your
current configuration, and attempt an automatic merge. It is recommended
that you check the contents after the merge.

.. note::
    Please always make sure your ``.ini`` files are up to date. Errors
    can often be caused by missing parameters added in new versions.


6. Upgrade your database
------------------------

Not required.


7. Rebuild the Whoosh full-text index
-------------------------------------

It is recommended that you rebuild the Whoosh index after upgrading since
new Whoosh versions can introduce incompatible index changes.


8. Start the Kallithea web application
--------------------------------------

This step once again depends entirely on the web server software used to
serve Kallithea.

Before starting the new version of Kallithea, you may find it helpful to
clear out your log file so that new errors are readily apparent.

.. note::
    If you're using Celery, make sure you restart all instances of it after
    upgrade.


.. _virtualenv: http://pypi.python.org/pypi/virtualenv