· 8 years ago · Jul 28, 2018, 09:26 PM
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 program.
9 * If you make changes to this file, be sure to protect it again after making
10 * your modifications. Failure to remove write permissions to this file is a
11 * security risk.
12 *
13 * The configuration file to be loaded is based upon the rules below. However
14 * if the multisite aliasing file named sites/sites.php is present, it will be
15 * loaded, and the aliases in the array $sites will override the default
16 * directory rules below. See sites/example.sites.php for more information about
17 * aliases.
18 *
19 * The configuration directory will be discovered by stripping the website's
20 * hostname from left to right and pathname from right to left. The first
21 * configuration file found will be used and any others will be ignored. If no
22 * other configuration file is found then the default configuration file at
23 * 'sites/default' will be used.
24 *
25 * For example, for a fictitious site installed at
26 * http://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
27 * for in the following directories:
28 *
29 * - sites/8080.www.drupal.org.mysite.test
30 * - sites/www.drupal.org.mysite.test
31 * - sites/drupal.org.mysite.test
32 * - sites/org.mysite.test
33 *
34 * - sites/8080.www.drupal.org.mysite
35 * - sites/www.drupal.org.mysite
36 * - sites/drupal.org.mysite
37 * - sites/org.mysite
38 *
39 * - sites/8080.www.drupal.org
40 * - sites/www.drupal.org
41 * - sites/drupal.org
42 * - sites/org
43 *
44 * - sites/default
45 *
46 * Note that if you are installing on a non-standard port number, prefix the
47 * hostname with that number. For example,
48 * http://www.drupal.org:8080/mysite/test/ could be loaded from
49 * sites/8080.www.drupal.org.mysite.test/.
50 *
51 * @see example.sites.php
52 * @see conf_path()
53 */
54
55/**
56 * Database settings:
57 *
58 * The $databases array specifies the database connection or
59 * connections that Drupal may use. Drupal is able to connect
60 * to multiple databases, including multiple types of databases,
61 * during the same request.
62 *
63 * Each database connection is specified as an array of settings,
64 * similar to the following:
65 * @code
66 * array(
67 * 'driver' => 'mysql',
68 * 'database' => 'databasename',
69 * 'username' => 'username',
70 * 'password' => 'password',
71 * 'host' => 'localhost',
72 * 'port' => 3306,
73 * 'prefix' => 'myprefix_',
74 * 'collation' => 'utf8_general_ci',
75 * );
76 * @endcode
77 *
78 * The "driver" property indicates what Drupal database driver the
79 * connection should use. This is usually the same as the name of the
80 * database type, such as mysql or sqlite, but not always. The other
81 * properties will vary depending on the driver. For SQLite, you must
82 * specify a database file name in a directory that is writable by the
83 * webserver. For most other drivers, you must specify a
84 * username, password, host, and database name.
85 *
86 * Transaction support is enabled by default for all drivers that support it,
87 * including MySQL. To explicitly disable it, set the 'transactions' key to
88 * FALSE.
89 * Note that some configurations of MySQL, such as the MyISAM engine, don't
90 * support it and will proceed silently even if enabled. If you experience
91 * transaction related crashes with such configuration, set the 'transactions'
92 * key to FALSE.
93 *
94 * For each database, you may optionally specify multiple "target" databases.
95 * A target database allows Drupal to try to send certain queries to a
96 * different database if it can but fall back to the default connection if not.
97 * That is useful for master/slave replication, as Drupal may try to connect
98 * to a slave server when appropriate and if one is not available will simply
99 * fall back to the single master server.
100 *
101 * The general format for the $databases array is as follows:
102 * @code
103 * $databases['default']['default'] = $info_array;
104 * $databases['default']['slave'][] = $info_array;
105 * $databases['default']['slave'][] = $info_array;
106 * $databases['extra']['default'] = $info_array;
107 * @endcode
108 *
109 * In the above example, $info_array is an array of settings described above.
110 * The first line sets a "default" database that has one master database
111 * (the second level default). The second and third lines create an array
112 * of potential slave databases. Drupal will select one at random for a given
113 * request as needed. The fourth line creates a new database with a name of
114 * "extra".
115 *
116 * For a single database configuration, the following is sufficient:
117 * @code
118 * $databases['default']['default'] = array(
119 * 'driver' => 'mysql',
120 * 'database' => 'databasename',
121 * 'username' => 'username',
122 * 'password' => 'password',
123 * 'host' => 'localhost',
124 * 'prefix' => 'main_',
125 * 'collation' => 'utf8_general_ci',
126 * );
127 * @endcode
128 *
129 * You can optionally set prefixes for some or all database table names
130 * by using the 'prefix' setting. If a prefix is specified, the table
131 * name will be prepended with its value. Be sure to use valid database
132 * characters only, usually alphanumeric and underscore. If no prefixes
133 * are desired, leave it as an empty string ''.
134 *
135 * To have all database names prefixed, set 'prefix' as a string:
136 * @code
137 * 'prefix' => 'main_',
138 * @endcode
139 * To provide prefixes for specific tables, set 'prefix' as an array.
140 * The array's keys are the table names and the values are the prefixes.
141 * The 'default' element is mandatory and holds the prefix for any tables
142 * not specified elsewhere in the array. Example:
143 * @code
144 * 'prefix' => array(
145 * 'default' => 'main_',
146 * 'users' => 'shared_',
147 * 'sessions' => 'shared_',
148 * 'role' => 'shared_',
149 * 'authmap' => 'shared_',
150 * ),
151 * @endcode
152 * You can also use a reference to a schema/database as a prefix. This may be
153 * useful if your Drupal installation exists in a schema that is not the default
154 * or you want to access several databases from the same code base at the same
155 * time.
156 * Example:
157 * @code
158 * 'prefix' => array(
159 * 'default' => 'main.',
160 * 'users' => 'shared.',
161 * 'sessions' => 'shared.',
162 * 'role' => 'shared.',
163 * 'authmap' => 'shared.',
164 * );
165 * @endcode
166 * NOTE: MySQL and SQLite's definition of a schema is a database.
167 *
168 * Advanced users can add or override initial commands to execute when
169 * connecting to the database server, as well as PDO connection settings. For
170 * example, to enable MySQL SELECT queries to exceed the max_join_size system
171 * variable, and to reduce the database connection timeout to 5 seconds:
172 *
173 * @code
174 * $databases['default']['default'] = array(
175 * 'init_commands' => array(
176 * 'big_selects' => 'SET SQL_BIG_SELECTS=1',
177 * ),
178 * 'pdo' => array(
179 * PDO::ATTR_TIMEOUT => 5,
180 * ),
181 * );
182 * @endcode
183 *
184 * WARNING: These defaults are designed for database portability. Changing them
185 * may cause unexpected behavior, including potential data loss.
186 *
187 * @see DatabaseConnection_mysql::__construct
188 * @see DatabaseConnection_pgsql::__construct
189 * @see DatabaseConnection_sqlite::__construct
190 *
191 * Database configuration format:
192 * @code
193 * $databases['default']['default'] = array(
194 * 'driver' => 'mysql',
195 * 'database' => 'databasename',
196 * 'username' => 'username',
197 * 'password' => 'password',
198 * 'host' => 'localhost',
199 * 'prefix' => '',
200 * );
201 * $databases['default']['default'] = array(
202 * 'driver' => 'pgsql',
203 * 'database' => 'databasename',
204 * 'username' => 'username',
205 * 'password' => 'password',
206 * 'host' => 'localhost',
207 * 'prefix' => '',
208 * );
209 * $databases['default']['default'] = array(
210 * 'driver' => 'sqlite',
211 * 'database' => '/path/to/databasefilename',
212 * );
213 * @endcode
214 */
215$databases = array(
216
217 'default' =>
218 array (
219 'default' =>
220 array (
221
222 'database' => 'portal',
223 'username' => 'portal_user',
224 'password' => '123',
225 'host' => 'localhost',
226 'port' => '',
227 'driver' => 'mysql',
228 'prefix' => '',
229 ),
230 ),
231);
232
233/**
234 * Access control for update.php script.
235 *
236 * If you are updating your Drupal installation using the update.php script but
237 * are not logged in using either an account with the "Administer software
238 * updates" permission or the site maintenance account (the account that was
239 * created during installation), you will need to modify the access check
240 * statement below. Change the FALSE to a TRUE to disable the access check.
241 * After finishing the upgrade, be sure to open this file again and change the
242 * TRUE back to a FALSE!
243 */
244$update_free_access = FALSE;
245
246/**
247 * Salt for one-time login links and cancel links, form tokens, etc.
248 *
249 * This variable will be set to a random value by the installer. All one-time
250 * login links will be invalidated if the value is changed. Note that if your
251 * site is deployed on a cluster of web servers, you must ensure that this
252 * variable has the same value on each server. If this variable is empty, a hash
253 * of the serialized database credentials will be used as a fallback salt.
254 *
255 * For enhanced security, you may set this variable to a value using the
256 * contents of a file outside your docroot that is never saved together
257 * with any backups of your Drupal files and database.
258 *
259 * Example:
260 * $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
261 *
262 */
263$drupal_hash_salt = '';
264
265/**
266 * Base URL (optional).
267 *
268 * If Drupal is generating incorrect URLs on your site, which could
269 * be in HTML headers (links to CSS and JS files) or visible links on pages
270 * (such as in menus), uncomment the Base URL statement below (remove the
271 * leading hash sign) and fill in the absolute URL to your Drupal installation.
272 *
273 * You might also want to force users to use a given domain.
274 * See the .htaccess file for more information.
275 *
276 * Examples:
277 * $base_url = 'http://www.example.com';
278 * $base_url = 'http://www.example.com:8888';
279 * $base_url = 'http://www.example.com/drupal';
280 * $base_url = 'https://www.example.com:8888/drupal';
281 *
282 * It is not allowed to have a trailing slash; Drupal will add it
283 * for you.
284 */
285# $base_url = 'http://www.example.com'; // NO trailing slash!
286
287/**
288 * PHP settings:
289 *
290 * To see what PHP settings are possible, including whether they can be set at
291 * runtime (by using ini_set()), read the PHP documentation:
292 * http://www.php.net/manual/ini.list.php
293 * See drupal_environment_initialize() in includes/bootstrap.inc for required
294 * runtime settings and the .htaccess file for non-runtime settings. Settings
295 * defined there should not be duplicated here so as to avoid conflict issues.
296 */
297
298/**
299 * Some distributions of Linux (most notably Debian) ship their PHP
300 * installations with garbage collection (gc) disabled. Since Drupal depends on
301 * PHP's garbage collection for clearing sessions, ensure that garbage
302 * collection occurs by using the most common settings.
303 */
304ini_set('session.gc_probability', 1);
305ini_set('session.gc_divisor', 100);
306
307/**
308 * Set session lifetime (in seconds), i.e. the time from the user's last visit
309 * to the active session may be deleted by the session garbage collector. When
310 * a session is deleted, authenticated users are logged out, and the contents
311 * of the user's $_SESSION variable is discarded.
312 */
313ini_set('session.gc_maxlifetime', 200000);
314
315/**
316 * Set session cookie lifetime (in seconds), i.e. the time from the session is
317 * created to the cookie expires, i.e. when the browser is expected to discard
318 * the cookie. The value 0 means "until the browser is closed".
319 */
320ini_set('session.cookie_lifetime', 2000000);
321
322/**
323 * If you encounter a situation where users post a large amount of text, and
324 * the result is stripped out upon viewing but can still be edited, Drupal's
325 * output filter may not have sufficient memory to process it. If you
326 * experience this issue, you may wish to uncomment the following two lines
327 * and increase the limits of these variables. For more information, see
328 * http://php.net/manual/pcre.configuration.php.
329 */
330# ini_set('pcre.backtrack_limit', 200000);
331# ini_set('pcre.recursion_limit', 200000);
332
333/**
334 * Drupal automatically generates a unique session cookie name for each site
335 * based on its full domain name. If you have multiple domains pointing at the
336 * same Drupal site, you can either redirect them all to a single domain (see
337 * comment in .htaccess), or uncomment the line below and specify their shared
338 * base domain. Doing so assures that users remain logged in as they cross
339 * between your various domains. Make sure to always start the $cookie_domain
340 * with a leading dot, as per RFC 2109.
341 */
342# $cookie_domain = '.example.com';
343
344/**
345 * Variable overrides:
346 *
347 * To override specific entries in the 'variable' table for this site,
348 * set them here. You usually don't need to use this feature. This is
349 * useful in a configuration file for a vhost or directory, rather than
350 * the default settings.php. Any configuration setting from the 'variable'
351 * table can be given a new value. Note that any values you provide in
352 * these variable overrides will not be modifiable from the Drupal
353 * administration interface.
354 *
355 * The following overrides are examples:
356 * - site_name: Defines the site's name.
357 * - theme_default: Defines the default theme for this site.
358 * - anonymous: Defines the human-readable name of anonymous users.
359 * Remove the leading hash signs to enable.
360 */
361# $conf['site_name'] = 'My Drupal site';
362# $conf['theme_default'] = 'garland';
363# $conf['anonymous'] = 'Visitor';
364
365/**
366 * A custom theme can be set for the offline page. This applies when the site
367 * is explicitly set to maintenance mode through the administration page or when
368 * the database is inactive due to an error. It can be set through the
369 * 'maintenance_theme' key. The template file should also be copied into the
370 * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
371 * Note: This setting does not apply to installation and update pages.
372 */
373# $conf['maintenance_theme'] = 'bartik';
374
375/**
376 * Reverse Proxy Configuration:
377 *
378 * Reverse proxy servers are often used to enhance the performance
379 * of heavily visited sites and may also provide other site caching,
380 * security, or encryption benefits. In an environment where Drupal
381 * is behind a reverse proxy, the real IP address of the client should
382 * be determined such that the correct client IP address is available
383 * to Drupal's logging, statistics, and access management systems. In
384 * the most simple scenario, the proxy server will add an
385 * X-Forwarded-For header to the request that contains the client IP
386 * address. However, HTTP headers are vulnerable to spoofing, where a
387 * malicious client could bypass restrictions by setting the
388 * X-Forwarded-For header directly. Therefore, Drupal's proxy
389 * configuration requires the IP addresses of all remote proxies to be
390 * specified in $conf['reverse_proxy_addresses'] to work correctly.
391 *
392 * Enable this setting to get Drupal to determine the client IP from
393 * the X-Forwarded-For header (or $conf['reverse_proxy_header'] if set).
394 * If you are unsure about this setting, do not have a reverse proxy,
395 * or Drupal operates in a shared hosting environment, this setting
396 * should remain commented out.
397 *
398 * In order for this setting to be used you must specify every possible
399 * reverse proxy IP address in $conf['reverse_proxy_addresses'].
400 * If a complete list of reverse proxies is not available in your
401 * environment (for example, if you use a CDN) you may set the
402 * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
403 * Be aware, however, that it is likely that this would allow IP
404 * address spoofing unless more advanced precautions are taken.
405 */
406# $conf['reverse_proxy'] = TRUE;
407
408/**
409 * Specify every reverse proxy IP address in your environment.
410 * This setting is required if $conf['reverse_proxy'] is TRUE.
411 */
412# $conf['reverse_proxy_addresses'] = array('a.b.c.d', ...);
413
414/**
415 * Set this value if your proxy server sends the client IP in a header
416 * other than X-Forwarded-For.
417 */
418# $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';
419
420/**
421 * Page caching:
422 *
423 * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
424 * views. This tells a HTTP proxy that it may return a page from its local
425 * cache without contacting the web server, if the user sends the same Cookie
426 * header as the user who originally requested the cached page. Without "Vary:
427 * Cookie", authenticated users would also be served the anonymous page from
428 * the cache. If the site has mostly anonymous users except a few known
429 * editors/administrators, the Vary header can be omitted. This allows for
430 * better caching in HTTP proxies (including reverse proxies), i.e. even if
431 * clients send different cookies, they still get content served from the cache.
432 * However, authenticated users should access the site directly (i.e. not use an
433 * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
434 * getting cached pages from the proxy.
435 */
436# $conf['omit_vary_cookie'] = TRUE;
437
438/**
439 * CSS/JS aggregated file gzip compression:
440 *
441 * By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
442 * store a gzip compressed (.gz) copy of the aggregated files. If this file is
443 * available then rewrite rules in the default .htaccess file will serve these
444 * files to browsers that accept gzip encoded content. This allows pages to load
445 * faster for these users and has minimal impact on server load. If you are
446 * using a webserver other than Apache httpd, or a caching reverse proxy that is
447 * configured to cache and compress these files itself you may want to uncomment
448 * one or both of the below lines, which will prevent gzip files being stored.
449 */
450# $conf['css_gzip_compression'] = FALSE;
451# $conf['js_gzip_compression'] = FALSE;
452
453/**
454 * Block caching:
455 *
456 * Block caching may not be compatible with node access modules depending on
457 * how the original block cache policy is defined by the module that provides
458 * the block. By default, Drupal therefore disables block caching when one or
459 * more modules implement hook_node_grants(). If you consider block caching to
460 * be safe on your site and want to bypass this restriction, uncomment the line
461 * below.
462 */
463# $conf['block_cache_bypass_node_grants'] = TRUE;
464
465/**
466 * String overrides:
467 *
468 * To override specific strings on your site with or without enabling the Locale
469 * module, add an entry to this list. This functionality allows you to change
470 * a small number of your site's default English language interface strings.
471 *
472 * Remove the leading hash signs to enable.
473 */
474# $conf['locale_custom_strings_en'][''] = array(
475# 'forum' => 'Discussion board',
476# '@count min' => '@count minutes',
477# );
478
479/**
480 *
481 * IP blocking:
482 *
483 * To bypass database queries for denied IP addresses, use this setting.
484 * Drupal queries the {blocked_ips} table by default on every page request
485 * for both authenticated and anonymous users. This allows the system to
486 * block IP addresses from within the administrative interface and before any
487 * modules are loaded. However on high traffic websites you may want to avoid
488 * this query, allowing you to bypass database access altogether for anonymous
489 * users under certain caching configurations.
490 *
491 * If using this setting, you will need to add back any IP addresses which
492 * you may have blocked via the administrative interface. Each element of this
493 * array represents a blocked IP address. Uncommenting the array and leaving it
494 * empty will have the effect of disabling IP blocking on your site.
495 *
496 * Remove the leading hash signs to enable.
497 */
498# $conf['blocked_ips'] = array(
499# 'a.b.c.d',
500# );
501
502/**
503 * Fast 404 pages:
504 *
505 * Drupal can generate fully themed 404 pages. However, some of these responses
506 * are for images or other resource files that are not displayed to the user.
507 * This can waste bandwidth, and also generate server load.
508 *
509 * The options below return a simple, fast 404 page for URLs matching a
510 * specific pattern:
511 * - 404_fast_paths_exclude: A regular expression to match paths to exclude,
512 * such as images generated by image styles, or dynamically-resized images.
513 * The default pattern provided below also excludes the private file system.
514 * If you need to add more paths, you can add '|path' to the expression.
515 * - 404_fast_paths: A regular expression to match paths that should return a
516 * simple 404 page, rather than the fully themed 404 page. If you don't have
517 * any aliases ending in htm or html you can add '|s?html?' to the expression.
518 * - 404_fast_html: The html to return for simple 404 pages.
519 *
520 * Add leading hash signs if you would like to disable this functionality.
521 */
522$conf['404_fast_paths_exclude'] = '/\/(?:styles)|(?:system\/files)\//';
523$conf['404_fast_paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
524$conf['404_fast_html'] = '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>404 Not Found</title></head><body><h1>Not Found</h1><p>The requested URL "@path" was not found on this server.</p></body></html>';
525
526/**
527 * By default the page request process will return a fast 404 page for missing
528 * files if they match the regular expression set in '404_fast_paths' and not
529 * '404_fast_paths_exclude' above. 404 errors will simultaneously be logged in
530 * the Drupal system log.
531 *
532 * You can choose to return a fast 404 page earlier for missing pages (as soon
533 * as settings.php is loaded) by uncommenting the line below. This speeds up
534 * server response time when loading 404 error pages and prevents the 404 error
535 * from being logged in the Drupal system log. In order to prevent valid pages
536 * such as image styles and other generated content that may match the
537 * '404_fast_paths' regular expression from returning 404 errors, it is
538 * necessary to add them to the '404_fast_paths_exclude' regular expression
539 * above. Make sure that you understand the effects of this feature before
540 * uncommenting the line below.
541 */
542# drupal_fast_404();
543
544/**
545 * External access proxy settings:
546 *
547 * If your site must access the Internet via a web proxy then you can enter
548 * the proxy settings here. Currently only basic authentication is supported
549 * by using the username and password variables. The proxy_user_agent variable
550 * can be set to NULL for proxies that require no User-Agent header or to a
551 * non-empty string for proxies that limit requests to a specific agent. The
552 * proxy_exceptions variable is an array of host names to be accessed directly,
553 * not via proxy.
554 */
555# $conf['proxy_server'] = '';
556# $conf['proxy_port'] = 8080;
557# $conf['proxy_username'] = '';
558# $conf['proxy_password'] = '';
559# $conf['proxy_user_agent'] = '';
560# $conf['proxy_exceptions'] = array('127.0.0.1', 'localhost');
561
562/**
563 * Authorized file system operations:
564 *
565 * The Update manager module included with Drupal provides a mechanism for
566 * site administrators to securely install missing updates for the site
567 * directly through the web user interface. On securely-configured servers,
568 * the Update manager will require the administrator to provide SSH or FTP
569 * credentials before allowing the installation to proceed; this allows the
570 * site to update the new files as the user who owns all the Drupal files,
571 * instead of as the user the webserver is running as. On servers where the
572 * webserver user is itself the owner of the Drupal files, the administrator
573 * will not be prompted for SSH or FTP credentials (note that these server
574 * setups are common on shared hosting, but are inherently insecure).
575 *
576 * Some sites might wish to disable the above functionality, and only update
577 * the code directly via SSH or FTP themselves. This setting completely
578 * disables all functionality related to these authorized file operations.
579 *
580 * @see http://drupal.org/node/244924
581 *
582 * Remove the leading hash signs to disable.
583 */
584# $conf['allow_authorize_operations'] = FALSE;
585
586/**
587 * Theme debugging:
588 *
589 * When debugging is enabled:
590 * - The markup of each template is surrounded by HTML comments that contain
591 * theming information, such as template file name suggestions.
592 * - Note that this debugging markup will cause automated tests that directly
593 * check rendered HTML to fail.
594 *
595 * For more information about debugging theme templates, see
596 * https://www.drupal.org/node/223440#theme-debug.
597 *
598 * Not recommended in production environments.
599 *
600 * Remove the leading hash sign to enable.
601 */
602# $conf['theme_debug'] = TRUE;
603
604
605$conf['base-mod-conf']= array(
606 'zayavkasabspathtofilesdir'=>'/var/www/dev/tender-files',
607 'userabspathtofilesdir'=>'/var/www/dev/user-files',
608);