Use packages

This page explains how to use packages, including checking for them, uploading, downloading, and importing them.

Check packages

You can check whether a particular product launch or quarterly results package is created. The list of packages is sorted by creation date by default. Once you’ve found the package you’re looking for, you can look inside to check if all the content is included within the package.

Package Manager - Browse view

Download packages

You can download a package to create a backup or transfer it to another environment. A package’s contents must be built before you can download it.

  1. Open the Package Manager app.

  2. Select a package.

  3. Click the Download icon in the Actions column of the browser view or use the three-dot of the edit package view.

    Package Manager - Package contents
  4. The package is downloaded, and you can upload it on another instance.

Upload packages

Packages are created as .zip files. To upload a package, its contents must be built and the package name must be unique.

  1. Open the Package Manager app.

  2. Click Upload.

  3. Select the package .zip file you want to upload and click Open.

    Package Manager - Upload dialog
  4. The package is imported, and you can view its contents in the Package Manager.

    Package Manager - Package contents

Install packages

To launch content at a specific time, you can install it on a public instance. Once the process is started, you can’t stop it. Content is applied to the instance where you created or uploaded the package.

  1. Open the Package Manager app.

  2. Select a package.

  3. From the three-dot menu, click Install.

  4. Choose a content merge rule:

    • Replace : Content from the package replaces any content found in the same path on the current instance. Use this option if you want to replace any content on the current instance with the content present in the package. This means that existing content is overridden or deleted as necessary.

    • Merge: This option installs content from the package only to paths that don’t already exist on the current instance. It’s ideal for incorporating new package content while safeguarding existing content on the instance.

    • Update: Existing content on the current instance is updated with package content, and new package content is added. Any existing content on the server not included in the package remains untouched.

  5. Confirm by pressing Install.

    • Live: If content is installed successfully without errors, the package’s status changes to Live.

      Package Manager is for installing bulk content on instances immediately, which is then live if it happens to be a public instance, and moving bulk content around.

      Synchronicity between the author and public instances is only guaranteed in DX Core publishing. Package Manager skips the publishing workflow completely and unzips content on an instance instead.

      If you need to remove live content, delete it from the respective workspace. For example, to delete content installed in the website workspace, use the Pages app or JCR app.

    • Content is live. Errors occurred during the process: In the event of errors, you can view the log.

      If errors occur, content may be partially installed on the instance.
    • Install failed: Your package content isn’t live on the instance.

Feedback

DX Core

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the Package Manager module docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules