# HG changeset patch # User Thomas De Schampheleire # Date 1546033595 -3600 # Node ID b3644eeee44577e423cff2c3c2136c5f3ea3c05c # Parent a2abde4062eceb0a8c2a09f16b50d39c6292fa67 docs: upgrade: recreating git hooks can only be done after starting Kallithea The upgrade instructions lets the user click on UI links while Kallithea is not yet started. Move those instructions down to fix the flow. diff -r a2abde4062ec -r b3644eeee445 docs/upgrade.rst --- a/docs/upgrade.rst Fri Dec 28 22:43:49 2018 +0100 +++ b/docs/upgrade.rst Fri Dec 28 22:46:35 2018 +0100 @@ -184,8 +184,29 @@ kallithea-cli front-end-build -8. Update Git repository hooks ------------------------------- +8. 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. + + +9. 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. + + +10. Update Git repository hooks +------------------------------- It is possible that an upgrade involves changes to the Git hooks installed by Kallithea. As these hooks are created inside the repositories on the server @@ -202,25 +223,4 @@ not necessary if you only have Mercurial repositories. -9. 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. - - -10. 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