{type}
32 |{message}
33 |{summary}
44 |The requested URL "@path" was not found on this server.
'; 688 | 689 | /** 690 | * Load services definition file. 691 | */ 692 | $settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; 693 | 694 | /** 695 | * Override the default service container class. 696 | * 697 | * This is useful for example to trace the service container for performance 698 | * tracking purposes, for testing a service container with an error condition or 699 | * to test a service container that throws an exception. 700 | */ 701 | # $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; 702 | 703 | /** 704 | * Override the default yaml parser class. 705 | * 706 | * Provide a fully qualified class name here if you would like to provide an 707 | * alternate implementation YAML parser. The class must implement the 708 | * \Drupal\Component\Serialization\SerializationInterface interface. 709 | */ 710 | # $settings['yaml_parser_class'] = NULL; 711 | 712 | /** 713 | * Trusted host configuration. 714 | * 715 | * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host 716 | * header spoofing. 717 | * 718 | * To enable the trusted host mechanism, you enable your allowable hosts 719 | * in $settings['trusted_host_patterns']. This should be an array of regular 720 | * expression patterns, without delimiters, representing the hosts you would 721 | * like to allow. 722 | * 723 | * For example: 724 | * @code 725 | * $settings['trusted_host_patterns'] = array( 726 | * '^www\.example\.com$', 727 | * ); 728 | * @endcode 729 | * will allow the site to only run from www.example.com. 730 | * 731 | * If you are running multisite, or if you are running your site from 732 | * different domain names (eg, you don't redirect http://www.example.com to 733 | * http://example.com), you should specify all of the host patterns that are 734 | * allowed by your site. 735 | * 736 | * For example: 737 | * @code 738 | * $settings['trusted_host_patterns'] = array( 739 | * '^example\.com$', 740 | * '^.+\.example\.com$', 741 | * '^example\.org$', 742 | * '^.+\.example\.org$', 743 | * ); 744 | * @endcode 745 | * will allow the site to run off of all variants of example.com and 746 | * example.org, with all subdomains included. 747 | */ 748 | 749 | /** 750 | * The default list of directories that will be ignored by Drupal's file API. 751 | * 752 | * By default ignore node_modules and bower_components folders to avoid issues 753 | * with common frontend tools and recursive scanning of directories looking for 754 | * extensions. 755 | * 756 | * @see file_scan_directory() 757 | * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() 758 | */ 759 | $settings['file_scan_ignore_directories'] = [ 760 | 'node_modules', 761 | 'bower_components', 762 | ]; 763 | 764 | /** 765 | * The default number of entities to update in a batch process. 766 | * 767 | * This is used by update and post-update functions that need to go through and 768 | * change all the entities on a site, so it is useful to increase this number 769 | * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a 770 | * larger number of entities to be processed in a single batch run. 771 | */ 772 | $settings['entity_update_batch_size'] = 50; 773 | 774 | /** 775 | * Load local development override configuration, if available. 776 | * 777 | * Use settings.local.php to override variables on secondary (staging, 778 | * development, etc) installations of this site. Typically used to disable 779 | * caching, JavaScript/CSS compression, re-routing of outgoing emails, and 780 | * other things that should not happen on development and testing sites. 781 | * 782 | * Keep this code block at the end of this file to take full effect. 783 | */ 784 | # 785 | # if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { 786 | # include $app_root . '/' . $site_path . '/settings.local.php'; 787 | # } 788 | -------------------------------------------------------------------------------- /config/drupal/lando.settings.php: -------------------------------------------------------------------------------- 1 | 'databasename', 81 | * 'username' => 'sqlusername', 82 | * 'password' => 'sqlpassword', 83 | * 'host' => 'localhost', 84 | * 'port' => '3306', 85 | * 'driver' => 'mysql', 86 | * 'prefix' => '', 87 | * 'collation' => 'utf8mb4_general_ci', 88 | * ); 89 | * @endcode 90 | */ 91 | $databases = array(); 92 | 93 | /** 94 | * Customizing database settings. 95 | * 96 | * Many of the values of the $databases array can be customized for your 97 | * particular database system. Refer to the sample in the section above as a 98 | * starting point. 99 | * 100 | * The "driver" property indicates what Drupal database driver the 101 | * connection should use. This is usually the same as the name of the 102 | * database type, such as mysql or sqlite, but not always. The other 103 | * properties will vary depending on the driver. For SQLite, you must 104 | * specify a database file name in a directory that is writable by the 105 | * webserver. For most other drivers, you must specify a 106 | * username, password, host, and database name. 107 | * 108 | * Transaction support is enabled by default for all drivers that support it, 109 | * including MySQL. To explicitly disable it, set the 'transactions' key to 110 | * FALSE. 111 | * Note that some configurations of MySQL, such as the MyISAM engine, don't 112 | * support it and will proceed silently even if enabled. If you experience 113 | * transaction related crashes with such configuration, set the 'transactions' 114 | * key to FALSE. 115 | * 116 | * For each database, you may optionally specify multiple "target" databases. 117 | * A target database allows Drupal to try to send certain queries to a 118 | * different database if it can but fall back to the default connection if not. 119 | * That is useful for primary/replica replication, as Drupal may try to connect 120 | * to a replica server when appropriate and if one is not available will simply 121 | * fall back to the single primary server (The terms primary/replica are 122 | * traditionally referred to as master/slave in database server documentation). 123 | * 124 | * The general format for the $databases array is as follows: 125 | * @code 126 | * $databases['default']['default'] = $info_array; 127 | * $databases['default']['replica'][] = $info_array; 128 | * $databases['default']['replica'][] = $info_array; 129 | * $databases['extra']['default'] = $info_array; 130 | * @endcode 131 | * 132 | * In the above example, $info_array is an array of settings described above. 133 | * The first line sets a "default" database that has one primary database 134 | * (the second level default). The second and third lines create an array 135 | * of potential replica databases. Drupal will select one at random for a given 136 | * request as needed. The fourth line creates a new database with a name of 137 | * "extra". 138 | * 139 | * You can optionally set prefixes for some or all database table names 140 | * by using the 'prefix' setting. If a prefix is specified, the table 141 | * name will be prepended with its value. Be sure to use valid database 142 | * characters only, usually alphanumeric and underscore. If no prefixes 143 | * are desired, leave it as an empty string ''. 144 | * 145 | * To have all database names prefixed, set 'prefix' as a string: 146 | * @code 147 | * 'prefix' => 'main_', 148 | * @endcode 149 | * 150 | * Per-table prefixes are deprecated as of Drupal 8.2, and will be removed in 151 | * Drupal 9.0. After that, only a single prefix for all tables will be 152 | * supported. 153 | * 154 | * To provide prefixes for specific tables, set 'prefix' as an array. 155 | * The array's keys are the table names and the values are the prefixes. 156 | * The 'default' element is mandatory and holds the prefix for any tables 157 | * not specified elsewhere in the array. Example: 158 | * @code 159 | * 'prefix' => array( 160 | * 'default' => 'main_', 161 | * 'users' => 'shared_', 162 | * 'sessions' => 'shared_', 163 | * 'role' => 'shared_', 164 | * 'authmap' => 'shared_', 165 | * ), 166 | * @endcode 167 | * You can also use a reference to a schema/database as a prefix. This may be 168 | * useful if your Drupal installation exists in a schema that is not the default 169 | * or you want to access several databases from the same code base at the same 170 | * time. 171 | * Example: 172 | * @code 173 | * 'prefix' => array( 174 | * 'default' => 'main.', 175 | * 'users' => 'shared.', 176 | * 'sessions' => 'shared.', 177 | * 'role' => 'shared.', 178 | * 'authmap' => 'shared.', 179 | * ); 180 | * @endcode 181 | * NOTE: MySQL and SQLite's definition of a schema is a database. 182 | * 183 | * Advanced users can add or override initial commands to execute when 184 | * connecting to the database server, as well as PDO connection settings. For 185 | * example, to enable MySQL SELECT queries to exceed the max_join_size system 186 | * variable, and to reduce the database connection timeout to 5 seconds: 187 | * @code 188 | * $databases['default']['default'] = array( 189 | * 'init_commands' => array( 190 | * 'big_selects' => 'SET SQL_BIG_SELECTS=1', 191 | * ), 192 | * 'pdo' => array( 193 | * PDO::ATTR_TIMEOUT => 5, 194 | * ), 195 | * ); 196 | * @endcode 197 | * 198 | * WARNING: The above defaults are designed for database portability. Changing 199 | * them may cause unexpected behavior, including potential data loss. See 200 | * https://www.drupal.org/developing/api/database/configuration for more 201 | * information on these defaults and the potential issues. 202 | * 203 | * More details can be found in the constructor methods for each driver: 204 | * - \Drupal\Core\Database\Driver\mysql\Connection::__construct() 205 | * - \Drupal\Core\Database\Driver\pgsql\Connection::__construct() 206 | * - \Drupal\Core\Database\Driver\sqlite\Connection::__construct() 207 | * 208 | * Sample Database configuration format for PostgreSQL (pgsql): 209 | * @code 210 | * $databases['default']['default'] = array( 211 | * 'driver' => 'pgsql', 212 | * 'database' => 'databasename', 213 | * 'username' => 'sqlusername', 214 | * 'password' => 'sqlpassword', 215 | * 'host' => 'localhost', 216 | * 'prefix' => '', 217 | * ); 218 | * @endcode 219 | * 220 | * Sample Database configuration format for SQLite (sqlite): 221 | * @code 222 | * $databases['default']['default'] = array( 223 | * 'driver' => 'sqlite', 224 | * 'database' => '/path/to/databasefilename', 225 | * ); 226 | * @endcode 227 | */ 228 | 229 | /** 230 | * Location of the site configuration files. 231 | * 232 | * The $config_directories array specifies the location of file system 233 | * directories used for configuration data. On install, the "sync" directory is 234 | * created. This is used for configuration imports. The "active" directory is 235 | * not created by default since the default storage for active configuration is 236 | * the database rather than the file system. (This can be changed. See "Active 237 | * configuration settings" below). 238 | * 239 | * The default location for the "sync" directory is inside a randomly-named 240 | * directory in the public files path. The setting below allows you to override 241 | * the "sync" location. 242 | * 243 | * If you use files for the "active" configuration, you can tell the 244 | * Configuration system where this directory is located by adding an entry with 245 | * array key CONFIG_ACTIVE_DIRECTORY. 246 | * 247 | * Example: 248 | * @code 249 | * $config_directories = array( 250 | * CONFIG_SYNC_DIRECTORY => '/directory/outside/webroot', 251 | * ); 252 | * @endcode 253 | */ 254 | $config_directories = array(); 255 | 256 | /** 257 | * Settings: 258 | * 259 | * $settings contains environment-specific configuration, such as the files 260 | * directory and reverse proxy address, and temporary configuration, such as 261 | * security overrides. 262 | * 263 | * @see \Drupal\Core\Site\Settings::get() 264 | */ 265 | 266 | /** 267 | * The active installation profile. 268 | * 269 | * Changing this after installation is not recommended as it changes which 270 | * directories are scanned during extension discovery. If this is set prior to 271 | * installation this value will be rewritten according to the profile selected 272 | * by the user. 273 | * 274 | * @see install_select_profile() 275 | * 276 | * @deprecated in Drupal 8.3.0 and will be removed before Drupal 9.0.0. The 277 | * install profile is written to the core.extension configuration. If a 278 | * service requires the install profile use the 'install_profile' container 279 | * parameter. Functional code can use \Drupal::installProfile(). 280 | */ 281 | # $settings['install_profile'] = ''; 282 | 283 | /** 284 | * Salt for one-time login links, cancel links, form tokens, etc. 285 | * 286 | * This variable will be set to a random value by the installer. All one-time 287 | * login links will be invalidated if the value is changed. Note that if your 288 | * site is deployed on a cluster of web servers, you must ensure that this 289 | * variable has the same value on each server. 290 | * 291 | * For enhanced security, you may set this variable to the contents of a file 292 | * outside your document root; you should also ensure that this file is not 293 | * stored with backups of your database. 294 | * 295 | * Example: 296 | * @code 297 | * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); 298 | * @endcode 299 | */ 300 | $settings['hash_salt'] = '9-cZWPN4x_FY7VqpDnpcBtw0DIMWerpu2B57tb2Ue-93vkCM891Qv90dUpMuFhQ57T7o5x_TbQ'; 301 | 302 | /** 303 | * Deployment identifier. 304 | * 305 | * Drupal's dependency injection container will be automatically invalidated and 306 | * rebuilt when the Drupal core version changes. When updating contributed or 307 | * custom code that changes the container, changing this identifier will also 308 | * allow the container to be invalidated as soon as code is deployed. 309 | */ 310 | # $settings['deployment_identifier'] = \Drupal::VERSION; 311 | 312 | /** 313 | * Access control for update.php script. 314 | * 315 | * If you are updating your Drupal installation using the update.php script but 316 | * are not logged in using either an account with the "Administer software 317 | * updates" permission or the site maintenance account (the account that was 318 | * created during installation), you will need to modify the access check 319 | * statement below. Change the FALSE to a TRUE to disable the access check. 320 | * After finishing the upgrade, be sure to open this file again and change the 321 | * TRUE back to a FALSE! 322 | */ 323 | $settings['update_free_access'] = FALSE; 324 | 325 | /** 326 | * External access proxy settings: 327 | * 328 | * If your site must access the Internet via a web proxy then you can enter the 329 | * proxy settings here. Set the full URL of the proxy, including the port, in 330 | * variables: 331 | * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP 332 | * requests. 333 | * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS 334 | * requests. 335 | * You can pass in the user name and password for basic authentication in the 336 | * URLs in these settings. 337 | * 338 | * You can also define an array of host names that can be accessed directly, 339 | * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. 340 | */ 341 | # $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; 342 | # $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; 343 | # $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; 344 | 345 | /** 346 | * Reverse Proxy Configuration: 347 | * 348 | * Reverse proxy servers are often used to enhance the performance 349 | * of heavily visited sites and may also provide other site caching, 350 | * security, or encryption benefits. In an environment where Drupal 351 | * is behind a reverse proxy, the real IP address of the client should 352 | * be determined such that the correct client IP address is available 353 | * to Drupal's logging, statistics, and access management systems. In 354 | * the most simple scenario, the proxy server will add an 355 | * X-Forwarded-For header to the request that contains the client IP 356 | * address. However, HTTP headers are vulnerable to spoofing, where a 357 | * malicious client could bypass restrictions by setting the 358 | * X-Forwarded-For header directly. Therefore, Drupal's proxy 359 | * configuration requires the IP addresses of all remote proxies to be 360 | * specified in $settings['reverse_proxy_addresses'] to work correctly. 361 | * 362 | * Enable this setting to get Drupal to determine the client IP from 363 | * the X-Forwarded-For header (or $settings['reverse_proxy_header'] if set). 364 | * If you are unsure about this setting, do not have a reverse proxy, 365 | * or Drupal operates in a shared hosting environment, this setting 366 | * should remain commented out. 367 | * 368 | * In order for this setting to be used you must specify every possible 369 | * reverse proxy IP address in $settings['reverse_proxy_addresses']. 370 | * If a complete list of reverse proxies is not available in your 371 | * environment (for example, if you use a CDN) you may set the 372 | * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. 373 | * Be aware, however, that it is likely that this would allow IP 374 | * address spoofing unless more advanced precautions are taken. 375 | */ 376 | # $settings['reverse_proxy'] = TRUE; 377 | 378 | /** 379 | * Specify every reverse proxy IP address in your environment. 380 | * This setting is required if $settings['reverse_proxy'] is TRUE. 381 | */ 382 | # $settings['reverse_proxy_addresses'] = array('a.b.c.d', ...); 383 | 384 | /** 385 | * Set this value if your proxy server sends the client IP in a header 386 | * other than X-Forwarded-For. 387 | */ 388 | # $settings['reverse_proxy_header'] = 'X_CLUSTER_CLIENT_IP'; 389 | 390 | /** 391 | * Set this value if your proxy server sends the client protocol in a header 392 | * other than X-Forwarded-Proto. 393 | */ 394 | # $settings['reverse_proxy_proto_header'] = 'X_FORWARDED_PROTO'; 395 | 396 | /** 397 | * Set this value if your proxy server sends the client protocol in a header 398 | * other than X-Forwarded-Host. 399 | */ 400 | # $settings['reverse_proxy_host_header'] = 'X_FORWARDED_HOST'; 401 | 402 | /** 403 | * Set this value if your proxy server sends the client protocol in a header 404 | * other than X-Forwarded-Port. 405 | */ 406 | # $settings['reverse_proxy_port_header'] = 'X_FORWARDED_PORT'; 407 | 408 | /** 409 | * Set this value if your proxy server sends the client protocol in a header 410 | * other than Forwarded. 411 | */ 412 | # $settings['reverse_proxy_forwarded_header'] = 'FORWARDED'; 413 | 414 | /** 415 | * Page caching: 416 | * 417 | * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page 418 | * views. This tells a HTTP proxy that it may return a page from its local 419 | * cache without contacting the web server, if the user sends the same Cookie 420 | * header as the user who originally requested the cached page. Without "Vary: 421 | * Cookie", authenticated users would also be served the anonymous page from 422 | * the cache. If the site has mostly anonymous users except a few known 423 | * editors/administrators, the Vary header can be omitted. This allows for 424 | * better caching in HTTP proxies (including reverse proxies), i.e. even if 425 | * clients send different cookies, they still get content served from the cache. 426 | * However, authenticated users should access the site directly (i.e. not use an 427 | * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid 428 | * getting cached pages from the proxy. 429 | */ 430 | # $settings['omit_vary_cookie'] = TRUE; 431 | 432 | 433 | /** 434 | * Cache TTL for client error (4xx) responses. 435 | * 436 | * Items cached per-URL tend to result in a large number of cache items, and 437 | * this can be problematic on 404 pages which by their nature are unbounded. A 438 | * fixed TTL can be set for these items, defaulting to one hour, so that cache 439 | * backends which do not support LRU can purge older entries. To disable caching 440 | * of client error responses set the value to 0. Currently applies only to 441 | * page_cache module. 442 | */ 443 | # $settings['cache_ttl_4xx'] = 3600; 444 | 445 | /** 446 | * Expiration of cached forms. 447 | * 448 | * Drupal's Form API stores details of forms in a cache and these entries are 449 | * kept for at least 6 hours by default. Expired entries are cleared by cron. 450 | * 451 | * @see \Drupal\Core\Form\FormCache::setCache() 452 | */ 453 | # $settings['form_cache_expiration'] = 21600; 454 | 455 | /** 456 | * Class Loader. 457 | * 458 | * If the APC extension is detected, the Symfony APC class loader is used for 459 | * performance reasons. Detection can be prevented by setting 460 | * class_loader_auto_detect to false, as in the example below. 461 | */ 462 | # $settings['class_loader_auto_detect'] = FALSE; 463 | 464 | /* 465 | * If the APC extension is not detected, either because APC is missing or 466 | * because auto-detection has been disabled, auto-loading falls back to 467 | * Composer's ClassLoader, which is good for development as it does not break 468 | * when code is moved in the file system. You can also decorate the base class 469 | * loader with another cached solution than the Symfony APC class loader, as 470 | * all production sites should have a cached class loader of some sort enabled. 471 | * 472 | * To do so, you may decorate and replace the local $class_loader variable. For 473 | * example, to use Symfony's APC class loader without automatic detection, 474 | * uncomment the code below. 475 | */ 476 | /* 477 | if ($settings['hash_salt']) { 478 | $prefix = 'drupal.' . hash('sha256', 'drupal.' . $settings['hash_salt']); 479 | $apc_loader = new \Symfony\Component\ClassLoader\ApcClassLoader($prefix, $class_loader); 480 | unset($prefix); 481 | $class_loader->unregister(); 482 | $apc_loader->register(); 483 | $class_loader = $apc_loader; 484 | } 485 | */ 486 | 487 | /** 488 | * Authorized file system operations: 489 | * 490 | * The Update Manager module included with Drupal provides a mechanism for 491 | * site administrators to securely install missing updates for the site 492 | * directly through the web user interface. On securely-configured servers, 493 | * the Update manager will require the administrator to provide SSH or FTP 494 | * credentials before allowing the installation to proceed; this allows the 495 | * site to update the new files as the user who owns all the Drupal files, 496 | * instead of as the user the webserver is running as. On servers where the 497 | * webserver user is itself the owner of the Drupal files, the administrator 498 | * will not be prompted for SSH or FTP credentials (note that these server 499 | * setups are common on shared hosting, but are inherently insecure). 500 | * 501 | * Some sites might wish to disable the above functionality, and only update 502 | * the code directly via SSH or FTP themselves. This setting completely 503 | * disables all functionality related to these authorized file operations. 504 | * 505 | * @see https://www.drupal.org/node/244924 506 | * 507 | * Remove the leading hash signs to disable. 508 | */ 509 | # $settings['allow_authorize_operations'] = FALSE; 510 | 511 | /** 512 | * Default mode for directories and files written by Drupal. 513 | * 514 | * Value should be in PHP Octal Notation, with leading zero. 515 | */ 516 | # $settings['file_chmod_directory'] = 0775; 517 | # $settings['file_chmod_file'] = 0664; 518 | 519 | /** 520 | * Public file base URL: 521 | * 522 | * An alternative base URL to be used for serving public files. This must 523 | * include any leading directory path. 524 | * 525 | * A different value from the domain used by Drupal to be used for accessing 526 | * public files. This can be used for a simple CDN integration, or to improve 527 | * security by serving user-uploaded files from a different domain or subdomain 528 | * pointing to the same server. Do not include a trailing slash. 529 | */ 530 | # $settings['file_public_base_url'] = 'http://downloads.example.com/files'; 531 | 532 | /** 533 | * Public file path: 534 | * 535 | * A local file system path where public files will be stored. This directory 536 | * must exist and be writable by Drupal. This directory must be relative to 537 | * the Drupal installation directory and be accessible over the web. 538 | */ 539 | # $settings['file_public_path'] = 'sites/default/files'; 540 | 541 | /** 542 | * Private file path: 543 | * 544 | * A local file system path where private files will be stored. This directory 545 | * must be absolute, outside of the Drupal installation directory and not 546 | * accessible over the web. 547 | * 548 | * Note: Caches need to be cleared when this value is changed to make the 549 | * private:// stream wrapper available to the system. 550 | * 551 | * See https://www.drupal.org/documentation/modules/file for more information 552 | * about securing private files. 553 | */ 554 | # $settings['file_private_path'] = ''; 555 | 556 | /** 557 | * Session write interval: 558 | * 559 | * Set the minimum interval between each session write to database. 560 | * For performance reasons it defaults to 180. 561 | */ 562 | # $settings['session_write_interval'] = 180; 563 | 564 | /** 565 | * String overrides: 566 | * 567 | * To override specific strings on your site with or without enabling the Locale 568 | * module, add an entry to this list. This functionality allows you to change 569 | * a small number of your site's default English language interface strings. 570 | * 571 | * Remove the leading hash signs to enable. 572 | * 573 | * The "en" part of the variable name, is dynamic and can be any langcode of 574 | * any added language. (eg locale_custom_strings_de for german). 575 | */ 576 | # $settings['locale_custom_strings_en'][''] = array( 577 | # 'forum' => 'Discussion board', 578 | # '@count min' => '@count minutes', 579 | # ); 580 | 581 | /** 582 | * A custom theme for the offline page: 583 | * 584 | * This applies when the site is explicitly set to maintenance mode through the 585 | * administration page or when the database is inactive due to an error. 586 | * The template file should also be copied into the theme. It is located inside 587 | * 'core/modules/system/templates/maintenance-page.html.twig'. 588 | * 589 | * Note: This setting does not apply to installation and update pages. 590 | */ 591 | # $settings['maintenance_theme'] = 'bartik'; 592 | 593 | /** 594 | * PHP settings: 595 | * 596 | * To see what PHP settings are possible, including whether they can be set at 597 | * runtime (by using ini_set()), read the PHP documentation: 598 | * http://php.net/manual/ini.list.php 599 | * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime 600 | * settings and the .htaccess file for non-runtime settings. 601 | * Settings defined there should not be duplicated here so as to avoid conflict 602 | * issues. 603 | */ 604 | 605 | /** 606 | * If you encounter a situation where users post a large amount of text, and 607 | * the result is stripped out upon viewing but can still be edited, Drupal's 608 | * output filter may not have sufficient memory to process it. If you 609 | * experience this issue, you may wish to uncomment the following two lines 610 | * and increase the limits of these variables. For more information, see 611 | * http://php.net/manual/pcre.configuration.php. 612 | */ 613 | # ini_set('pcre.backtrack_limit', 200000); 614 | # ini_set('pcre.recursion_limit', 200000); 615 | 616 | /** 617 | * Active configuration settings. 618 | * 619 | * By default, the active configuration is stored in the database in the 620 | * {config} table. To use a different storage mechanism for the active 621 | * configuration, do the following prior to installing: 622 | * - Create an "active" directory and declare its path in $config_directories 623 | * as explained under the 'Location of the site configuration files' section 624 | * above in this file. To enhance security, you can declare a path that is 625 | * outside your document root. 626 | * - Override the 'bootstrap_config_storage' setting here. It must be set to a 627 | * callable that returns an object that implements 628 | * \Drupal\Core\Config\StorageInterface. 629 | * - Override the service definition 'config.storage.active'. Put this 630 | * override in a services.yml file in the same directory as settings.php 631 | * (definitions in this file will override service definition defaults). 632 | */ 633 | # $settings['bootstrap_config_storage'] = array('Drupal\Core\Config\BootstrapConfigStorageFactory', 'getFileStorage'); 634 | 635 | /** 636 | * Configuration overrides. 637 | * 638 | * To globally override specific configuration values for this site, 639 | * set them here. You usually don't need to use this feature. This is 640 | * useful in a configuration file for a vhost or directory, rather than 641 | * the default settings.php. 642 | * 643 | * Note that any values you provide in these variable overrides will not be 644 | * viewable from the Drupal administration interface. The administration 645 | * interface displays the values stored in configuration so that you can stage 646 | * changes to other environments that don't have the overrides. 647 | * 648 | * There are particular configuration values that are risky to override. For 649 | * example, overriding the list of installed modules in 'core.extension' is not 650 | * supported as module install or uninstall has not occurred. Other examples 651 | * include field storage configuration, because it has effects on database 652 | * structure, and 'core.menu.static_menu_link_overrides' since this is cached in 653 | * a way that is not config override aware. Also, note that changing 654 | * configuration values in settings.php will not fire any of the configuration 655 | * change events. 656 | */ 657 | # $config['system.file']['path']['temporary'] = '/tmp'; 658 | # $config['system.site']['name'] = 'My Drupal site'; 659 | # $config['system.theme']['default'] = 'stark'; 660 | # $config['user.settings']['anonymous'] = 'Visitor'; 661 | 662 | /** 663 | * Fast 404 pages: 664 | * 665 | * Drupal can generate fully themed 404 pages. However, some of these responses 666 | * are for images or other resource files that are not displayed to the user. 667 | * This can waste bandwidth, and also generate server load. 668 | * 669 | * The options below return a simple, fast 404 page for URLs matching a 670 | * specific pattern: 671 | * - $config['system.performance']['fast_404']['exclude_paths']: A regular 672 | * expression to match paths to exclude, such as images generated by image 673 | * styles, or dynamically-resized images. The default pattern provided below 674 | * also excludes the private file system. If you need to add more paths, you 675 | * can add '|path' to the expression. 676 | * - $config['system.performance']['fast_404']['paths']: A regular expression to 677 | * match paths that should return a simple 404 page, rather than the fully 678 | * themed 404 page. If you don't have any aliases ending in htm or html you 679 | * can add '|s?html?' to the expression. 680 | * - $config['system.performance']['fast_404']['html']: The html to return for 681 | * simple 404 pages. 682 | * 683 | * Remove the leading hash signs if you would like to alter this functionality. 684 | */ 685 | # $config['system.performance']['fast_404']['exclude_paths'] = '/\/(?:styles)|(?:system\/files)\//'; 686 | # $config['system.performance']['fast_404']['paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i'; 687 | # $config['system.performance']['fast_404']['html'] = 'The requested URL "@path" was not found on this server.
'; 688 | 689 | /** 690 | * Load services definition file. 691 | */ 692 | $settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; 693 | 694 | /** 695 | * Override the default service container class. 696 | * 697 | * This is useful for example to trace the service container for performance 698 | * tracking purposes, for testing a service container with an error condition or 699 | * to test a service container that throws an exception. 700 | */ 701 | # $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; 702 | 703 | /** 704 | * Override the default yaml parser class. 705 | * 706 | * Provide a fully qualified class name here if you would like to provide an 707 | * alternate implementation YAML parser. The class must implement the 708 | * \Drupal\Component\Serialization\SerializationInterface interface. 709 | */ 710 | # $settings['yaml_parser_class'] = NULL; 711 | 712 | /** 713 | * Trusted host configuration. 714 | * 715 | * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host 716 | * header spoofing. 717 | * 718 | * To enable the trusted host mechanism, you enable your allowable hosts 719 | * in $settings['trusted_host_patterns']. This should be an array of regular 720 | * expression patterns, without delimiters, representing the hosts you would 721 | * like to allow. 722 | * 723 | * For example: 724 | * @code 725 | * $settings['trusted_host_patterns'] = array( 726 | * '^www\.example\.com$', 727 | * ); 728 | * @endcode 729 | * will allow the site to only run from www.example.com. 730 | * 731 | * If you are running multisite, or if you are running your site from 732 | * different domain names (eg, you don't redirect http://www.example.com to 733 | * http://example.com), you should specify all of the host patterns that are 734 | * allowed by your site. 735 | * 736 | * For example: 737 | * @code 738 | * $settings['trusted_host_patterns'] = array( 739 | * '^example\.com$', 740 | * '^.+\.example\.com$', 741 | * '^example\.org$', 742 | * '^.+\.example\.org$', 743 | * ); 744 | * @endcode 745 | * will allow the site to run off of all variants of example.com and 746 | * example.org, with all subdomains included. 747 | */ 748 | 749 | /** 750 | * The default list of directories that will be ignored by Drupal's file API. 751 | * 752 | * By default ignore node_modules and bower_components folders to avoid issues 753 | * with common frontend tools and recursive scanning of directories looking for 754 | * extensions. 755 | * 756 | * @see file_scan_directory() 757 | * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() 758 | */ 759 | $settings['file_scan_ignore_directories'] = [ 760 | 'node_modules', 761 | 'bower_components', 762 | ]; 763 | 764 | /** 765 | * The default number of entities to update in a batch process. 766 | * 767 | * This is used by update and post-update functions that need to go through and 768 | * change all the entities on a site, so it is useful to increase this number 769 | * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a 770 | * larger number of entities to be processed in a single batch run. 771 | */ 772 | $settings['entity_update_batch_size'] = 50; 773 | 774 | /** 775 | * Load local development override configuration, if available. 776 | * 777 | * Use settings.local.php to override variables on secondary (staging, 778 | * development, etc) installations of this site. Typically used to disable 779 | * caching, JavaScript/CSS compression, re-routing of outgoing emails, and 780 | * other things that should not happen on development and testing sites. 781 | * 782 | * Keep this code block at the end of this file to take full effect. 783 | */ 784 | # 785 | if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { 786 | include $app_root . '/' . $site_path . '/settings.local.php'; 787 | } 788 | $config_directories['sync'] = '../config/sync'; 789 | $databases['default']['default'] = array ( 790 | 'database' => 'cms', 791 | 'username' => 'cms', 792 | 'password' => 'cms', 793 | 'prefix' => '', 794 | 'host' => 'mariadb', 795 | 'port' => '3306', 796 | 'namespace' => 'Drupal\\Core\\Database\\Driver\\mysql', 797 | 'driver' => 'mysql', 798 | ); 799 | $settings['install_profile'] = 'standard'; 800 | --------------------------------------------------------------------------------