Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Liferay properties is powerful instrument that allows us to configure Portal behaviour without coding of hooks-, ext- and theme-plugin. By new requirement we proof at first for possibility to solve this requirement with change of Liferay configuration. The default properties configuration can be found at Liferay source code: <a href="https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/portal.properties" rel="noreferrer">https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/portal.properties</a> or in <a href="https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/portal.properties" rel="noreferrer">https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/portal.properties</a> or in <code>liferay-bundles\tomcat-7\webapps\ROOT\WEB-INF\lib\portal-impl.jar</code></p> <p>To configure or to override configuration properties of Liferay portal we have to create <code>portal-ext.properties</code> at root folder of Liferay (bundled with tomcat).</p> <pre><code>Liferay |-data |-deploy |-license |-logs |-tomcat-7.xxx |-portal-ext.propeties &lt;- override portal properties |-portal-${user}.propeties &lt;- override user specific properties </code></pre> <p>Usual we work in team with version control systems like git or svn, and developers have different configuration like database path etc. Liferay allows to configure user specific configuration in e.g. <code>portal-${user}.properties</code>. Therefor put at first to the <code>portal-ext.properties</code> the inclusion of user properties:</p> <pre><code>include-and-override = ${default.liferay.home}/portal-${user.name}.properties </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload