External configuration for publishing receivers
Publishing receivers are configured using MicroProfile Config. You can supply MicroProfile configurations using:
- 
properties files 
- 
YAML files 
- 
system properties or environment variables (and more) 
To point to your config file, you must pass the magnolia.config.locations as a system property (for example, using Tomcat VM options in the setenv.sh configuration file), pointing to the directory where your config file resides (for example -Dmagnolia.config.locations=/opt/magnolia/mounted-config).
magnolia.publishing.receivers[0].name=magnoliaPublic-0
magnolia.publishing.receivers[0].url=http://dev-magnolia-helm-public-0-svc:8080
magnolia.publishing.receivers[1].name=magnoliaPublic-1
magnolia.publishing.receivers[1].url=http://dev-magnolia-helm-public-1-svc:8080magnolia:
  publishing:
    receivers:
      - name: magnoliaPublic-0
        url: http://dev-magnolia-helm-public-0-svc:8080
      - name: magnoliaPublic-1
        url: http://dev-magnolia-helm-public-1-svc:8080| The default receiver for local development ( Receiver example for local development 
 | 
Previous (Magnolia 6.2) definition in JCR
In Magnolia 6.2, publishing receivers were configured in JCR, under the publishing-core module.
This made it difficult to provision instances across multiple environments and configure receivers during installation or startup through various JCR bootstrapping techniques.
| Node name | Value | 
|---|---|
| 📁 modules | |
| 📁 publishing-core | |
| 📁 config | |
| ⸬ receivers | |
| ⸬ magnoliaPublic8080 | |
| ⬩ url | |
| ⬩ enabled | true | 
- Related topics