Setup

Update

To update configuratorware it is necessary to have a valid licence installed.

The update is a 2-step process:

• Update the api and database

• Update or rebuild the frontendgui and admingui

Api and Database

For each update, it is recommended to first backup the database before upgrading. To update the api and the database run via shell from the project directory: composer update-configuratorware

Make sure to read the upgrade notes for the version you’re about to install. Deprecations, breaking changes, updated dependencies and other version specific changes are documented there:

• Version 1.15

• Version 1.16

• Version 1.17

• Version 1.18

• Version 1.19

• Version 1.20

• Version 1.21

• Version 1.22

• Version 1.24

• Version 1.25

• Version 1.27

• Version 1.28

• Version 1.29

• Version 1.31

• Version 1.32

• Version 1.33

• Version 1.35

• Version 1.38

• Version 1.42

• Version 1.45

The latest upgrade notes can also be found in the vendor folder in your configuratorware based project: vendor/configuratorware/configurator-api/UPGRADE-<VersionNumber>.md

frontendgui and admingui

If there is no customizing in frontend projects it’s possible to use prebundled frontends by running: bin/console configuratorware:download-frontend-apps [argument]

This command downloads a ready to use version of the configuratorware frontendgui and admingui and can be run with the following different arguments:

• frontendgui to update only the frontendgui

• admingui to update only the admingui

• frontendgui+admingui to update both

For customized frontends it is necessary to setup a build process to create bundled versions.