Upgrading to GROWI v6.1.x
GROWI v6.1 adds new features such as chart drawing by Mermaid (opens new window), detachable permissions for viewing only, and a bookmark sidebar. Many other fixes and improvements have been made to ensure stable operation of each feature in response to the fundamental changes in the v6.0 series.
In addition, the supported middleware versions have been changed.
|3.6, 4.0, 4.2, 4.4, 5
|3.6, 4.0, 4.2, 4.4, 5, 6
There are changes to the execution environment and supported middleware, so admin should check the version used in their current environment before upgrading.
Table of Contents
Node.js v14 no longer supported
- Systems using official Docker images (opens new window) are not affected
- Upgrade to v16 or v18
Elasticsearch v6 no longer supported, default version changed to v8
GROWI v6.1.0 removes code for Elasticsearch v6 and adds support for v8. Also, the default version used is now v8.
- Systems using Elasticsearch v6 should upgrade to v7 or v8
- If you want to use Elasticsearch v7, set
7in environment variables.
Build Procedure Change
This section is required if you are building from source code published on GitHub.
It is not required if you are using official docker images.
Turborepo (opens new window) is now required as a build tool instead of Lerna, which was previously used. Since it is not included in package.json, a global installation is required. Please install it with the following command before building.
yarn global add turbo
[Specification Change] Change File Save Location Under
The contents of this item are only required on systems configured to store attachments on the local file system.
It is not required for systems storing on AWS S3, GCP GCS, or MongoDB GridFS.
The location of the
app package has changed, and the location of the files has changed.
Please move existing files after upgrade.
Also see discussion below. https://github.com/weseek/growi/discussions/6086 (opens new window)
[Specification Change] Elimination of
mdcont- Prefix Automatically Added to Anchor Links
Starting with v6.0.0, any anchor link in a page (including links in the auto-generated table of contents) was automatically given the prefix
id of the
Headers section in
Starting with v6.1.0, this specification has been eliminated and the
mdcont- prefix is no longer attached.
However, there is no problem with GROWI-generated links such as the table of contents.
If the link contains a
mdcont- prefix in the document or if the link refers to a document or system outside of GROWI, it will not jump to the anchor when accessing the document.
Please rewrite the relevant links accordingly.
The content of pages saved using the previous notation will not automatically change when the GROWI version is upgraded.
We have provided a script to batch rewrite Markdown documents to the new notation, please check the discussion below. https://github.com/weseek/growi/discussions/7180 (opens new window)
Check before upgrading
- Upgrade to Node.js v16 or higher.
- Upgrade to Elasticsearch v7 or v8.
- If you are building from source code, check the new build instructions.
- On systems with
FILE_UPLOAD=localsetting, check the procedure for moving files after the upgrade.
- Check the change in anchor links.
- Inform GROWI users about the change.
- Decide on a strategy for future rewrites of existing page content.