QTrPteww

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