root / bin / settings-D7-bddinde-template.php @ 09c4516a
1 |
<?php
|
---|---|
2 |
|
3 |
/**
|
4 |
* @file
|
5 |
* Drupal site-specific configuration file.
|
6 |
*
|
7 |
* IMPORTANT NOTE:
|
8 |
* This file may have been set to read-only by the Drupal installation
|
9 |
* program. If you make changes to this file, be sure to protect it again
|
10 |
* after making your modifications. Failure to remove write permissions
|
11 |
* to this file is a security risk.
|
12 |
*
|
13 |
* The configuration file to be loaded is based upon the rules below.
|
14 |
*
|
15 |
* The configuration directory will be discovered by stripping the
|
16 |
* website's hostname from left to right and pathname from right to
|
17 |
* left. The first configuration file found will be used and any
|
18 |
* others will be ignored. If no other configuration file is found
|
19 |
* then the default configuration file at 'sites/default' will be used.
|
20 |
*
|
21 |
* For example, for a fictitious site installed at
|
22 |
* http://www.drupal.org/mysite/test/, the 'settings.php'
|
23 |
* is searched in the following directories:
|
24 |
*
|
25 |
* 1. sites/www.drupal.org.mysite.test
|
26 |
* 2. sites/drupal.org.mysite.test
|
27 |
* 3. sites/org.mysite.test
|
28 |
*
|
29 |
* 4. sites/www.drupal.org.mysite
|
30 |
* 5. sites/drupal.org.mysite
|
31 |
* 6. sites/org.mysite
|
32 |
*
|
33 |
* 7. sites/www.drupal.org
|
34 |
* 8. sites/drupal.org
|
35 |
* 9. sites/org
|
36 |
*
|
37 |
* 10. sites/default
|
38 |
*
|
39 |
* If you are installing on a non-standard port number, prefix the
|
40 |
* hostname with that number. For example,
|
41 |
* http://www.drupal.org:8080/mysite/test/ could be loaded from
|
42 |
* sites/8080.www.drupal.org.mysite.test/.
|
43 |
*/
|
44 |
|
45 |
/**
|
46 |
* Database settings:
|
47 |
*
|
48 |
* The $databases array specifies the database connection or
|
49 |
* connections that Drupal may use. Drupal is able to connect
|
50 |
* to multiple databases, including multiple types of databases,
|
51 |
* during the same request.
|
52 |
*
|
53 |
* Each database connection is specified as an array of settings,
|
54 |
* similar to the following:
|
55 |
* @code
|
56 |
* array(
|
57 |
* 'driver' => 'mysql',
|
58 |
* 'database' => 'databasename',
|
59 |
* 'username' => 'username',
|
60 |
* 'password' => 'password',
|
61 |
* 'host' => 'localhost',
|
62 |
* 'port' => 3306,
|
63 |
* 'prefix' => 'myprefix_',
|
64 |
* 'collation' => 'utf8_general_ci',
|
65 |
* );
|
66 |
* @endcode
|
67 |
*
|
68 |
* The "driver" property indicates what Drupal database driver the
|
69 |
* connection should use. This is usually the same as the name of the
|
70 |
* database type, such as mysql or sqlite, but not always. The other
|
71 |
* properties will vary depending on the driver. For SQLite, you must
|
72 |
* specify a database file name in a directory that is writable by the
|
73 |
* webserver. For most other drivers, you must specify a
|
74 |
* username, password, host, and database name.
|
75 |
*
|
76 |
* Some database engines support transactions. In order to enable
|
77 |
* transaction support for a given database, set the 'transactions' key
|
78 |
* to TRUE. To disable it, set it to FALSE. Note that the default value
|
79 |
* varies by driver. For MySQL, the default is FALSE since MyISAM tables
|
80 |
* do not support transactions.
|
81 |
*
|
82 |
* For each database, you may optionally specify multiple "target" databases.
|
83 |
* A target database allows Drupal to try to send certain queries to a
|
84 |
* different database if it can but fall back to the default connection if not.
|
85 |
* That is useful for master/slave replication, as Drupal may try to connect
|
86 |
* to a slave server when appropriate and if one is not available will simply
|
87 |
* fall back to the single master server.
|
88 |
*
|
89 |
* The general format for the $databases array is as follows:
|
90 |
* @code
|
91 |
* $databases['default']['default'] = $info_array;
|
92 |
* $databases['default']['slave'][] = $info_array;
|
93 |
* $databases['default']['slave'][] = $info_array;
|
94 |
* $databases['extra']['default'] = $info_array;
|
95 |
* @endcode
|
96 |
*
|
97 |
* In the above example, $info_array is an array of settings described above.
|
98 |
* The first line sets a "default" database that has one master database
|
99 |
* (the second level default). The second and third lines create an array
|
100 |
* of potential slave databases. Drupal will select one at random for a given
|
101 |
* request as needed. The fourth line creates a new database with a name of
|
102 |
* "extra".
|
103 |
*
|
104 |
* For a single database configuration, the following is sufficient:
|
105 |
* @code
|
106 |
* $databases['default']['default'] = array(
|
107 |
* 'driver' => 'mysql',
|
108 |
* 'database' => 'databasename',
|
109 |
* 'username' => 'username',
|
110 |
* 'password' => 'password',
|
111 |
* 'host' => 'localhost',
|
112 |
* 'prefix' => 'main_',
|
113 |
* 'collation' => 'utf8_general_ci',
|
114 |
* );
|
115 |
* @endcode
|
116 |
*
|
117 |
* You can optionally set prefixes for some or all database table names
|
118 |
* by using the 'prefix' setting. If a prefix is specified, the table
|
119 |
* name will be prepended with its value. Be sure to use valid database
|
120 |
* characters only, usually alphanumeric and underscore. If no prefixes
|
121 |
* are desired, leave it as an empty string ''.
|
122 |
*
|
123 |
* To have all database names prefixed, set 'prefix' as a string:
|
124 |
* @code
|
125 |
* 'prefix' => 'main_',
|
126 |
* @endcode
|
127 |
* To provide prefixes for specific tables, set 'prefix' as an array.
|
128 |
* The array's keys are the table names and the values are the prefixes.
|
129 |
* The 'default' element is mandatory and holds the prefix for any tables
|
130 |
* not specified elsewhere in the array. Example:
|
131 |
* @code
|
132 |
* 'prefix' => array(
|
133 |
* 'default' => 'main_',
|
134 |
* 'users' => 'shared_',
|
135 |
* 'sessions' => 'shared_',
|
136 |
* 'role' => 'shared_',
|
137 |
* 'authmap' => 'shared_',
|
138 |
* ),
|
139 |
* @endcode
|
140 |
* You can also use a reference to a schema/database as a prefix. This maybe
|
141 |
* useful if your Drupal installation exists in a schema that is not the default
|
142 |
* or you want to access several databases from the same code base at the same
|
143 |
* time.
|
144 |
* Example:
|
145 |
* @code
|
146 |
* 'prefix' => array(
|
147 |
* 'default' => 'main.',
|
148 |
* 'users' => 'shared.',
|
149 |
* 'sessions' => 'shared.',
|
150 |
* 'role' => 'shared.',
|
151 |
* 'authmap' => 'shared.',
|
152 |
* );
|
153 |
* @endcode
|
154 |
* NOTE: MySQL and SQLite's definition of a schema is a database.
|
155 |
*
|
156 |
* Database configuration format:
|
157 |
* @code
|
158 |
* $databases['default']['default'] = array(
|
159 |
* 'driver' => 'mysql',
|
160 |
* 'database' => 'databasename',
|
161 |
* 'username' => 'username',
|
162 |
* 'password' => 'password',
|
163 |
* 'host' => 'localhost',
|
164 |
* 'prefix' => '',
|
165 |
* );
|
166 |
* $databases['default']['default'] = array(
|
167 |
* 'driver' => 'pgsql',
|
168 |
* 'database' => 'databasename',
|
169 |
* 'username' => 'username',
|
170 |
* 'password' => 'password',
|
171 |
* 'host' => 'localhost',
|
172 |
* 'prefix' => '',
|
173 |
* );
|
174 |
* $databases['default']['default'] = array(
|
175 |
* 'driver' => 'sqlite',
|
176 |
* 'database' => '/path/to/databasefilename',
|
177 |
* );
|
178 |
* @endcode
|
179 |
*/
|
180 |
$databases = array ( |
181 |
'default' =>
|
182 |
array (
|
183 |
'default' =>
|
184 |
array (
|
185 |
'database' => '%%DBNAME%%', |
186 |
'username' => '%%DBUSER%%', |
187 |
'password' => '%%DBPASS%%', |
188 |
'host' => 'myassos.serv.int', |
189 |
'port' => '', |
190 |
'driver' => 'mysql', |
191 |
'prefix' => '', |
192 |
), |
193 |
), |
194 |
); |
195 |
|
196 |
/**
|
197 |
* Access control for update.php script.
|
198 |
*
|
199 |
* If you are updating your Drupal installation using the update.php script but
|
200 |
* are not logged in using either an account with the "Administer software
|
201 |
* updates" permission or the site maintenance account (the account that was
|
202 |
* created during installation), you will need to modify the access check
|
203 |
* statement below. Change the FALSE to a TRUE to disable the access check.
|
204 |
* After finishing the upgrade, be sure to open this file again and change the
|
205 |
* TRUE back to a FALSE!
|
206 |
*/
|
207 |
$update_free_access = FALSE; |
208 |
|
209 |
/**
|
210 |
* Salt for one-time login links and cancel links, form tokens, etc.
|
211 |
*
|
212 |
* This variable will be set to a random value by the installer. All one-time
|
213 |
* login links will be invalidated if the value is changed. Note that this
|
214 |
* variable must have the same value on every web server. If this variable is
|
215 |
* empty, a hash of the serialized database credentials will be used as a
|
216 |
* fallback salt.
|
217 |
*
|
218 |
* For enhanced security, you may set this variable to a value using the
|
219 |
* contents of a file outside your docroot that is never saved together
|
220 |
* with any backups of your Drupal files and database.
|
221 |
*
|
222 |
* Example:
|
223 |
* $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
|
224 |
*
|
225 |
*/
|
226 |
$drupal_hash_salt = 'xDFiCZHVl9O32bnWAipVIwqmRvPbkpjhIVk9z1fEej4'; |
227 |
|
228 |
/**
|
229 |
* Base URL (optional).
|
230 |
*
|
231 |
* If Drupal is generating incorrect URLs on your site, which could
|
232 |
* be in HTML headers (links to CSS and JS files) or visible links on pages
|
233 |
* (such as in menus), uncomment the Base URL statement below (remove the
|
234 |
* leading hash sign) and fill in the absolute URL to your Drupal installation.
|
235 |
*
|
236 |
* You might also want to force users to use a given domain.
|
237 |
* See the .htaccess file for more information.
|
238 |
*
|
239 |
* Examples:
|
240 |
* $base_url = 'http://www.example.com';
|
241 |
* $base_url = 'http://www.example.com:8888';
|
242 |
* $base_url = 'http://www.example.com/drupal';
|
243 |
* $base_url = 'https://www.example.com:8888/drupal';
|
244 |
*
|
245 |
* It is not allowed to have a trailing slash; Drupal will add it
|
246 |
* for you.
|
247 |
*/
|
248 |
$base_url = 'http://assos.centrale-marseille.fr/%%nomsite%%'; // NO trailing slash! |
249 |
|
250 |
/**
|
251 |
* PHP settings:
|
252 |
*
|
253 |
* To see what PHP settings are possible, including whether they can be set at
|
254 |
* runtime (by using ini_set()), read the PHP documentation:
|
255 |
* http://www.php.net/manual/en/ini.list.php
|
256 |
* See drupal_initialize_variables() in includes/bootstrap.inc for required
|
257 |
* runtime settings and the .htaccess file for non-runtime settings. Settings
|
258 |
* defined there should not be duplicated here so as to avoid conflict issues.
|
259 |
*/
|
260 |
|
261 |
/**
|
262 |
* Some distributions of Linux (most notably Debian) ship their PHP
|
263 |
* installations with garbage collection (gc) disabled. Since Drupal depends on
|
264 |
* PHP's garbage collection for clearing sessions, ensure that garbage
|
265 |
* collection occurs by using the most common settings.
|
266 |
*/
|
267 |
ini_set('session.gc_probability', 1); |
268 |
ini_set('session.gc_divisor', 100); |
269 |
|
270 |
/**
|
271 |
* Set session lifetime (in seconds), i.e. the time from the user's last visit
|
272 |
* to the active session may be deleted by the session garbage collector. When
|
273 |
* a session is deleted, authenticated users are logged out, and the contents
|
274 |
* of the user's $_SESSION variable is discarded.
|
275 |
*/
|
276 |
ini_set('session.gc_maxlifetime', 200000); |
277 |
|
278 |
/**
|
279 |
* Set session cookie lifetime (in seconds), i.e. the time from the session is
|
280 |
* created to the cookie expires, i.e. when the browser is expected to discard
|
281 |
* the cookie. The value 0 means "until the browser is closed".
|
282 |
*/
|
283 |
ini_set('session.cookie_lifetime', 2000000); |
284 |
|
285 |
/**
|
286 |
* If you encounter a situation where users post a large amount of text, and
|
287 |
* the result is stripped out upon viewing but can still be edited, Drupal's
|
288 |
* output filter may not have sufficient memory to process it. If you
|
289 |
* experience this issue, you may wish to uncomment the following two lines
|
290 |
* and increase the limits of these variables. For more information, see
|
291 |
* http://php.net/manual/en/pcre.configuration.php.
|
292 |
*/
|
293 |
# ini_set('pcre.backtrack_limit', 200000);
|
294 |
# ini_set('pcre.recursion_limit', 200000);
|
295 |
|
296 |
/**
|
297 |
* Drupal automatically generates a unique session cookie name for each site
|
298 |
* based on its full domain name. If you have multiple domains pointing at the
|
299 |
* same Drupal site, you can either redirect them all to a single domain (see
|
300 |
* comment in .htaccess), or uncomment the line below and specify their shared
|
301 |
* base domain. Doing so assures that users remain logged in as they cross
|
302 |
* between your various domains.
|
303 |
*/
|
304 |
# $cookie_domain = 'example.com';
|
305 |
|
306 |
/**
|
307 |
* Variable overrides:
|
308 |
*
|
309 |
* To override specific entries in the 'variable' table for this site,
|
310 |
* set them here. You usually don't need to use this feature. This is
|
311 |
* useful in a configuration file for a vhost or directory, rather than
|
312 |
* the default settings.php. Any configuration setting from the 'variable'
|
313 |
* table can be given a new value. Note that any values you provide in
|
314 |
* these variable overrides will not be modifiable from the Drupal
|
315 |
* administration interface.
|
316 |
*
|
317 |
* The following overrides are examples:
|
318 |
* - site_name: Defines the site's name.
|
319 |
* - theme_default: Defines the default theme for this site.
|
320 |
* - anonymous: Defines the human-readable name of anonymous users.
|
321 |
* Remove the leading hash signs to enable.
|
322 |
*/
|
323 |
# $conf['site_name'] = 'My Drupal site';
|
324 |
# $conf['theme_default'] = 'garland';
|
325 |
# $conf['anonymous'] = 'Visitor';
|
326 |
|
327 |
/**
|
328 |
* A custom theme can be set for the offline page. This applies when the site
|
329 |
* is explicitly set to maintenance mode through the administration page or when
|
330 |
* the database is inactive due to an error. It can be set through the
|
331 |
* 'maintenance_theme' key. The template file should also be copied into the
|
332 |
* theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
|
333 |
* Note: This setting does not apply to installation and update pages.
|
334 |
*/
|
335 |
# $conf['maintenance_theme'] = 'bartik';
|
336 |
|
337 |
/**
|
338 |
* Enable this setting to determine the correct IP address of the remote
|
339 |
* client by examining information stored in the X-Forwarded-For headers.
|
340 |
* X-Forwarded-For headers are a standard mechanism for identifying client
|
341 |
* systems connecting through a reverse proxy server, such as Squid or
|
342 |
* Pound. Reverse proxy servers are often used to enhance the performance
|
343 |
* of heavily visited sites and may also provide other site caching,
|
344 |
* security or encryption benefits. If this Drupal installation operates
|
345 |
* behind a reverse proxy, this setting should be enabled so that correct
|
346 |
* IP address information is captured in Drupal's session management,
|
347 |
* logging, statistics and access management systems; if you are unsure
|
348 |
* about this setting, do not have a reverse proxy, or Drupal operates in
|
349 |
* a shared hosting environment, this setting should remain commented out.
|
350 |
*/
|
351 |
# $conf['reverse_proxy'] = TRUE;
|
352 |
|
353 |
/**
|
354 |
* Set this value if your proxy server sends the client IP in a header other
|
355 |
* than X-Forwarded-For.
|
356 |
*
|
357 |
* The "X-Forwarded-For" header is a comma+space separated list of IP addresses,
|
358 |
* only the last one (the left-most) will be used.
|
359 |
*/
|
360 |
# $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';
|
361 |
|
362 |
/**
|
363 |
* reverse_proxy accepts an array of IP addresses.
|
364 |
*
|
365 |
* Each element of this array is the IP address of any of your reverse
|
366 |
* proxies. Filling this array Drupal will trust the information stored
|
367 |
* in the X-Forwarded-For headers only if Remote IP address is one of
|
368 |
* these, that is the request reaches the web server from one of your
|
369 |
* reverse proxies. Otherwise, the client could directly connect to
|
370 |
* your web server spoofing the X-Forwarded-For headers.
|
371 |
*/
|
372 |
# $conf['reverse_proxy_addresses'] = array('a.b.c.d', ...);
|
373 |
|
374 |
/**
|
375 |
* Page caching:
|
376 |
*
|
377 |
* By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
|
378 |
* views. This tells a HTTP proxy that it may return a page from its local
|
379 |
* cache without contacting the web server, if the user sends the same Cookie
|
380 |
* header as the user who originally requested the cached page. Without "Vary:
|
381 |
* Cookie", authenticated users would also be served the anonymous page from
|
382 |
* the cache. If the site has mostly anonymous users except a few known
|
383 |
* editors/administrators, the Vary header can be omitted. This allows for
|
384 |
* better caching in HTTP proxies (including reverse proxies), i.e. even if
|
385 |
* clients send different cookies, they still get content served from the cache.
|
386 |
* However, authenticated users should access the site directly (i.e. not use an
|
387 |
* HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
|
388 |
* getting cached pages from the proxy.
|
389 |
*/
|
390 |
# $conf['omit_vary_cookie'] = TRUE;
|
391 |
|
392 |
/**
|
393 |
* CSS/JS aggregated file gzip compression:
|
394 |
*
|
395 |
* By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
|
396 |
* store a gzip compressed (.gz) copy of the aggregated files. If this file is
|
397 |
* available then rewrite rules in the default .htaccess file will serve these
|
398 |
* files to browsers that accept gzip encoded content. This allows pages to load
|
399 |
* faster for these users and has minimal impact on server load. If you are
|
400 |
* using a webserver other than Apache httpd, or a caching reverse proxy that is
|
401 |
* configured to cache and compress these files itself you may want to uncomment
|
402 |
* one or both of the below lines, which will prevent gzip files being stored.
|
403 |
*/
|
404 |
# $conf['css_gzip_compression'] = FALSE;
|
405 |
# $conf['js_gzip_compression'] = FALSE;
|
406 |
|
407 |
/**
|
408 |
* String overrides:
|
409 |
*
|
410 |
* To override specific strings on your site with or without enabling locale
|
411 |
* module, add an entry to this list. This functionality allows you to change
|
412 |
* a small number of your site's default English language interface strings.
|
413 |
*
|
414 |
* Remove the leading hash signs to enable.
|
415 |
*/
|
416 |
# $conf['locale_custom_strings_en'][''] = array(
|
417 |
# 'forum' => 'Discussion board',
|
418 |
# '@count min' => '@count minutes',
|
419 |
# );
|
420 |
|
421 |
/**
|
422 |
*
|
423 |
* IP blocking:
|
424 |
*
|
425 |
* To bypass database queries for denied IP addresses, use this setting.
|
426 |
* Drupal queries the {blocked_ips} table by default on every page request
|
427 |
* for both authenticated and anonymous users. This allows the system to
|
428 |
* block IP addresses from within the administrative interface and before any
|
429 |
* modules are loaded. However on high traffic websites you may want to avoid
|
430 |
* this query, allowing you to bypass database access altogether for anonymous
|
431 |
* users under certain caching configurations.
|
432 |
*
|
433 |
* If using this setting, you will need to add back any IP addresses which
|
434 |
* you may have blocked via the administrative interface. Each element of this
|
435 |
* array represents a blocked IP address. Uncommenting the array and leaving it
|
436 |
* empty will have the effect of disabling IP blocking on your site.
|
437 |
*
|
438 |
* Remove the leading hash signs to enable.
|
439 |
*/
|
440 |
# $conf['blocked_ips'] = array(
|
441 |
# 'a.b.c.d',
|
442 |
# );
|
443 |
|
444 |
/**
|
445 |
* Authorized file system operations:
|
446 |
*
|
447 |
* The Update manager module included with Drupal provides a mechanism for
|
448 |
* site administrators to securely install missing updates for the site
|
449 |
* directly through the web user interface by providing either SSH or FTP
|
450 |
* credentials. This allows the site to update the new files as the user who
|
451 |
* owns all the Drupal files, instead of as the user the webserver is running
|
452 |
* as. However, some sites might wish to disable this functionality, and only
|
453 |
* update the code directly via SSH or FTP themselves. This setting completely
|
454 |
* disables all functionality related to these authorized file operations.
|
455 |
*
|
456 |
* Remove the leading hash signs to disable.
|
457 |
*/
|
458 |
# $conf['allow_authorize_operations'] = FALSE;
|