CoreMedia Content Cloud v11 Upgrade Guide / Version 2110
Table Of ContentsFirst of all, in order to upgrade to CoreMedia Content Cloud v11, you should start from the latest CoreMedia Content Cloud v10 version.
The list below gives a detailed overview of the software you must have installed prior to the upgrade.
Git >= 2.25.0
The guide uses the Git command restore which is only available since Git version 2.25.0.
NodeJS 16.x
In order to compile the Studio Client workspace and all frontend related components, you need to install NodeJS in the latest version 16.x.
pnpm 6.x
In order to compile the Studio Client workspace and all frontend related components, you need to install pnpm as the packet manager. Simply call
npm install -g pnpm@6on the commandline.Configuring Access to CoreMedia npm Repository
In CoreMedia Content Cloud v11 CoreMedia provides an npm registry to provide CoreMedia npm packages. To access this registry, you need a GitHub user token and need to set the credentials. The GitHub user needs to be a member of the coremedia-contributions organisation in GitHub. If in doubt, contact CoreMedia support to validate your permissions.
Creating a GitHub Token
Create a GitHub token as described in https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token. with the following parameters:
read:packages
read:org
read:user
Configuring your npm Repositories
Configure the npm repositories with the following pnpm calls:
pnpm config set @coremedia:registry https://npm.coremedia.io pnpm config set @jangaroo:registry https://npm.coremedia.io
pnpm login --registry=https://npm.coremedia.io
You will be asked for user and password. Enter your GitHub username (all lowercase) and the created GitHub token as the password.
