Edit online

Configuring Publishing Main Container

The Publishing Main Container manages deliverables, the templates used by deliverables, and the builds associated with a deliverable. You can configure the container by setting some properties to customize and optimize the behavior of the publishing and build processes according to your specific requirements:

publishing.service.deliverable.builds.number
Sets the number of builds to retain for each deliverable. This helps manage disk space while maintaining only the most recent builds. Default value is 3.
publishing.service.allow.automatic.builds
Controls whether or not automatic builds (triggered by remote modifications or scheduled tasks) are allowed. Default value is true.
publising.service.check.remote.period
The interval (in seconds) at which the system checks for remote changes. Default value is 60 seconds.
publishing.service.start.build.remote.changes.period
The delay (in minutes) before starting a build when remote changes are detected. If additional remote changes are detected during this period, the build is re-triggered. Default value is 3 minutes.
publishing.service.start.build.remote.changes.max.period
The delay (in minutes) before starting a build when remote changes are detected. If additional remote changes are detected during this period, the build is not re-triggered. Default value is 10 minutes.
publishing.service.build.console.max.lines.numbe
Specifies the maximum number of lines displayed in the console that shows the transformation progress. Default value is 1000 lines.

Increasing the CPU Limit for the Publishing Container

The CPU limit for the Content Fusion publishing container can be controlled by setting a value for cpus in the /fusion/docker-compose.override.yml file.

For example:
  publishing-main:
  deploy:
    resources:
      limits:
        cpus: '1.80'
Important:
The indentation is required in the YML file.
After modifying this configuration, you need to restart by running the following commands in the /fusion directory:
docker-compose stop publishing-main
docker-compose rm -f publishing-main
docker-compose up -d publishing-main