Horde :: Horde Configuration

The preferences backend is currently unavailable and your preferences have not been loaded. You may continue to use the system with default preferences.
Last login: Never

General Horde Settings
* $conf[vhosts]	Enable virtual host configuration? If you want to use a single Horde installation for different virtual hosts, you can create separate configuration files for each virtual host, e.g. `conf-www.example.com.php` or `prefs-mail.example.com.php`. The global configuration files are always loaded first, and virtual host specific files are not required. If running command line scripts, you can specify the host name with the environment variable SERVER_NAME.
PHP Settings
* $conf[debug_level]	The value to set error_reporting() to. See http://www.php.net/manual/function.error-reporting.php for more information and possible values. Enter a valid PHP expression.
* $conf[max_exec_time]	If we need to perform a long operation, what should we set max_execution_time to (in seconds)? 0 means no limit; however, a value of 0 will cause a warning if you are running in safe mode. See http://www.php.net/manual/function.set-time-limit.php for more information.
* $conf[compress_pages]	If this option is set to true, and you have the php zlib extension installed, pages over a certain size will be compressed and sent to the browser as gzip-encoded data in order to save bandwidth. There is little reason not to enable this.
* $conf[secret_key]	Secret key for generating signed messages from this server. This is a random string unique to this Horde installation.
* $conf[umask]	What umask should we run with? This will affect the permissions on any temporary files that are created. This value is an integer.
* $conf[testdisable]	Disable the test script (horde/test.php)? For security reasons, this is disabled by default
$conf[tmpdir]	If you want to use a temporary directory other than the system default or the one specified in php's upload_tmp_dir value, enter it here.
URL Settings
* $conf[use_ssl]	Determines how we generate full URLs (for location headers and such).
* $conf[server][name]	What server name should we use? You'll probably know if you need to change this default; only in situations where you need to override what Apache thinks the server name is. Enter a valid PHP expression.
$conf[server][port]	What port number is the webserver running on? Again, you shouldn't need to change the default, and you probably know it if you do. The exception is if you have chosen to always generate https URLs, as described above. Enter a valid PHP expression.
* $conf[urls][token_lifetime]	This is the length of time in minutes that links protected with request tokens (to prevent cross-site request forgery) will be valid. Higher values may make your users more vulnerable to these attacks.
* $conf[urls][hmac_lifetime]	This is the length of time in minutes that links signed with HMACs (to prevent forged URL parametes) will be valid. Higher values may make your users more vulnerable to forgery or phishing.
$conf[urls][pretty]	Use pretty URLs?
$conf[safe_ips]	A list of IP subnets that are considered safe, e.g. to transfer encryption passphrases without requiring an HTTPS connection. (Example: 192.168.0.0, 10.0.0.0) To consider all connections to be safe (e.g. when SSL is handled by an SSL crypto card and not by the webserver) this value should be '*'.
Session Settings
* $conf[session][name]	What name should we use for the session that Horde applications share? If you want to share sessions with other applications on your webserver, you will need to make sure that they are using the same session name. This value can also be used to invalidate previous sessions when upgrading your local version of Horde (Note: Session names must consist of only alphanumeric characters.)
* $conf[session][use_only_cookies]	Should we only allow session information to be stored in a session cookie and not be passed by URL (GET) parameters? This is on by default because passing session information in the URL is a security risk. Consider carefully before turning it off. Cookies must be working and enabled in the browser though, or you won't be able to login to Horde. If false, session information will be passed via both the URL and cookies.
* $conf[session][timeout]	The cookie lifetime (in seconds). If 0, (DEFAULT; RECOMMENDED) cookies will expire when the browser closes. Otherwise, this is the length after which a cookie will expire (this lifetime is updated after every browser request). Setting a non-zero value is NOT RECOMMENDED as there is no guarantee a session will ever expire; additionally, the session expiration value is based on the SERVER, not the CLIENT, so this will most certainly not work the way you want/think it should (see http://www.php.net/manual/en/function.session-set-cookie-params.php) for further information.
* $conf[session][cache_limiter]	What caching level should we use for the session? DO NOT CHANGE THIS UNLESS YOU REALLY KNOW WHAT YOU ARE DOING. Setting this to anything other than 'nocache' will almost certainly result in severely broken script behavior.
* $conf[session][max_time]	The maximum length of time (in seconds) a session can be active after user authentication before it will be destroyed. (Sessions may otherwise never timeout if a user never closes their browser.) 0 means there is no maximum session time (NOT RECOMMENDED).
* $conf[cookie][domain]	What domain should we set cookies from? If you have a cluster that needs to share cookies, this might be '.example.com' - the leading '.' is important. If you only use session cookies (see above), but you are running Horde on an intranet server without a domain part, i.e. http//horde/, you need to set this value to ''. Most likely, though, you won't have to change the default. Enter a valid PHP expression.
* $conf[cookie][path]	What path should we set cookies to? For maximum security this should match the URL where Horde is on your webserver. If Horde is at /horde, then this should be '/horde'. If Horde is installed as the document root, then this needs to be '/' - NOT ''. If IE will be used to access Horde modules, you should read this first (discussing issues with IE's Content Advisor): http://lists.horde.org/archives/imp/Week-of-Mon-20030113/029149.html

NOTE: These are only the default values for any database driven backends. You still need to configure the different systems like "Preferences" to actually use a database backend.
SQL Database Settings
These are the database settings for the traditional relational databases backends (e.g. databases that use SQL to manage its data).
* $conf[sql][phptype]	What database backend should we use?
* $conf[sql][username]	Username to connect to the database as
$conf[sql][password]	Password to connect with
* $conf[sql][protocol]	How should we connect to the database?
* $conf[sql][hostspec]	Database server/host
$conf[sql][port]	Port the DB is running on, if non-standard
* $conf[sql][database]	Database name to use
* $conf[sql][charset]	Internally used charset
* $conf[sql][ssl]	Use SSL to connect to the server?
* $conf[sql][splitread]	Split reads to a different server?
$conf[sql][logqueries]	Should Horde log all queries. If selected, queries will be logged at the DEBUG level to your configured logger.
NoSQL Database Settings
These are the database settings for the NoSQL database backends. These are databases generally optimized for scalability/availability, but do not use a standardized query language to interact with the data.
* $conf[nosql][phptype]	What database backend should we use?

LDAP Settings
NOTE: These are only the default values for any LDAP driven backends. You still need to configure the different systems like "Preferences" to actually use a LDAP backend.
* $conf[ldap][useldap]	Use LDAP?

Authentication Settings
$conf[auth][admins]	Which users should be treated as administrators (root, super-user) by Horde?
* $conf[auth][checkip]	Should we always store and validate the IP address of the client (as seen by the web server) in the session? Doing so will help increase security by making it harder for an attacker from another host to hijack the session.
* $conf[auth][checkbrowser]	Should we always store and validate the browser string of the client (as seen by the web server) in the session? Doing so will help increase security by making it harder for an attacker to hijack the session.
* $conf[auth][resetpassword]	Allow users to reset passwords and provide a link on the login screen?
$conf[auth][resetpassword_from]	The e-mail address to send password reset e-mails from. If empty, is sent from the user's e-mail address.
* $conf[auth][alternate_login]	If this is not false, it is assumed to be the URL of an alternate login screen which will be used in place of horde's default login screen. The URL will have an "app" parameter appended that contains the application that redirected to the login screen, and a "url" parameter with the originally requested URL. The alternate login screen should redirect to that URL after authentication. Alternatively you can include a "%u" place holder in the alternate URL that will be replaced by that original URL. Optionally appended URL parameters are "logout_reason" that contains a number with the logout reason (see the Horde_Auth::REASON_* constants for possible values), and "logout_msg" that contains an error message describing the logout reason.
* $conf[auth][redirect_on_logout]	If this is not false, it is assumed to be the URL of an alternate logout page which users will be sent to when they log out.
* $conf[auth][list_users]	If the authentication backend is capable of listing all users, should we show this list to the users, e.g. in the permissions screen?
* $conf[auth][driver]	What backend should we use for authenticating users to Horde?
* $conf[auth][params][username]	The username to authenticate everyone as
$conf[auth][params][password]	The password to use for the user's credentials
* $conf[auth][params][requestuser]	Allow username to be passed by GET, POST or cookie?
$conf[auth][params][count_bad_logins]	Should Horde count the number of bad logins?
$conf[auth][params][login_block]	Allow to block logins for certain users?
$conf[auth][params][login_block_count]	After how many failed logins the login should be blocked? Setting 0 disables the feature
$conf[auth][params][login_block_time]	How many minutes should the login be blocked? Setting 0 means permanent blocking
Terms of Service Agreement
$conf[tos][file]	If you want to require users to accept certain terms before they can use the system, enter the path of the agreement file to display here.

Logging Settings
* $conf[log][enabled]	Should Horde log errors and other useful information?
* $conf[log][priority]	What level of messages should we log? Each level logs itself and all those that come before it: ALERT would only log alerts and emergencies, but DEBUG would log everything.
$conf[log][ident]	What identifier should we use in the logs?
$conf[log][time_format]	What time format should we use in the logs? (Acceptable formats are the inputs to PHP's date() function). Leave blank to use the default.
* $conf[log][type]	What log driver should we use?
* $conf[log][name]	Syslog facility to use Enter a valid PHP expression.
* $conf[log_accesskeys]	Should Horde log statistics about used access keys? This is only useful for translators of the UI. You also need to set the log level to at least INFO.

Preferences Settings
* $conf[prefs][maxsize]	The maximum size of a preferences entry (in bytes).
* $conf[prefs][driver]	What preferences driver should we use?
* $conf[prefs][params][driverconfig]	Driver configuration
$conf[prefs][params][table]	The name of the preference table in the database [horde_prefs]

Sign Up Settings
* $conf[signup][allow]	Allow non-registered users to register and provide a link on the login screen?

Alarms Settings
* $conf[alarms][driver]	What alarm storage driver should we use?
* $conf[alarms][params][driverconfig]	Driver configuration
$conf[alarms][params][table]	The name of the alarm table in the database [horde_alarms]
* $conf[alarms][params][ttl]	How often should the applications be queried for new alarms, in seconds?

Groups Settings
* $conf[group][driver]	What backend should we use for Horde Groups?
* $conf[group][params][driverconfig]	Driver configuration

Permissions Settings
* $conf[perms][driver]	What backend should we use for Horde Permissions?
* $conf[perms][driverconfig]	Driver configuration

Shares Settings
Shares are objects or lists that can be shared with other users, e.g. calendars that other users can be given read or write access to.
Allow Sharing?
$conf[share][no_sharing]	Prevent users from editing permissions on their shares. This will keep a user from granting other users (or guests) access to their address book, notebook, calendar, etc.
$conf[share][auto_create]	Automatically create personal default shares for any users that don't own any shares?
$conf[share][world]	If you enable this option, users will be able to share their resources with all (authenticated and guest) users on the system.
$conf[share][any_group]	If you enable this option, users will be able to share their resources with any group, regardless of whether or not they are a member. If you disable it, users will only be able to share their resources with groups they are members of.
$conf[share][hidden]	If you enable this option, the shares that a user has access to will NOT be displayed automatically, but only if the user subscribed to them.
Share Caching
Enabling share caching improves performance because the share backend will only be queried once per session. But it also increases the users' session sizes, and share changes won't take effect before the users log in the next time.
$conf[share][cache]	Enable share caching?
Shares Driver
You can use different driver types for the Horde Share system. The default driver is the SQL-NG driver.
* $conf[share][driver]	What backend should we use for Horde Shares?

Caching Settings
* $conf[cache][default_lifetime]	How long, in seconds, should data be cached by default?
* $conf[cache][driver]	If you want to enable the Horde Cache, select a driver here. This is used to speed up portions of Horde by storing commonly processed objects.
$conf[cache][params][dir]	The location to store the cached files
$conf[cache][params][sub]	If non-zero, the number of subdirectories to create to store the file (see, e.g., http://php.net/manual/en/ref.session.php#ini.session.save-path). When creating the directory tree, the md5sum of the cache id will be used. Thus, each level of the tree will have up to 16 subdirectories named [0-9a-f].
$conf[cache][params][prefix]	The filename prefix to use for the cache files.
* $conf[cache][use_memorycache]	Use a separate memory cache driver to store data in memory? If data is not found in this driver, we will fall back to accessing the persistent backend. This setting has no effect if already using a memory caching backend.
CSS Caching
CSS caching packages all stylesheets used in a page into a single file sent to the browser. It also allows compression and optimization of this file to reduce the data size. Caching reduces server load, speeds up the user's browsing experience, and is HIGHLY RECOMMENDED.
* $conf[cachecss]	Cache CSS?
* $conf[cachecssparams][url_version_param]	Add version information to CSS URLs?
Javascript Caching
Javascript caching packages all static javascript files used in a page into more efficient chunks to send to the browser. It also allows compression and optimizations of this file to reduce the data size. Caching reduces server load, speeds up the user's browsing experience, and is HIGHLY RECOMMENDED.
* $conf[cachejs]	Cache javascript?
* $conf[cachejsparams][url_version_param]	Add version information to javascript URLs?
Theme Caching
Theme caching optimizes display of themed elements. Caching reduces server load (specifically by dramatically reducing filesystem access), and is HIGHLY RECOMMENDED. Requires a configured Horde caching backend.
* $conf[cachethemes]	Cache themes?

Locking Settings
* $conf[lock][driver]	If you want to enable resource locking you must choose a driver here.
* $conf[lock][params][driverconfig]	Driver configuration
$conf[lock][params][table]	The name of the locking table in the database [horde_locks]

Tokens Settings
$conf[token][timeout]	The period (in seconds) after which an id is purged
* $conf[token][driver]	If you want to enable Form Tokens, select a driver here. This is used by the Horde::Form:: API and some other parts of Horde to ensure that a form can only be submitted once.
* $conf[token][params][driverconfig]	Driver configuration
$conf[token][params][table]	The name of the tokens table in the database [horde_tokens]

History Settings
* $conf[history][driver]	If you want to enable history tracking, select a driver here. This is required by various subsystems.
* $conf[history][params][driverconfig]	Driver configuration

DAV Settings
* $conf[davstorage][driver]	If you want to use CalDAV or CardDAV, select a driver here. Please note that History system needs to be enabled too.
* $conf[davstorage][params][driverconfig]	Driver configuration

Mailer Settings
* $conf[mailer][type]	What method should we use for sending mail?
$conf[mailer][params][sendmail_path]	The location of the sendmail binary on the filesystem [/usr/sbin/sendmail]
$conf[mailer][params][sendmail_args]	Any extra parameters to pass to the sendmail or sendmail wrapper binary
$conf[mailer][params][sendmail_eol]	The end-of-line (EOL) sequence to use when piping the message to the sendmail binary. It is not possible to reliably auto-configure sendmail, so if your messages are being sent incorrectly, you should adjust this value (if blank, the system default is used).

HTTP Proxy Settings
If you need to use a proxy for fetching HTTP resources (feeds, security keys, external calendars or free/busy information, etc.), configure it here.
$conf[http][proxy][proxy_host]	Proxy host
$conf[http][proxy][proxy_port]	Proxy port
$conf[http][proxy][proxy_user]	Proxy user if necessary
$conf[http][proxy][proxy_pass]	Proxy password

Spell Checker Settings
* $conf[spell][driver]	Choose a Spell Checking backend

GnuPG Settings
$conf[gnupg][path]	If you want users to have the option of using the GNU Privacy Guard program to decrypt/encrypt PGP files, enter the location of the 'gpg' binary here. If this is empty this feature will be disabled. Additional command line arguments, if needed locally (e.g. extensions), can be added at the end of this entry.
$conf[gnupg][keyserver]	To select multiple items, hold down the Control (PC) or Command (Mac) key while clicking. The address of the public PGP keyserver(s) to use.
$conf[gnupg][timeout]	The timeout for connecting to the PGP keyserver. Timeouts are not supported on all systems.

Virtual File Storage Settings
* $conf[vfs][type]	What VFS driver should we use?
* $conf[vfs][params][driverconfig]	Driver configuration

Session Handler Settings
Unless you are running Horde on a PHP cluster, there is NO reason to use any session handler backend other than Builtin (i.e. session data stored on local filesystem).
* $conf[sessionhandler][type]	What sessionhandler driver should we use?
If you have configured a custom session extension in php.ini (such as native memcache sessions) then you should use this option. Horde doesn't force PHP to use the file-based session handler, so your php.ini settings settings will be deferred to.
* $conf[sessionhandler][hashtable]	Use a distributed hash table to cache session information?

OpenSSL Settings
$conf[openssl][cafile]	The location of the root certificates bundle, e.g. /etc/ssl/certs. See http://www.php.net/manual/en/openssl.cert.verification.php for details.
$conf[openssl][path]	The location of the OpenSSL binary on your system, e.g. /usr/bin/openssl. This program is REQUIRED to import personal S/MIME certificate information, as there is no native PHP function that can read pkcs12 files.

Theme Settings
$conf[nobase64_img]	Always send full URLs for image data? By default, Horde will send image data within the page itself if the browser supports it. This eliminates the need for additional server connections to grab the image data, at the expense of slightly larger page sizes.

Image Manipulation Settings
* $conf[image][driver]
Image Metadata Driver Settings
* $conf[exif][driver]

MIME Detection Settings
$conf[mime][magic_db]	Location of the MIME magic database. This only needs to be set if PHP cannot auto-determine the value (the output from the test script will clearly indiciate if this is an issue).

Timezone Lookup Settings
$conf[timezone][location]	Horde may lookup timezone information from a global timezone database, also known as Olson database. You can enter any http://, ftp:// or file:// location here.

Problem Reporting Settings
* $conf[problems][tickets]	If a ticket system with a tickets/addTicket API method is present, should we create tickets for problem reports instead of emailing them?
* $conf[problems][email]	Where should problem report emails be sent?
* $conf[problems][maildomain]	If Horde cannot determine a user's email address, this domain will be appended to their username.
$conf[problems][username]	If requiring SMTP authentication without a global SMTP user (in section "Mailer" and allowing problem reporting for not authenticated users (in section "Menu Settings"), what username should be use for SMTP authentication?
$conf[problems][password]	The password to use
$conf[problems][attachments]	Allow users to upload file attachments to the problem report?

Menu Settings
* $conf[menu][links][help]	Should we display help links in the menu?
* $conf[menu][links][prefs]	Should we display preferences links in the menu? You still need to configure a preference backend in the "Preferences" section.
* $conf[menu][links][problem]	Should we display problem reporting links in the menu?
* $conf[menu][links][login]	Should we display a login link in the menu when not logged in?
* $conf[menu][links][logout]	Should we display a logout link in the menu when logged in?

Portal Blocks Settings
$conf[portal][fixed_blocks]	To select multiple items, hold down the Control (PC) or Command (Mac) key while clicking. Which blocks should always be displayed in the portal?
Fortune Configuration
$conf[fortune][exec_path]	Path to fortune executable, e.g. /usr/games/fortune
Account Info Configuration
* $conf[accounts][driver]	What driver should we use?

User Capabilities and Constraints
* $conf[user][verify_from_addr]	If users are adding new From: addresses to their identities, should we send them a confirmation message to verify that the email address is really theirs?
* $conf[user][select_view]	Allow user to select the application view mode on login?

API Keys Settings
$conf[api][googlemaps]	Google Maps API Key
$conf[api][googlesafebrowsing]	Google Safe Browsing API Key
$conf[api][googlesearch]	Google AJAX Search API Key
$conf[api][bing]	Bing Maps API Key
Facebook Integration Settings
If you want to allow your users to interact with their Facebook profiles, and you've set up the necessary settings on Facebook, you can enter the key and secret here. See http://wiki.horde.org/Doc/Admin/Config/Horde/Facebook for details.
* $conf[facebook][enabled]
Twitter Integration Settings
If you want to allow your users to interact with their Twitter account, enable this section. You must setup an application on Twitter and obtain the OAuth secret and key from Twitter. See http://wiki.horde.org/Doc/Admin/Config/Horde/Twitter for details.
* $conf[twitter][enabled]
Url Shortening
* $conf[urlshortener]	Should Horde use a URL shortening service? This will be used when submitting URLs to social network providers.
Weather Services
If you want to provide weather information to your users you must select a provider and provide your API keys.
* $conf[weather][provider]

IMAP Server Settings
If you intend to store user data like shares and groupware data on an IMAP server then you will need to ensure that the following fields correspond to your IMAP server setup. The IMAP groupware storage will use version 2 of the Kolab XML format. See http://wiki.kolab.org/Kolab_Format_Intro for details.
* $conf[imap][enabled]	Use an IMAP server?

IMSP Server Settings
If you plan to use any of Horde's IMSP server support, enable this option and configure the server settings below. Note that you must still configure/enable specific IMSP support in the appropriate section.
* $conf[imsp][enabled]

Kolab Server Settings
* IF YOU HAVE NO IDEA WHAT KOLAB IS THEN YOU CAN SAFELY IGNORE THIS TAB * Kolab is in no way required for normal Horde usage. If, however, you intend to use Horde as a webclient for Kolab then you will need to ensure that the following fields correspond to those required by your Kolab installation. You can find some of the required values in the `$KOLAB_ROOT/etc/kolab/kolab.conf` configuration file. Please note that the old iCal/vCard storage format has been dropped in favour of the new XML storage format & IMAP folder annotations; subsequently the Horde Kolab modules will only work with version 2 of the Kolab server. If you would like to find out more about Kolab then please visit the Kolab community website at http://www.kolab.org/
* $conf[kolab][enabled]	Horde/Kolab integration status

A distributed hash table is a way of sharing data across multiple servers by associating a piece of data with a static key. It is useful for cache-like operations, since it is usually much faster to set and retrieve the data from the hash table than the underlying data storage driver.
* $conf[hashtable][driver]	What backend should we use for the distributed hash table?