Search results

...ning the property <tt>com.openexchange.context.group</tt> to a context via config cascade. A context may only be part of one group, contexts without group as ...g the property <tt>com.openexchange.context.group</tt> at any level of the config cascade, e.g. during provisioning when creating the context like:

...n the config editor by selecting "Tools" -> "Options..." -> "Advanced" -> "Config Editor..." and set the properties "calendar.debug.log" and "calendar.debug.

com.openexchange.oxcs.provisioning.configdn=ou=config,o=oxcs

=== Sample config files === ...e propose to create a custom include directory "ox.conf.d", put our custom config files therein, and include this directory as latest directory in /etc/mysql

...n the config editor by selecting "Tools" -> "Options..." -> "Advanced" -> "Config Editor..." and set the properties "calendar.debug.log" and "calendar.debug.

Now you have to create a new config file to the main Apache configuration which will rewrite all requests from

All those dynamical values can be fetched via a config object at startup. This object shows the capabilities of the server to the ...]]. The action commands which are valid here can be determined through the config object see Table 24

...enexchange.client.onboarding.plist.signkey.alias''' can be overwritten via config-cascade.

This config is still valid since the old wizard can still be enabled via setting. ...y option is fully [http://oxpedia.org/wiki/index.php?title=ConfigCascade ''config-cascade''] aware and therefore can be controlled on a global, per context s

and change the config parameter

This will install new config files of some packages as <code>.rpmnew</code> files. Check those files to

This will install new config files of some packages as <code>.rpmnew</code> files. Check those files to

.ox-portal-controls, .ox-quick-config { .firefox .ox-portal-controls, .firefox .ox-quick-config {

=== yum repo config on i386 === === yum repo config on x86_64 ===

To use this you'll have to edit/create a local config +marens@openxchange:~$ vim config/local.rb

...igit pin to new Guest emails was completely re-written in 2.10. The prior config-cascade value of com.openexchange.capability.guard-pin is now used to speci

wforce package will be removed during dist-upgrade but config files are left in place The example policies are located in /etc/wforce/example-config.

...e.update.branding'' property, which can be overwritten via [[ConfigCascade|Config Cascade]] therefore. Most properties located in configuration file ''drive.properties'' are now config-cascade aware. Therefore all settings can be set per user, per contextSet o

The config file we use is given below. Since OX App Suite has its own built-in read/wr

Hint: use <tt>grunt show-config:local --output grunt/local.conf.json</tt> to generate <tt>grunt/local.conf.