Files
@ ccc66ed2f85b
Branch filter:
Location: kallithea/docs/upgrade.rst
ccc66ed2f85b
3.8 KiB
text/prs.fallenstein.rst
db: enable use of main Kallithea config as Alembic config
Newly generated Kallithea config .ini files will be valid Alembic
config files, eliminating the need for a separate alembic.ini config
redundantly specifying the database connection string.
We reference the Alembic migration environment using kallithea:alembic,
which should work independently of how Kallithea is installed.
We also configure a default 'alembic' log level of WARNING, to reduce
the amount of clutter in the config file, reduce the changes needed
to upgrade existing config files for use with Alembic, and allowing us
to change the default Alembic log level for all users down the road.
(It makes sense to define Alembic logging in code, while all other
loggers are configured in the configuration file, because Alembic
is special: it runs on the command line, not as part of the web app.)
Newly generated Kallithea config .ini files will be valid Alembic
config files, eliminating the need for a separate alembic.ini config
redundantly specifying the database connection string.
We reference the Alembic migration environment using kallithea:alembic,
which should work independently of how Kallithea is installed.
We also configure a default 'alembic' log level of WARNING, to reduce
the amount of clutter in the config file, reduce the changes needed
to upgrade existing config files for use with Alembic, and allowing us
to change the default Alembic log level for all users down the road.
(It makes sense to define Alembic logging in code, while all other
loggers are configured in the configuration file, because Alembic
is special: it runs on the command line, not as part of the web app.)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 | .. _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
|