Configuring Portal Properties

In traditional deployments, portal properties are configured through portal-ext.properties and related files. In CNE, they’re defined in the portalProperties field of your GitOps liferay.yaml. Changes are version-controlled, auditable, and easy to revert.

This applies to every Cloud Provider Ready toolkit. The steps are the same whether you deploy with AWS Ready or GCP Ready.

Before configuring portal properties, ensure you have these things:

• A bootstrapped CNE environment (see Getting Started for AWS or GCP)
• Write access to your GitOps repository
• Access to the Argo CD dashboard

Configuring Base Properties

To configure portal properties for all environments,

1. Open the base liferay.yaml for your project:

   liferay/projects/[projectId]/base/liferay.yaml
   

2. Add a portalProperties block under liferay-default: using the same key=value format as portal.properties:

   liferay-default:
     portalProperties: |
       my.custom.property=value
       company.default.web.id=liferay.com
   

3. Commit and push the change to your GitOps repository. If your repository requires a pull request, merge it to apply the change.

   Tip

   When the pull request merges, Argo CD detects the change and synchronizes the environment automatically.

4. In the Argo CD dashboard, confirm the application status shows Synced. Once synchronized, the Liferay pod restarts with the updated configuration.

CNE writes the portalProperties content to portal-cloud.properties in the central ConfigMap. portal-ext.properties then includes it via include-and-override=portal-cloud.properties, so these settings take effect over the base portal property defaults.

Important

Some platform-managed properties (such as web.server.http.port and schema.module.build.auto.upgrade) are appended after your entries in portal-cloud.properties and take precedence over any matching keys you set via portalProperties. Use portalProperties for your application-specific configuration only.

Per-Environment Overrides

To use different portal properties in a specific environment, add a portalProperties block to the environment-specific liferay.yaml:

liferay/projects/[projectId]/environments/[environmentId]/liferay.yaml

Important

An environment-specific portalProperties block replaces the base configuration entirely for that environment. Include all required properties — both shared and environment-specific — in each environment’s block. If an environment file defines no portalProperties key, the base configuration applies unchanged.

liferay-default:
  portalProperties: |
    my.custom.property=dev-value
    feature.flag.LPS-000000=true

Related Topics

• Portal Properties
• CNE AWS Ready: Helm Values Reference
• CNE GCP Ready: Helm Values Reference