Search results

== OX Config File Review == Review each config files one by one.

| caldav access. ATTENTION: This is actually handled by the config cascade! | carddav access. ATTENTION: This is actually handled by the config cascade!

...odify /var/www/ox6/3rdparty/tinymce/jscripts/tiny_mce/plugins/spellchecker/config.php to specify the aspell binary location. Please use the following example * config.php

...ge collects typical configuration scenarios that can be addressed with the config cascade

...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).

= Introduction to the config cascade = The config cascade is a configuration system that allows administrators to selectively

There is a config cascade enabled property ('''com.openexchange.frontend.uwa.widgetFile''') t This will make the widget files vary along the config cascade.

...in folder (see above), you will find the configuration file <code>services/config.js</code>. This file contains all services that you want to provide to your == Enable specific services only / Cascading Config ==

| static configured for the config db in configdb.properties and within the configdb for the data dbs (stored

...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"

Apply the following config-cascade enabled properties:

...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 the

==Apache config==

protected int userId = 1234; // read userId from config protected int context = 5678 // read context from config

* Change to the <tt>contacts-ldap</tt> config directory: * create a contacts-ldap config directory for your context.

changeuser ... --config/com.openexchange.capability.[myproduct]=true changecontext -c ... --config/com.openexchange.capability.[myproduct]=true

You can define them system-wide or via the config cascade mechanism. You can define them system-wide or via the config cascade mechanism.

'''Please note''': For some config files, the following interaction dialog may occur: ...hanges have been screwed. You can do this by comparing the new (installed) config file with the dpkg.old files created by dpkg.

grunt.config('connect', { var config = grunt.config().local.appserver;

you may want to check that the following arguments are present in the config file: