2
// $Id: default.settings.php,v 1.8.2.1 2008/08/13 06:52:36 dries Exp $
6
* Drupal site-specific configuration file.
9
* This file may have been set to read-only by the Drupal installation
10
* program. If you make changes to this file, be sure to protect it again
11
* after making your modifications. Failure to remove write permissions
12
* to this file is a security risk.
14
* The configuration file to be loaded is based upon the rules below.
16
* The configuration directory will be discovered by stripping the
17
* website's hostname from left to right and pathname from right to
18
* left. The first configuration file found will be used and any
19
* others will be ignored. If no other configuration file is found
20
* then the default configuration file at 'sites/default' will be used.
22
* For example, for a fictitious site installed at
23
* http://www.drupal.org/mysite/test/, the 'settings.php'
24
* is searched in the following directories:
26
* 1. sites/www.drupal.org.mysite.test
27
* 2. sites/drupal.org.mysite.test
28
* 3. sites/org.mysite.test
30
* 4. sites/www.drupal.org.mysite
31
* 5. sites/drupal.org.mysite
34
* 7. sites/www.drupal.org
40
* If you are installing on a non-standard port number, prefix the
41
* hostname with that number. For example,
42
* http://www.drupal.org:8080/mysite/test/ could be loaded from
43
* sites/8080.www.drupal.org.mysite.test/.
49
* Note that the $db_url variable gets parsed using PHP's built-in
50
* URL parser (i.e. using the "parse_url()" function) so make sure
51
* not to confuse the parser. If your username, password
52
* or database name contain characters used to delineate
53
* $db_url parts, you can escape them via URI hex encodings:
55
* : = %3a / = %2f @ = %40
56
* + = %2b ( = %28 ) = %29
57
* ? = %3f = = %3d & = %26
59
* To specify multiple connections to be used in your site (i.e. for
60
* complex custom modules) you can also specify an associative array
61
* of $db_url variables with the 'default' element used until otherwise
64
* You can optionally set prefixes for some or all database table names
65
* by using the $db_prefix setting. If a prefix is specified, the table
66
* name will be prepended with its value. Be sure to use valid database
67
* characters only, usually alphanumeric and underscore. If no prefixes
68
* are desired, leave it as an empty string ''.
70
* To have all database names prefixed, set $db_prefix as a string:
72
* $db_prefix = 'main_';
74
* To provide prefixes for specific tables, set $db_prefix as an array.
75
* The array's keys are the table names and the values are the prefixes.
76
* The 'default' element holds the prefix for any tables not specified
77
* elsewhere in the array. Example:
80
* 'default' => 'main_',
81
* 'users' => 'shared_',
82
* 'sessions' => 'shared_',
83
* 'role' => 'shared_',
84
* 'authmap' => 'shared_',
87
* Database URL format:
88
* $db_url = 'mysql://username:password@localhost/databasename';
89
* $db_url = 'mysqli://username:password@localhost/databasename';
90
* $db_url = 'pgsql://username:password@localhost/databasename';
92
$db_url = 'mysqli://username:password@localhost/spreadubuntu';
96
* Access control for update.php script
98
* If you are updating your Drupal installation using the update.php script
99
* being not logged in as administrator, you will need to modify the access
100
* check statement below. Change the FALSE to a TRUE to disable the access
101
* check. After finishing the upgrade, be sure to open this file again
102
* and change the TRUE back to a FALSE!
104
$update_free_access = FALSE;
107
* Base URL (optional).
109
* If you are experiencing issues with different site domains,
110
* uncomment the Base URL statement below (remove the leading hash sign)
111
* and fill in the URL to your Drupal installation.
113
* You might also want to force users to use a given domain.
114
* See the .htaccess file for more information.
117
* $base_url = 'http://www.example.com';
118
* $base_url = 'http://www.example.com:8888';
119
* $base_url = 'http://www.example.com/drupal';
120
* $base_url = 'https://www.example.com:8888/drupal';
122
* It is not allowed to have a trailing slash; Drupal will add it
125
# $base_url = 'http://www.example.com'; // NO trailing slash!
130
* To see what PHP settings are possible, including whether they can
131
* be set at runtime (ie., when ini_set() occurs), read the PHP
132
* documentation at http://www.php.net/manual/en/ini.php#ini.list
133
* and take a look at the .htaccess file to see which non-runtime
134
* settings are used there. Settings defined here should not be
135
* duplicated there so as to avoid conflict issues.
137
ini_set('arg_separator.output', '&');
138
ini_set('magic_quotes_runtime', 0);
139
ini_set('magic_quotes_sybase', 0);
140
ini_set('session.cache_expire', 200000);
141
ini_set('session.cache_limiter', 'none');
142
ini_set('session.cookie_lifetime', 2000000);
143
ini_set('session.gc_maxlifetime', 200000);
144
ini_set('session.save_handler', 'user');
145
ini_set('session.use_only_cookies', 1);
146
ini_set('session.use_trans_sid', 0);
147
ini_set('url_rewriter.tags', '');
150
* Drupal automatically generates a unique session cookie name for each site
151
* based on on its full domain name. If you have multiple domains pointing at
152
* the same Drupal site, you can either redirect them all to a single domain
153
* (see comment in .htaccess), or uncomment the line below and specify their
154
* shared base domain. Doing so assures that users remain logged in as they
155
* cross between your various domains.
157
# $cookie_domain = 'example.com';
160
* Variable overrides:
162
* To override specific entries in the 'variable' table for this site,
163
* set them here. You usually don't need to use this feature. This is
164
* useful in a configuration file for a vhost or directory, rather than
165
* the default settings.php. Any configuration setting from the 'variable'
166
* table can be given a new value. Note that any values you provide in
167
* these variable overrides will not be modifiable from the Drupal
168
* administration interface.
170
* Remove the leading hash signs to enable.
173
# 'site_name' => 'My Drupal site',
174
# 'theme_default' => 'minnelli',
175
# 'anonymous' => 'Visitor',
177
* A custom theme can be set for the off-line page. This applies when the site
178
* is explicitly set to off-line mode through the administration page or when
179
* the database is inactive due to an error. It can be set through the
180
* 'maintenance_theme' key. The template file should also be copied into the
181
* theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
182
* Note: This setting does not apply to installation and update pages.
184
# 'maintenance_theme' => 'minnelli',
186
* reverse_proxy accepts a boolean value.
188
* Enable this setting to determine the correct IP address of the remote
189
* client by examining information stored in the X-Forwarded-For headers.
190
* X-Forwarded-For headers are a standard mechanism for identifying client
191
* systems connecting through a reverse proxy server, such as Squid or
192
* Pound. Reverse proxy servers are often used to enhance the performance
193
* of heavily visited sites and may also provide other site caching,
194
* security or encryption benefits. If this Drupal installation operates
195
* behind a reverse proxy, this setting should be enabled so that correct
196
* IP address information is captured in Drupal's session management,
197
* logging, statistics and access management systems; if you are unsure
198
* about this setting, do not have a reverse proxy, or Drupal operates in
199
* a shared hosting environment, this setting should be set to disabled.
201
# 'reverse_proxy' => TRUE,
203
* reverse_proxy accepts an array of IP addresses.
205
* Each element of this array is the IP address of any of your reverse
206
* proxies. Filling this array Drupal will trust the information stored
207
* in the X-Forwarded-For headers only if Remote IP address is one of
208
* these, that is the request reaches the web server from one of your
209
* reverse proxies. Otherwise, the client could directly connect to
210
* your web server spoofing the X-Forwarded-For headers.
212
# 'reverse_proxy_addresses' => array('a.b.c.d', ...),
218
* To override specific strings on your site with or without enabling locale
219
* module, add an entry to this list. This functionality allows you to change
220
* a small number of your site's default English language interface strings.
222
* Remove the leading hash signs to enable.
224
# $conf['locale_custom_strings_en'] = array(
225
# 'forum' => 'Discussion board',
226
# '@count min' => '@count minutes',