kallithea Changeset - a2abde4062ec

Changeset - a2abde4062ec

Parent rev.

Child rev.

[Not reviewed]

default

0 1 0

Thomas De Schampheleire - 7 years ago 2018-12-28 22:43:49
thomas.de_schampheleire@nokia.com

docs: upgrade: front-end should be built for all installation methods

... and not exclusively when installing from version control.

1 file changed with 14 insertions and 5 deletions:

docs/upgrade.rst

0 comments (0 inline, 0 general)

docs/upgrade.rst

➞

Show inline comments

@@ @@ -90,7 +90,6 @@ private changes (in which case you shoul @@
     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 @@ need to append the following lines to it @@
 Your config file should now work with Alembic.
 . Update Git repository hooks
 . 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
 . Update Git repository hooks
 ------------------------------
 It is possible that an upgrade involves changes to the Git hooks installed by
@@ @@ -193,15 +202,15 @@ To update the hooks of your Git reposito @@
     not necessary if you only have Mercurial repositories.
-. Rebuild the Whoosh full-text index
+. 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.
 . Start the Kallithea web application
 --------------------------------------
 . Start the Kallithea web application
 ---------------------------------------
 This step once again depends entirely on the web server software used to
 serve Kallithea.

0 comments (0 inline, 0 general)