Installing a release in Live

Once a release has been tested and accepted in the UAT (User Acceptance Testing) environment, the release can be installed in the Live environment. When you install a release in the Live environment, that version of the site is made public to your end users.

During the installation of the release in your Live environment, your public website remains available.


To install a release:

  1. In Installed releases click Install an update.

  2. Click Install a release.

  3. Installing is a four-step process:

    1. Select the release you want to install and click Next. Latest versions display first. Select Other releases for a dropdown of earlier versions.

    2. Select the environment to install in and click Next. Environments that have not been set up are not available for selection.

    3. Confirm the consequences of the installation and click Install.
      WARNING: Note that if you are installing the release in the Live environment, you should make a backup of the environment beforehand to safeguard your Live environment in case something goes wrong during the installation process, or if you want to roll back the changes at a later time.

    4. Installation may take a few minutes. As all actions in the Magnolia cockpit are asynchronous, you can click on OK before the installation is complete: the action will run in the background and a notification will appear once it is complete.

The installation action appears in the activity log and a notification banner is displayed. The new release details are displayed in Environments section of the Package overview page.

Test changes on updated environment

To check that the environment is running on the correct release:

  • Click Edit content in Author space of the environment in which you installed the release.

  • Log in to Magnolia and check that the updates included in the release are present. You may want to check changed style (due to updated webresources) or create new content with new features.

Always avoid hotfixing problems in the Resources app because the changes are not propagated back to your GIT repository.