External DAM module
Digital asset management Unbundled: Extension
|
Magnolia External DAM module 2.0.0 is in beta with Magnolia 6.3. We are updating docs based on development and feedback. Consider the beta docs currently in a state of progress and not final. |
License |
|
Issues |
|
Maven site |
|
Latest |
2.0.0 |
Module structure
| artifactID | Description |
|---|---|
|
Parent reactor. |
|
Provides the foundation for integrating with S3 and Bynder and a sample component for using assets in the Pages app. |
|
Provides a default implementation to connect to Bynder. |
|
Provides a default implementation to connect to Amazon S3. |
Installing with Maven
Maven is the easiest way to install the module. Add the following to your bundle:
<dependency>
<groupId>info.magnolia.external.dam</groupId>
<artifactId>magnolia-external-dam</artifactId>
<version>2.0.0</version> (1)
</dependency>| 1 | Should you need to specify the module version, do it using <version>. |
<dependency>
<groupId>info.magnolia.external.dam</groupId>
<artifactId>magnolia-external-dam-bynder</artifactId>
<version>2.0.0</version> (1)
</dependency>| 1 | Should you need to specify the module version, do it using <version>. |
<dependency>
<groupId>info.magnolia.external.dam</groupId>
<artifactId>magnolia-external-dam-s3</artifactId>
<version>2.0.0</version> (1)
</dependency>| 1 | Should you need to specify the module version, do it using <version>. |
Connection configuration
See the following pages for detailed information about connecting to and configuring your external DAM solution:
Essentially, you:
-
Provide connection credentials for your external solution.
-
Enable the subapp to display in the Magnolia Assets app.
-
Configure the cache if necessary.
You can create or edit the configuration in the JCR or the File System (YAML) under <module-name>/external-dams/<definition-name>.
Before you configure the connection, make sure you know:
-
Which solution you want to connect to. Default implementations are provided for:
-
AWS S3
-
Bynder
-
-
Connection credentials for your solution.
| If you want to connect to another third-party tool, extend the Magnolia DAM API and create your own asset provider |
| There are several additional DAM connector modules. For more details, see Digital asset management modules. |
Release history
External DAM module changelog
|
Magnolia External DAM module 2.0.0 is in beta with Magnolia 6.3. We are updating docs based on development and feedback. Consider the beta docs currently in a state of progress and not final. |
The changelog gives you an overview of the changes made to the External DAM module at each release.
This changelog covers the 2.0.x branch of the External DAM module. For the 1.1.x changelog, see here.
|
2.0.0-beta2
Not yet publicly released
| Ticket | Type | Description |
|---|---|---|
S3: Bring back the bucket icon. |
||
Build on JDK 11. |
||
S3: Remove bucket name from app folder links and item description. |
||
S3: |
||
S3:Option to store width and height in the asset metadata. |
||
S3: Add filtering on the Name column. |
DAM integration framework compatibility
| Module version | Magnolia CMS version |
|---|---|
1.1.0+ |
6.2.13+ |
1.0.3+ |
6.2.4 |
1.0.2 |
6.2.4 |
1.0.1 |
6.2.1 |
1.0 |
6.2 |
|
A note about connector compatibilty The third-party versions listed below are the versions Magnolia has developed and tested against. If you don’t see a particular version listed, it simply means that we do not routinely test on it. If you are using another version of the third-party tool and run into compatibility issues, please contact our Support. |
| Module version | Bynder SDK |
|---|---|
1.0.4 |
Tested against 2.2.1 |
1.0 |
Tested against 2.2.0 |
| Module version | AWS Java SDK |
|---|---|
1.0.1 |
2.13.25 |
1.0 |
Tested against 2.9.7 |
