Package Manager module

Unbundled: Extension Magnolia 6.4 compatible

Edition

DX Core

License

MLA

Issues

PACKMAN

Maven site

Package manager

Latest

2.0.0-alpha1

This module is in alpha state. This alpha version is intended for testing and evaluation purposes only and must not be used in production environments.

The Package Manager module installs the Package Manager app allowing users to configure packages on author instances and use the packages on both author and public instances.

Package manager is incompatible with assets that include binaries stored outside of JCR. This applies to hybrid assets and DAM version 5, version 6, and later.

Installing with Maven

Maven is the easiest way to install the module. Add the following to your bundle:

<dependency>
  <groupId>info.magnolia.packagemanager</groupId>
  <artifactId>magnolia-package-manager-core</artifactId>
  <version>2.0.0-alpha1</version> (1)
</dependency>

1	Should you need to specify the module version, do it using `<version>`.

<dependency>
  <groupId>info.magnolia.packagemanager</groupId>
  <artifactId>magnolia-package-manager-api</artifactId>
  <version>2.0.0-alpha1</version> (1)
</dependency>

1	Should you need to specify the module version, do it using `<version>`.

<dependency>
  <groupId>info.magnolia.packagemanager</groupId>
  <artifactId>magnolia-package-manager-app</artifactId>
  <version>2.0.0-alpha1</version> (1)
</dependency>

1	Should you need to specify the module version, do it using `<version>`.

<dependency>
  <groupId>info.magnolia.warp</groupId>
  <artifactId>warp-frontend</artifactId>
  <version>1.0.0-beta1-packman</version>
</dependency>

Local and remote deployment

This section outlines the process for installing the Package Manager on Magnolia 6.4. The core step involves adding the Package Manager to your webapp, regardless of your environment (development, local, or remote).

Add Package Manager jars, version 2.0.0-alpha1, to the webapp.
- core
- api
- app

Remote deployment without the frontend

For remote installations of the Package Manager on Magnolia 6.4 where the frontend isn’t included, the steps are the same as for local and remote deployment. However, the key difference is how the frontend is managed separately.

Deploy and configure the frontend independently.
- The specific configuration for the frontend’s URL, magnolia.warp.url, is handled at the frontend deployment level, not within the Magnolia webapp. magnolia.api.url is used to define the URL for the backend API. With that, you can specify the endpoint where the API can be accessed.
  values.yml
  global: ... env: - name: magnolia.warp.url value: "<FRONTEND_SERVER>" (1) - name: magnolia.api.url value: <AUTHOR_SERVER>/.rest/ (2)
  1 Frontend URL value.
  
  2 Backend URL value.

Add a CORS filter because the backend and frontend have different origins.

If you’re using a Nginx/Apache proxy configuration, add the CORS filter on the proxy:

values.yml

ingress:
  enabled: true
  annotations:
    ...
    nginx.ingress.kubernetes.io/cors-allow-headers: "Authorization, Tus-Resumable, Upload-Length, Upload-Metadata, Upload-Offset, Accept, Content-Type, Origin, upload-concat, x-http-method-override, X-PINGOTHER, X-Requested-With" (1)
    nginx.ingress.kubernetes.io/cors-allow-methods: "PUT, GET, POST, HEAD, OPTIONS, DELETE, PATCH" (1)
    nginx.ingress.kubernetes.io/cors-allow-origin: "http://localhost:3000, <AUTHOR_SERVER>" (1)
    nginx.ingress.kubernetes.io/enable-cors: "true" (1)

1	CORS filter creation.

If you’re not using a proxy, import this CORS filter to your site definition: /modules/travel-demo/config/travel/cors.

1	Frontend URL value.
2	Backend URL value.

Package Manager module

Installing with Maven

Local and remote deployment

Remote deployment without the frontend

Location

Main doc sections