Search results
Create the page "Config" on this wiki! See also the search results found.
- grunt.config('connect', { var config = grunt.config().local.appserver;13 KB (1,923 words) - 12:08, 14 March 2014
- and change the config parameter4 KB (521 words) - 10:44, 14 February 2017
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...e users. See http://oxpedia.org/wiki/index.php?title=ConfigCascade and /ox-config-path/contextSets/index.yml for more information on this. Possible modules:268 KB (37,155 words) - 12:16, 21 October 2015
- ...and pass our session onto your implementation. This is a replacement for "Config Jump" of OX6. Not to be confused with [[AppSuite:Creating_a_settings_sectio You can declare pages to embed via [[ConfigCascade|Config Cascade]] settings. There are several ways to do so, this example uses the4 KB (623 words) - 10:01, 22 May 2017
- ...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 o22 KB (3,224 words) - 13:19, 18 December 2023
- ...rs''. This will install UI as well as backend components (in the form of a config file).5 KB (774 words) - 12:53, 29 November 2016
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infos351 KB (48,276 words) - 15:48, 31 January 2017
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...e users. See http://oxpedia.org/wiki/index.php?title=ConfigCascade and /ox-config-path/contextSets/index.yml for more information on this. Possible modules:280 KB (38,131 words) - 21:26, 5 March 2014
- == OX Config File Review == Review each config files one by one.1 KB (204 words) - 11:03, 29 December 2015
- Hint: use <tt>grunt show-config:local --output grunt/local.conf.json</tt> to generate <tt>grunt/local.conf.4 KB (710 words) - 08:33, 3 June 2014
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infos347 KB (47,794 words) - 13:34, 31 January 2017
- ...change-Frontend/shared-grunt-config/releases releases page of shared-grunt-config] and add the name of the latest tag to your apps <tt>package.json</tt>. It "shared-grunt-config": "Open-Xchange-Frontend/shared-grunt-config#v0.5.0"4 KB (616 words) - 09:21, 22 May 2017
- ...th Grunt]]. In a nutshell: git clone repository, setup (npm install, local config etc.), and build with grunt. ...''' is not configured. Grunt will offer you a command to get a basic grunt config (see next step).3 KB (474 words) - 10:18, 22 May 2017
- ...en-xchange/sbin/changeuser -c 1 -A oxadmin -P admin_password -u testuser --config/com.openexchange.capability.guard-mail=true</source> ...en-xchange/sbin/changeuser -c 1 -A oxadmin -P admin_password -u testuser --config/com.openexchange.capability.guard-drive=true</source>44 KB (6,324 words) - 12:12, 9 October 2023
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infos366 KB (50,420 words) - 07:11, 29 September 2017
- 'key' => 'config' SOAPMapEntry config = new SOAPMapEntry();62 KB (7,178 words) - 12:18, 2 March 2023
- Config file generated at "/home/jb/code/appsuite/ox_pgp_mail/karma.conf.js". requirejs.config({7 KB (766 words) - 09:20, 22 May 2017
- ...on usage of the open source tool Liquibase. Currently this applies to the config database, as well as so-called global databases for storing cross-context d6 KB (785 words) - 10:03, 14 March 2019
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infos293 KB (39,973 words) - 13:36, 1 July 2015
- To use this you'll have to edit/create a local config +marens@openxchange:~$ vim config/local.rb26 KB (3,476 words) - 10:17, 22 February 2018
- you may want to check that the following arguments are present in the config file:2 KB (254 words) - 19:22, 5 June 2015
- ...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:7 KB (1,110 words) - 07:54, 5 November 2021
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infos321 KB (44,146 words) - 07:59, 2 December 2015
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infos301 KB (41,323 words) - 19:56, 2 December 2015
- | <nowiki>URL to the config interface. %c is replaced with context login information. %u is replaced wi ...capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infos333 KB (45,761 words) - 15:55, 17 May 2016
- 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 s23 KB (3,482 words) - 10:54, 5 May 2021
- $ update-alternatives --config java $ update-alternatives --config java38 KB (5,758 words) - 18:25, 13 April 2017
- 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.31 KB (4,248 words) - 12:18, 9 June 2022
- ...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 speci5 KB (688 words) - 12:30, 14 March 2019
- ...to have write access for the IC user can be configured via the following config item: ...last access time) within the cache are configured via the the following IC config properties:21 KB (3,180 words) - 12:14, 9 October 2023
- # http://autoconfig.example.org/mail/config-v1.1.xml # http://example.org/.well-known/autoconfig/mail/config-v1.1.xml6 KB (820 words) - 10:20, 28 January 2021
- ...limits or add additional limits have a look at our default example drop-in config which is located at /etc/systemd/system/open-xchange.service.d/limits.conf ...The technical implementation of systemd differs as service definition and config aren't read every time during service start but the changes need to be rere24 KB (3,264 words) - 16:52, 26 April 2017
- Apply the following config-cascade enabled properties:1 KB (137 words) - 16:23, 20 October 2017
- The config file we use is given below. Since OX App Suite has its own built-in read/wr5 KB (750 words) - 12:16, 18 October 2017
- ...en-xchange/sbin/changeuser -c 1 -A oxadmin -P admin_password -u testuser --config/com.openexchange.capability.guard-mail=true</source> ...en-xchange/sbin/changeuser -c 1 -A oxadmin -P admin_password -u testuser --config/com.openexchange.capability.guard-drive=true</source>39 KB (5,606 words) - 09:59, 5 February 2020