Mercurial > kallithea
changeset 7492:a2abde4062ec
docs: upgrade: front-end should be built for all installation methods
... and not exclusively when installing from version control.
| author | Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> |
|---|---|
| date | Fri, 28 Dec 2018 22:43:49 +0100 |
| parents | 634c2fa427e8 |
| children | b3644eeee445 |
| files | docs/upgrade.rst |
| diffstat | 1 files changed, 14 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/upgrade.rst Fri Dec 28 22:39:38 2018 +0100 +++ b/docs/upgrade.rst Fri Dec 28 22:43:49 2018 +0100 @@ -90,7 +90,6 @@ hg update hg parent # make a note of the new revision pip install --upgrade -e . - kallithea-cli front-end-build .. _upgrade_config: @@ -175,7 +174,17 @@ Your config file should now work with Alembic. -7. Update Git repository hooks +7. Prepare the front-end +------------------------ + +Starting with Kallithea 0.4, external front-end dependencies are no longer +shipped but need to be downloaded and/or generated at installation time. Run the +following command:: + + kallithea-cli front-end-build + + +8. Update Git repository hooks ------------------------------ It is possible that an upgrade involves changes to the Git hooks installed by @@ -193,15 +202,15 @@ not necessary if you only have Mercurial repositories. -8. Rebuild the Whoosh full-text index +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. -9. Start the Kallithea web application --------------------------------------- +10. Start the Kallithea web application +--------------------------------------- This step once again depends entirely on the web server software used to serve Kallithea.