##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

replaced all decode('utf-8') instances with .decode('utf-8','replace') for more error prof setup,...
replaced all decode('utf-8') instances with .decode('utf-8','replace') for more error prof setup, this way rhodecode could handle displaying non utf8 encoded file paths. This is still an invalid path, but this way we could at least show those paths without errors
marcink - - Load All Authors

File last commit:

r1095:3cdacd15 default
r1100:e7d7f052 beta
Show More
upgrade.rst
50 lines | 1.6 KiB | text/x-rst | RstLexer
/ docs / upgrade.rst
History | Annotation | Raw |Copy content |Copy permalink

Upgrade

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 recheck the content after the automerge.

Note

The next steps only apply to upgrading from non bugfix releases eg. from any minor or major releases. Bugfix releases (eg. 1.1.2->1.1.3) will not have any database schema changes or whoosh library updates.

It is also recommended that you rebuild the whoosh index after upgrading since the new whoosh version could introduce some incompatible index changes.

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.