Upgrading

New versions of the CUE Front start pack are released at regular intervals, usually together with new versions of the CUE Content Store and CUE editor. Customers are recommended to follow this upgrade cycle in order to ensure that they are running a recent version of the CUE Front infrastructure.

You should be aware that CUE Front has three groups of components, each of which can be upgraded independently of the other two. These groups are:

The start pack

This is the CUE Front infrastructure:

  • Docker files that define the containers in which the various components run, download and install the Cook, Cleaver and Fridge.

  • The default Waiter code

  • Patternlab, the setup tool and other CUE Front utilities

This component is upgraded by downloading a tarball from the Stibo DX Maven repo and unpacking it. For further information, see Upgrade Procedure.

Cook and Cleaver

Whenever a new version of the CUE Front start pack is released, new versions of the Cook and Cleaver are also released and made available on Stibo DX's Debian repo. An upgraded start pack will not automatically download and install new versions of these components however. The start pack's Docker files are configured to look for a version number in the appropriate publication definition folder, and download the version specified there.

To upgrade the Cook and Cleaver versions used at your installation, therefore, you must edit the cue.yaml file in the root folder of your publication definition. For more information about how to do this, see Upgrading Cook and Cleaver.

Recipe extensions

Upgrading the start pack does not affect your publication definition: your recipe, GraphQL queries, templates and so on are not touched by the upgrade process in any way.

The default recipe extensions made by Stibo DX are published on the NPM server npm.escenic.com. Each extension published on npm.escenic.com is separately maintained and has its own version number. As corrections and improvements are made to an extension, new versions may be published. This process is completely independent of the CUE Front release cycle. You will only ever get a new version of a recipe extension if you explicitly request it, and you can upgrade a recipe extension at any time.

Nevertheless, you may choose to upgrade recipe extensions in combination with a CUE Front upgrade. For more information about how to do this, see Upgrading Recipe Extensions.