Migration of configs.json from version 2.x to version 3.0.0🔗
-
Clone the current master portal Git repository (if not yet available).
-
Check out the current Masterportal 3.0.0 development branch via Git.
- Help for use is displayed if the help parameter is specified.
- Certain packages with specific versions are mandatory for the migration. These include Node.js and npm with the version numbers defined in the package.json. In Masterportal version 3.13.0, it states:: To check whether the packages are already installed and which versions are being used, the following commands can be executed: If these versions are not correct, the correct versions can be installed using the following commands:
-
MigrateConfig script without parameters: The information in the console guides you through the file conversion. You will be asked for the paths of the portal to be migrated.
-
First, the portal folder of the portal to be migrated must be specified (here
testportal_v2) with path.The source file config.json must be located in the folder. -
You will then be asked to enter the destination folder (here:
testportal_v3). -
Call MigrateConfig with parameters.
-
Migration of one portal:
- Migration of several portals: a folder containing several portals is specified. ATTENTION: the config.json files of the portals will be overwritten!