diff --git a/Dockerfile b/Dockerfile index f2f1119..1fb015b 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,5 +1,4 @@ FROM ghcr.io/osu-wams/php:8.2-apache AS production -COPY docker-wams-entry /usr/local/bin ENV PATH="$PATH:/var/www/html/vendor/bin" WORKDIR /var/www/html USER www-data @@ -13,12 +12,10 @@ RUN mkdir -p /var/www/html/docroot/sites/default/files; \ mkdir -p /var/www/files-private; \ chown -R www-data:www-data /var/www/files-private; VOLUME /var/www/html/docroot/sites/default/files -ENTRYPOINT [ "docker-wams-entry" ] CMD [ "apache2-foreground" ] FROM ghcr.io/osu-wams/php:8.2-apache-dev AS development ARG SMTP_HOST=${SMTP_HOST} -COPY docker-wams-entry /usr/local/bin ENV PATH="$PATH:/var/www/html/vendor/bin" WORKDIR /var/www/html COPY --from=production /var/www/html /var/www/html @@ -26,5 +23,4 @@ ARG GITHUB_TOKEN=${GITHUB_TOKEN} RUN composer config --global github-oauth.github.com ${GITHUB_TOKEN} \ && composer install -o ARG GITHUB_TOKEN= -ENTRYPOINT [ "docker-wams-entry" ] CMD [ "apache2-foreground" ] diff --git a/config/drupal-next.cws.oregonstate.edu/.gitkeep b/config/drupal-next.cws.oregonstate.edu/.gitkeep deleted file mode 100644 index e69de29..0000000 diff --git a/docker-wams-entry b/docker-wams-entry deleted file mode 100755 index 4da76d7..0000000 --- a/docker-wams-entry +++ /dev/null @@ -1,13 +0,0 @@ -#!/usr/bin/env bash -set -e -if [ -z "${DRUPAL_THEME_DEVEL}" ]; then - echo "Running in Production Mode" - composer update osulp/osulp-drupal-subtheme && drush cr & -else - cp /var/www/html/docroot/sites/default/default.services.yml /var/www/html/docroot/sites/default/services.yml - sed -i 's/debug\:\ false/debug\:\ true/' /var/www/html/docroot/sites/default/services.yml - sed -i 's/auto_reload\:\ null/auto_reload\:\ true/' /var/www/html/docroot/sites/default/services.yml - sed -i 's/cache\:\ true/cache\:\ false/' /var/www/html/docroot/sites/default/services.yml - echo "Finished setting up Theme Development Settings." -fi -exec "$@" diff --git a/docroot/sites/academicaffairs.oregonstate.edu/settings.php b/docroot/sites/academicaffairs.oregonstate.edu/settings.php deleted file mode 100644 index 5d86f9b..0000000 --- a/docroot/sites/academicaffairs.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/academicaffairs_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/accessibility.oregonstate.edu/settings.php b/docroot/sites/accessibility.oregonstate.edu/settings.php deleted file mode 100644 index 7c089a0..0000000 --- a/docroot/sites/accessibility.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/accessibility_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/accessosu.oregonstate.edu/settings.php b/docroot/sites/accessosu.oregonstate.edu/settings.php deleted file mode 100644 index 9da661e..0000000 --- a/docroot/sites/accessosu.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/accessosu_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/admissions.oregonstate.edu/settings.php b/docroot/sites/admissions.oregonstate.edu/settings.php deleted file mode 100644 index a1374aa..0000000 --- a/docroot/sites/admissions.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/admissions_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/advantage.oregonstate.edu/settings.php b/docroot/sites/advantage.oregonstate.edu/settings.php deleted file mode 100644 index c3eb090..0000000 --- a/docroot/sites/advantage.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/advantage_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/agresearchfoundation.oregonstate.edu/settings.php b/docroot/sites/agresearchfoundation.oregonstate.edu/settings.php deleted file mode 100644 index 98bb907..0000000 --- a/docroot/sites/agresearchfoundation.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/agresearchfoundation_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ai.oregonstate.edu/settings.php b/docroot/sites/ai.oregonstate.edu/settings.php deleted file mode 100644 index 9b645a2..0000000 --- a/docroot/sites/ai.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ai_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/amp.oregonstate.edu/settings.php b/docroot/sites/amp.oregonstate.edu/settings.php deleted file mode 100644 index f1bc416..0000000 --- a/docroot/sites/amp.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/amp_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/apa.oregonstate.edu/settings.php b/docroot/sites/apa.oregonstate.edu/settings.php deleted file mode 100644 index f4f5ff6..0000000 --- a/docroot/sites/apa.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/apa_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/aquaculture.oregonstate.edu/settings.php b/docroot/sites/aquaculture.oregonstate.edu/settings.php deleted file mode 100644 index 5ffc4f8..0000000 --- a/docroot/sites/aquaculture.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/aquaculture_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/asosu.oregonstate.edu/settings.php b/docroot/sites/asosu.oregonstate.edu/settings.php deleted file mode 100644 index 32e4e2d..0000000 --- a/docroot/sites/asosu.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/asosu_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/atami.oregonstate.edu/settings.php b/docroot/sites/atami.oregonstate.edu/settings.php deleted file mode 100644 index 3e1058d..0000000 --- a/docroot/sites/atami.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/atami_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/bartonm.cws.oregonstate.edu/settings.php b/docroot/sites/bartonm.cws.oregonstate.edu/settings.php deleted file mode 100644 index 52d8b9c..0000000 --- a/docroot/sites/bartonm.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/bartonm_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/barvep.cws.oregonstate.edu/settings.php b/docroot/sites/barvep.cws.oregonstate.edu/settings.php deleted file mode 100644 index 6cdc9a0..0000000 --- a/docroot/sites/barvep.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/barvep_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/basicneeds.oregonstate.edu/settings.php b/docroot/sites/basicneeds.oregonstate.edu/settings.php deleted file mode 100644 index f7fbb75..0000000 --- a/docroot/sites/basicneeds.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/basicneeds_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/beaverhangouts.oregonstate.edu/settings.php b/docroot/sites/beaverhangouts.oregonstate.edu/settings.php deleted file mode 100644 index 393603b..0000000 --- a/docroot/sites/beaverhangouts.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/beaverhangouts_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/beaverhealthy.oregonstate.edu/settings.php b/docroot/sites/beaverhealthy.oregonstate.edu/settings.php deleted file mode 100644 index c24abea..0000000 --- a/docroot/sites/beaverhealthy.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/beaverhealthy_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/beavr.oregonstate.edu/settings.php b/docroot/sites/beavr.oregonstate.edu/settings.php deleted file mode 100644 index f287a90..0000000 --- a/docroot/sites/beavr.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/beavr_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/beyond.oregonstate.edu/settings.php b/docroot/sites/beyond.oregonstate.edu/settings.php deleted file mode 100644 index 7af84ac..0000000 --- a/docroot/sites/beyond.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/beyond_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/bhardwai.cws.oregonstate.edu/settings.php b/docroot/sites/bhardwai.cws.oregonstate.edu/settings.php deleted file mode 100644 index 79221c8..0000000 --- a/docroot/sites/bhardwai.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/bhardwai_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/brabhamm.cws.oregonstate.edu/settings.php b/docroot/sites/brabhamm.cws.oregonstate.edu/settings.php deleted file mode 100644 index 2d4637f..0000000 --- a/docroot/sites/brabhamm.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,908 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/brabhamm_cws_oregonstate_edu-settings.inc'; - $config['automated_cron.settings']['interval'] = 0; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/c2f.oregonstate.edu/settings.php b/docroot/sites/c2f.oregonstate.edu/settings.php deleted file mode 100644 index ae19040..0000000 --- a/docroot/sites/c2f.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/c2f_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/caep.oregonstate.edu/settings.php b/docroot/sites/caep.oregonstate.edu/settings.php deleted file mode 100644 index a0c71d5..0000000 --- a/docroot/sites/caep.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/caep_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/camp.oregonstate.edu/settings.php b/docroot/sites/camp.oregonstate.edu/settings.php deleted file mode 100644 index 74cad10..0000000 --- a/docroot/sites/camp.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/camp_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/cape.oregonstate.edu/settings.php b/docroot/sites/cape.oregonstate.edu/settings.php deleted file mode 100644 index 33c9ce1..0000000 --- a/docroot/sites/cape.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/cape_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/career.oregonstate.edu/settings.php b/docroot/sites/career.oregonstate.edu/settings.php deleted file mode 100644 index 7e1ff4c..0000000 --- a/docroot/sites/career.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/career_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ccsi.oregonstate.edu/settings.php b/docroot/sites/ccsi.oregonstate.edu/settings.php deleted file mode 100644 index e2d854b..0000000 --- a/docroot/sites/ccsi.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ccsi_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ceoas.oregonstate.edu/settings.php b/docroot/sites/ceoas.oregonstate.edu/settings.php deleted file mode 100644 index f7f4ff6..0000000 --- a/docroot/sites/ceoas.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ceoas_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/cimers.oregonstate.edu/settings.php b/docroot/sites/cimers.oregonstate.edu/settings.php deleted file mode 100644 index bccd750..0000000 --- a/docroot/sites/cimers.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/cimers_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/cio.oregonstate.edu/settings.php b/docroot/sites/cio.oregonstate.edu/settings.php deleted file mode 100644 index eb9f4f8..0000000 --- a/docroot/sites/cio.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/cio_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/clery.oregonstate.edu/settings.php b/docroot/sites/clery.oregonstate.edu/settings.php deleted file mode 100644 index 25533b4..0000000 --- a/docroot/sites/clery.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/clery_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/colantoe.cws.oregonstate.edu/settings.php b/docroot/sites/colantoe.cws.oregonstate.edu/settings.php deleted file mode 100644 index 5a07de1..0000000 --- a/docroot/sites/colantoe.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/colantoe_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/commencement.oregonstate.edu/settings.php b/docroot/sites/commencement.oregonstate.edu/settings.php deleted file mode 100644 index 6037fc4..0000000 --- a/docroot/sites/commencement.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/commencement_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/coreeducation.oregonstate.edu/settings.php b/docroot/sites/coreeducation.oregonstate.edu/settings.php deleted file mode 100644 index d33a889..0000000 --- a/docroot/sites/coreeducation.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/coreeducation_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/counseling.oregonstate.edu/settings.php b/docroot/sites/counseling.oregonstate.edu/settings.php deleted file mode 100644 index 1eeeb78..0000000 --- a/docroot/sites/counseling.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/counseling_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/craftcenter.oregonstate.edu/settings.php b/docroot/sites/craftcenter.oregonstate.edu/settings.php deleted file mode 100644 index babbf3f..0000000 --- a/docroot/sites/craftcenter.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/craftcenter_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ctl.oregonstate.edu/settings.php b/docroot/sites/ctl.oregonstate.edu/settings.php deleted file mode 100644 index 60bf615..0000000 --- a/docroot/sites/ctl.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ctl_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/data.oregonstate.edu/settings.php b/docroot/sites/data.oregonstate.edu/settings.php deleted file mode 100644 index d8f6b78..0000000 --- a/docroot/sites/data.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/data_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/dce.oregonstate.edu/settings.php b/docroot/sites/dce.oregonstate.edu/settings.php deleted file mode 100644 index c932858..0000000 --- a/docroot/sites/dce.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/dce_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/default/settings.php b/docroot/sites/default/settings.php index 23982d4..5dca283 100644 --- a/docroot/sites/default/settings.php +++ b/docroot/sites/default/settings.php @@ -932,4 +932,5 @@ if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { include $app_root . '/' . $site_path . '/settings.local.php'; -} \ No newline at end of file +} +$settings['config_sync_directory']='../config/default'; \ No newline at end of file diff --git a/docroot/sites/designforimpact.oregonstate.edu/settings.php b/docroot/sites/designforimpact.oregonstate.edu/settings.php deleted file mode 100644 index 444d454..0000000 --- a/docroot/sites/designforimpact.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/designforimpact_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/di.oregonstate.edu/settings.php b/docroot/sites/di.oregonstate.edu/settings.php deleted file mode 100644 index 1531994..0000000 --- a/docroot/sites/di.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/di_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/did.oregonstate.edu/settings.php b/docroot/sites/did.oregonstate.edu/settings.php deleted file mode 100644 index 47e0cf6..0000000 --- a/docroot/sites/did.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/did_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/dive.oregonstate.edu/settings.php b/docroot/sites/dive.oregonstate.edu/settings.php deleted file mode 100644 index a34363e..0000000 --- a/docroot/sites/dive.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/dive_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/diversity.oregonstate.edu/settings.php b/docroot/sites/diversity.oregonstate.edu/settings.php deleted file mode 100644 index 986bbd7..0000000 --- a/docroot/sites/diversity.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/diversity_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/dpo.oregonstate.edu/settings.php b/docroot/sites/dpo.oregonstate.edu/settings.php deleted file mode 100644 index f1e97d7..0000000 --- a/docroot/sites/dpo.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/dpo_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/dreya.cws.oregonstate.edu/settings.php b/docroot/sites/dreya.cws.oregonstate.edu/settings.php deleted file mode 100644 index 8b0cd31..0000000 --- a/docroot/sites/dreya.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/dreya_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/dri.oregonstate.edu/settings.php b/docroot/sites/dri.oregonstate.edu/settings.php deleted file mode 100644 index 994c995..0000000 --- a/docroot/sites/dri.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/dri_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/drupal.oregonstate.edu/settings.php b/docroot/sites/drupal.oregonstate.edu/settings.php deleted file mode 100644 index 16e1b23..0000000 --- a/docroot/sites/drupal.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/drupal_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ds.oregonstate.edu/settings.php b/docroot/sites/ds.oregonstate.edu/settings.php deleted file mode 100644 index 0cbb272..0000000 --- a/docroot/sites/ds.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ds_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/dsi.oregonstate.edu/settings.php b/docroot/sites/dsi.oregonstate.edu/settings.php deleted file mode 100644 index 2407aaa..0000000 --- a/docroot/sites/dsi.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/dsi_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/education.oregonstate.edu/settings.php b/docroot/sites/education.oregonstate.edu/settings.php deleted file mode 100644 index 0539253..0000000 --- a/docroot/sites/education.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/education_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ehsc.oregonstate.edu/settings.php b/docroot/sites/ehsc.oregonstate.edu/settings.php deleted file mode 100644 index 9c8696d..0000000 --- a/docroot/sites/ehsc.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ehsc_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ela.oregonstate.edu/settings.php b/docroot/sites/ela.oregonstate.edu/settings.php deleted file mode 100644 index c6267de..0000000 --- a/docroot/sites/ela.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ela_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/engineering.oregonstate.edu/settings.php b/docroot/sites/engineering.oregonstate.edu/settings.php deleted file mode 100644 index 543a805..0000000 --- a/docroot/sites/engineering.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/engineering_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/enrollmentmanagement.oregonstate.edu/settings.php b/docroot/sites/enrollmentmanagement.oregonstate.edu/settings.php deleted file mode 100644 index 86045d4..0000000 --- a/docroot/sites/enrollmentmanagement.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/enrollmentmanagement_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/eop.oregonstate.edu/settings.php b/docroot/sites/eop.oregonstate.edu/settings.php deleted file mode 100644 index 851f3fa..0000000 --- a/docroot/sites/eop.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/eop_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/eppmo.oregonstate.edu/settings.php b/docroot/sites/eppmo.oregonstate.edu/settings.php deleted file mode 100644 index 0ddc715..0000000 --- a/docroot/sites/eppmo.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/eppmo_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/experience.oregonstate.edu/settings.php b/docroot/sites/experience.oregonstate.edu/settings.php deleted file mode 100644 index 204af37..0000000 --- a/docroot/sites/experience.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/experience_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/extension.cws.oregonstate.edu/settings.php b/docroot/sites/extension.cws.oregonstate.edu/settings.php deleted file mode 100644 index 8a790ee..0000000 --- a/docroot/sites/extension.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/extension_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/facultyaffairs.oregonstate.edu/settings.php b/docroot/sites/facultyaffairs.oregonstate.edu/settings.php deleted file mode 100644 index b701304..0000000 --- a/docroot/sites/facultyaffairs.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/facultyaffairs_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/families.oregonstate.edu/settings.php b/docroot/sites/families.oregonstate.edu/settings.php deleted file mode 100644 index e6932e0..0000000 --- a/docroot/sites/families.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/families_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/fennellc.cws.oregonstate.edu/settings.php b/docroot/sites/fennellc.cws.oregonstate.edu/settings.php deleted file mode 100644 index 0a3ad44..0000000 --- a/docroot/sites/fennellc.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/fennellc_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/fenns.cws.oregonstate.edu/settings.php b/docroot/sites/fenns.cws.oregonstate.edu/settings.php deleted file mode 100644 index 92c49db..0000000 --- a/docroot/sites/fenns.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,908 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/fenns_cws_oregonstate_edu-settings.inc'; - $config['automated_cron.settings']['interval'] = 0; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/financialaid.oregonstate.edu/settings.php b/docroot/sites/financialaid.oregonstate.edu/settings.php deleted file mode 100644 index 3850ef1..0000000 --- a/docroot/sites/financialaid.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/financialaid_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/food.oregonstate.edu/settings.php b/docroot/sites/food.oregonstate.edu/settings.php deleted file mode 100644 index 8584833..0000000 --- a/docroot/sites/food.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/food_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/freedmas.cws.oregonstate.edu/settings.php b/docroot/sites/freedmas.cws.oregonstate.edu/settings.php deleted file mode 100644 index 8f4e089..0000000 --- a/docroot/sites/freedmas.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/freedmas_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/futureai.oregonstate.edu/settings.php b/docroot/sites/futureai.oregonstate.edu/settings.php deleted file mode 100644 index c8fe5b7..0000000 --- a/docroot/sites/futureai.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/futureai_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/gck.oregonstate.edu/settings.php b/docroot/sites/gck.oregonstate.edu/settings.php deleted file mode 100644 index 822f89e..0000000 --- a/docroot/sites/gck.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/gck_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/global.oregonstate.edu/settings.php b/docroot/sites/global.oregonstate.edu/settings.php deleted file mode 100644 index 93c7c34..0000000 --- a/docroot/sites/global.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/global_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/gogreek.oregonstate.edu/settings.php b/docroot/sites/gogreek.oregonstate.edu/settings.php deleted file mode 100644 index 4fd041e..0000000 --- a/docroot/sites/gogreek.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/gogreek_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/goldenkey.oregonstate.edu/settings.php b/docroot/sites/goldenkey.oregonstate.edu/settings.php deleted file mode 100644 index 0dc23cf..0000000 --- a/docroot/sites/goldenkey.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/goldenkey_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/goodwida.cws.oregonstate.edu/settings.php b/docroot/sites/goodwida.cws.oregonstate.edu/settings.php deleted file mode 100644 index e6b29d1..0000000 --- a/docroot/sites/goodwida.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/goodwida_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/government.oregonstate.edu/settings.php b/docroot/sites/government.oregonstate.edu/settings.php deleted file mode 100644 index 6bbb1c1..0000000 --- a/docroot/sites/government.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/government_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/hansenm.cws.oregonstate.edu/settings.php b/docroot/sites/hansenm.cws.oregonstate.edu/settings.php deleted file mode 100644 index df2f6c9..0000000 --- a/docroot/sites/hansenm.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,908 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/hansenm_cws_oregonstate_edu-settings.inc'; - $config['automated_cron.settings']['interval'] = 0; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/health.oregonstate.edu/settings.php b/docroot/sites/health.oregonstate.edu/settings.php deleted file mode 100644 index ff94e6e..0000000 --- a/docroot/sites/health.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/health_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/highlank.cws.oregonstate.edu/settings.php b/docroot/sites/highlank.cws.oregonstate.edu/settings.php deleted file mode 100644 index d68a7bd..0000000 --- a/docroot/sites/highlank.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/highlank_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/hmsc.oregonstate.edu/settings.php b/docroot/sites/hmsc.oregonstate.edu/settings.php deleted file mode 100644 index f569bca..0000000 --- a/docroot/sites/hmsc.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/hmsc_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/holcombk.cws.oregonstate.edu/settings.php b/docroot/sites/holcombk.cws.oregonstate.edu/settings.php deleted file mode 100644 index 3947a81..0000000 --- a/docroot/sites/holcombk.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,908 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/holcombk_cws_oregonstate_edu-settings.inc'; - $config['automated_cron.settings']['interval'] = 0; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/honors.oregonstate.edu/settings.php b/docroot/sites/honors.oregonstate.edu/settings.php deleted file mode 100644 index 977c8ef..0000000 --- a/docroot/sites/honors.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/honors_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/hr.oregonstate.edu/settings.php b/docroot/sites/hr.oregonstate.edu/settings.php deleted file mode 100644 index 2789534..0000000 --- a/docroot/sites/hr.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/hr_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/inr.oregonstate.edu/settings.php b/docroot/sites/inr.oregonstate.edu/settings.php deleted file mode 100644 index a8951aa..0000000 --- a/docroot/sites/inr.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/inr_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/institutionalresearch.oregonstate.edu/settings.php b/docroot/sites/institutionalresearch.oregonstate.edu/settings.php deleted file mode 100644 index 3fe7798..0000000 --- a/docroot/sites/institutionalresearch.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/institutionalresearch_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/internationalservices.oregonstate.edu/settings.php b/docroot/sites/internationalservices.oregonstate.edu/settings.php deleted file mode 100644 index 0fa57db..0000000 --- a/docroot/sites/internationalservices.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/internationalservices_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/kaurmanp.cws.oregonstate.edu/settings.php b/docroot/sites/kaurmanp.cws.oregonstate.edu/settings.php deleted file mode 100644 index f6d5804..0000000 --- a/docroot/sites/kaurmanp.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/kaurmanp_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/koettcra.cws.oregonstate.edu/settings.php b/docroot/sites/koettcra.cws.oregonstate.edu/settings.php deleted file mode 100644 index 7041062..0000000 --- a/docroot/sites/koettcra.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/koettcra_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/leadership.oregonstate.edu/settings.php b/docroot/sites/leadership.oregonstate.edu/settings.php deleted file mode 100644 index c1fecdc..0000000 --- a/docroot/sites/leadership.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/leadership_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/leighr.cws.oregonstate.edu/settings.php b/docroot/sites/leighr.cws.oregonstate.edu/settings.php deleted file mode 100644 index c6081d2..0000000 --- a/docroot/sites/leighr.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/leighr_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/lpitest.cws.oregonstate.edu/settings.php b/docroot/sites/lpitest.cws.oregonstate.edu/settings.php deleted file mode 100644 index 493cdbd..0000000 --- a/docroot/sites/lpitest.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/lpitest_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/lsamp.oregonstate.edu/settings.php b/docroot/sites/lsamp.oregonstate.edu/settings.php deleted file mode 100644 index ad8d58f..0000000 --- a/docroot/sites/lsamp.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/lsamp_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/maco.oregonstate.edu/settings.php b/docroot/sites/maco.oregonstate.edu/settings.php deleted file mode 100644 index 10d7d96..0000000 --- a/docroot/sites/maco.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/maco_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/marinestudies.oregonstate.edu/settings.php b/docroot/sites/marinestudies.oregonstate.edu/settings.php deleted file mode 100644 index db62547..0000000 --- a/docroot/sites/marinestudies.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/marinestudies_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/marterin.cws.oregonstate.edu/settings.php b/docroot/sites/marterin.cws.oregonstate.edu/settings.php deleted file mode 100644 index 62937e5..0000000 --- a/docroot/sites/marterin.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/marterin_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/mcqueenj.cws.oregonstate.edu/settings.php b/docroot/sites/mcqueenj.cws.oregonstate.edu/settings.php deleted file mode 100644 index 24cb847..0000000 --- a/docroot/sites/mcqueenj.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/mcqueenj_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/mediahub.oregonstate.edu/settings.php b/docroot/sites/mediahub.oregonstate.edu/settings.php deleted file mode 100644 index cbe78d6..0000000 --- a/docroot/sites/mediahub.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/mediahub_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/metrics.oregonstate.edu/settings.php b/docroot/sites/metrics.oregonstate.edu/settings.php deleted file mode 100644 index bb069e5..0000000 --- a/docroot/sites/metrics.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/metrics_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/millerga.cws.oregonstate.edu/settings.php b/docroot/sites/millerga.cws.oregonstate.edu/settings.php deleted file mode 100644 index 37a1c99..0000000 --- a/docroot/sites/millerga.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/millerga_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/mu.oregonstate.edu/settings.php b/docroot/sites/mu.oregonstate.edu/settings.php deleted file mode 100644 index 741ece4..0000000 --- a/docroot/sites/mu.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/mu_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/newstudents.oregonstate.edu/settings.php b/docroot/sites/newstudents.oregonstate.edu/settings.php deleted file mode 100644 index 3453be3..0000000 --- a/docroot/sites/newstudents.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/newstudents_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/occupationalhealth.oregonstate.edu/settings.php b/docroot/sites/occupationalhealth.oregonstate.edu/settings.php deleted file mode 100644 index 16b9482..0000000 --- a/docroot/sites/occupationalhealth.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/occupationalhealth_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/odegaarj.cws.oregonstate.edu/settings.php b/docroot/sites/odegaarj.cws.oregonstate.edu/settings.php deleted file mode 100644 index d62edfd..0000000 --- a/docroot/sites/odegaarj.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/odegaarj_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ohcc.oregonstate.edu/settings.php b/docroot/sites/ohcc.oregonstate.edu/settings.php deleted file mode 100644 index d8d2f49..0000000 --- a/docroot/sites/ohcc.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ohcc_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ombuds.oregonstate.edu/settings.php b/docroot/sites/ombuds.oregonstate.edu/settings.php deleted file mode 100644 index d7c3645..0000000 --- a/docroot/sites/ombuds.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ombuds_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/onid.oregonstate.edu/settings.php b/docroot/sites/onid.oregonstate.edu/settings.php deleted file mode 100644 index 6236b12..0000000 --- a/docroot/sites/onid.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/onid_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/oregonbroadbandequity.org/settings.php b/docroot/sites/oregonbroadbandequity.org/settings.php deleted file mode 100644 index eb2cf81..0000000 --- a/docroot/sites/oregonbroadbandequity.org/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/oregonbroadbandequity_org-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/oregoncoaststem.oregonstate.edu/settings.php b/docroot/sites/oregoncoaststem.oregonstate.edu/settings.php deleted file mode 100644 index 94c5daa..0000000 --- a/docroot/sites/oregoncoaststem.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/oregoncoaststem_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/oregongearup.org/settings.php b/docroot/sites/oregongearup.org/settings.php deleted file mode 100644 index 977eae0..0000000 --- a/docroot/sites/oregongearup.org/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/oregongearup_org-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/osucascades.edu/settings.php b/docroot/sites/osucascades.edu/settings.php deleted file mode 100644 index b19ad69..0000000 --- a/docroot/sites/osucascades.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/osucascades_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/osupc.oregonstate.edu/settings.php b/docroot/sites/osupc.oregonstate.edu/settings.php deleted file mode 100644 index b8dabad..0000000 --- a/docroot/sites/osupc.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/osupc_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/osura.oregonstate.edu/settings.php b/docroot/sites/osura.oregonstate.edu/settings.php deleted file mode 100644 index 08f637a..0000000 --- a/docroot/sites/osura.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/osura_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/outdooreconomy.oregonstate.edu/settings.php b/docroot/sites/outdooreconomy.oregonstate.edu/settings.php deleted file mode 100644 index 857bc49..0000000 --- a/docroot/sites/outdooreconomy.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/outdooreconomy_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/outdoorschool.oregonstate.edu/settings.php b/docroot/sites/outdoorschool.oregonstate.edu/settings.php deleted file mode 100644 index 18016cb..0000000 --- a/docroot/sites/outdoorschool.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/outdoorschool_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/partnerships.oregonstate.edu/settings.php b/docroot/sites/partnerships.oregonstate.edu/settings.php deleted file mode 100644 index 68de99b..0000000 --- a/docroot/sites/partnerships.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/partnerships_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/piscoweb.org/settings.php b/docroot/sites/piscoweb.org/settings.php deleted file mode 100644 index e6fd3fc..0000000 --- a/docroot/sites/piscoweb.org/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/piscoweb_org-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/pmec.oregonstate.edu/settings.php b/docroot/sites/pmec.oregonstate.edu/settings.php deleted file mode 100644 index efb4f76..0000000 --- a/docroot/sites/pmec.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/pmec_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/pnwcirc.org/settings.php b/docroot/sites/pnwcirc.org/settings.php deleted file mode 100644 index 79c9c29..0000000 --- a/docroot/sites/pnwcirc.org/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/pnwcirc_org-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/policy.oregonstate.edu/settings.php b/docroot/sites/policy.oregonstate.edu/settings.php deleted file mode 100644 index 8a8eb9e..0000000 --- a/docroot/sites/policy.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/policy_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/portland.oregonstate.edu/settings.php b/docroot/sites/portland.oregonstate.edu/settings.php deleted file mode 100644 index c76f894..0000000 --- a/docroot/sites/portland.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/portland_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/powwow.oregonstate.edu/settings.php b/docroot/sites/powwow.oregonstate.edu/settings.php deleted file mode 100644 index 1c401a2..0000000 --- a/docroot/sites/powwow.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/powwow_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/prax.oregonstate.edu/settings.php b/docroot/sites/prax.oregonstate.edu/settings.php deleted file mode 100644 index 9eca3ab..0000000 --- a/docroot/sites/prax.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/prax_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/precollege.oregonstate.edu/settings.php b/docroot/sites/precollege.oregonstate.edu/settings.php deleted file mode 100644 index 3124c70..0000000 --- a/docroot/sites/precollege.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/precollege_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/premed.oregonstate.edu/settings.php b/docroot/sites/premed.oregonstate.edu/settings.php deleted file mode 100644 index 71ce27b..0000000 --- a/docroot/sites/premed.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/premed_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/profiles.oregonstate.edu/settings.php b/docroot/sites/profiles.oregonstate.edu/settings.php deleted file mode 100644 index 311c620..0000000 --- a/docroot/sites/profiles.oregonstate.edu/settings.php +++ /dev/null @@ -1,908 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/profiles_oregonstate_edu-settings.inc'; - $config['automated_cron.settings']['interval'] = 0; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/publicsafety.oregonstate.edu/settings.php b/docroot/sites/publicsafety.oregonstate.edu/settings.php deleted file mode 100644 index f20150c..0000000 --- a/docroot/sites/publicsafety.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/publicsafety_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/recsports.oregonstate.edu/settings.php b/docroot/sites/recsports.oregonstate.edu/settings.php deleted file mode 100644 index f0009ab..0000000 --- a/docroot/sites/recsports.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/recsports_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/redseaweed.oregonstate.edu/settings.php b/docroot/sites/redseaweed.oregonstate.edu/settings.php deleted file mode 100644 index f57f72c..0000000 --- a/docroot/sites/redseaweed.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/redseaweed_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/registrar.oregonstate.edu/settings.php b/docroot/sites/registrar.oregonstate.edu/settings.php deleted file mode 100644 index 5295a14..0000000 --- a/docroot/sites/registrar.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/registrar_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/research.oregonstate.edu/settings.php b/docroot/sites/research.oregonstate.edu/settings.php deleted file mode 100644 index 1c140ec..0000000 --- a/docroot/sites/research.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/research_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/risk.oregonstate.edu/settings.php b/docroot/sites/risk.oregonstate.edu/settings.php deleted file mode 100644 index fd6cecd..0000000 --- a/docroot/sites/risk.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/risk_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/ruefa.cws.oregonstate.edu/settings.php b/docroot/sites/ruefa.cws.oregonstate.edu/settings.php deleted file mode 100644 index 23eeb90..0000000 --- a/docroot/sites/ruefa.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/ruefa_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/safety.oregonstate.edu/settings.php b/docroot/sites/safety.oregonstate.edu/settings.php deleted file mode 100644 index f2524d0..0000000 --- a/docroot/sites/safety.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/safety_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/sait.oregonstate.edu/settings.php b/docroot/sites/sait.oregonstate.edu/settings.php deleted file mode 100644 index 41d5b57..0000000 --- a/docroot/sites/sait.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/sait_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/sccs.oregonstate.edu/settings.php b/docroot/sites/sccs.oregonstate.edu/settings.php deleted file mode 100644 index 538f4f2..0000000 --- a/docroot/sites/sccs.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/sccs_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/scl.liberalarts.oregonstate.edu/settings.php b/docroot/sites/scl.liberalarts.oregonstate.edu/settings.php deleted file mode 100644 index 88d7170..0000000 --- a/docroot/sites/scl.liberalarts.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/scl_liberalarts_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/seagrant.oregonstate.edu/settings.php b/docroot/sites/seagrant.oregonstate.edu/settings.php deleted file mode 100644 index 946365f..0000000 --- a/docroot/sites/seagrant.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/seagrant_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/searchadvocate.oregonstate.edu/settings.php b/docroot/sites/searchadvocate.oregonstate.edu/settings.php deleted file mode 100644 index 031ca7a..0000000 --- a/docroot/sites/searchadvocate.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/searchadvocate_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/security.oregonstate.edu/settings.php b/docroot/sites/security.oregonstate.edu/settings.php deleted file mode 100644 index c1c2a05..0000000 --- a/docroot/sites/security.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/security_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/see.oregonstate.edu/settings.php b/docroot/sites/see.oregonstate.edu/settings.php deleted file mode 100644 index 597b91a..0000000 --- a/docroot/sites/see.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/see_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/seedlab.oregonstate.edu/settings.php b/docroot/sites/seedlab.oregonstate.edu/settings.php deleted file mode 100644 index 242d3f1..0000000 --- a/docroot/sites/seedlab.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/seedlab_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/semiconductor.oregonstate.edu/settings.php b/docroot/sites/semiconductor.oregonstate.edu/settings.php deleted file mode 100644 index 6e51db7..0000000 --- a/docroot/sites/semiconductor.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/semiconductor_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/smile.oregonstate.edu/settings.php b/docroot/sites/smile.oregonstate.edu/settings.php deleted file mode 100644 index 22a0d11..0000000 --- a/docroot/sites/smile.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/smile_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/stemacademy.oregonstate.edu/settings.php b/docroot/sites/stemacademy.oregonstate.edu/settings.php deleted file mode 100644 index 54e5ed0..0000000 --- a/docroot/sites/stemacademy.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/stemacademy_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/studentathlete.oregonstate.edu/settings.php b/docroot/sites/studentathlete.oregonstate.edu/settings.php deleted file mode 100644 index cc3de45..0000000 --- a/docroot/sites/studentathlete.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/studentathlete_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/studenthealth.oregonstate.edu/settings.php b/docroot/sites/studenthealth.oregonstate.edu/settings.php deleted file mode 100644 index 0f671cc..0000000 --- a/docroot/sites/studenthealth.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/studenthealth_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/success.oregonstate.edu/settings.php b/docroot/sites/success.oregonstate.edu/settings.php deleted file mode 100644 index 529e647..0000000 --- a/docroot/sites/success.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/success_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/summer.oregonstate.edu/settings.php b/docroot/sites/summer.oregonstate.edu/settings.php deleted file mode 100644 index 684d306..0000000 --- a/docroot/sites/summer.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/summer_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/sunto.cws.oregonstate.edu/settings.php b/docroot/sites/sunto.cws.oregonstate.edu/settings.php deleted file mode 100644 index 97f4a52..0000000 --- a/docroot/sites/sunto.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/sunto_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/teach.oregonstate.edu/settings.php b/docroot/sites/teach.oregonstate.edu/settings.php deleted file mode 100644 index ca906cc..0000000 --- a/docroot/sites/teach.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/teach_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/technology.oregonstate.edu/settings.php b/docroot/sites/technology.oregonstate.edu/settings.php deleted file mode 100644 index d5e11a9..0000000 --- a/docroot/sites/technology.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/technology_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/thomajam.cws.oregonstate.edu/settings.php b/docroot/sites/thomajam.cws.oregonstate.edu/settings.php deleted file mode 100644 index c0a0357..0000000 --- a/docroot/sites/thomajam.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/thomajam_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/topscholars.oregonstate.edu/settings.php b/docroot/sites/topscholars.oregonstate.edu/settings.php deleted file mode 100644 index 92cdb99..0000000 --- a/docroot/sites/topscholars.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/topscholars_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/training.oregonstate.edu/settings.php b/docroot/sites/training.oregonstate.edu/settings.php deleted file mode 100644 index 9610c26..0000000 --- a/docroot/sites/training.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/training_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/transboundarywaters.ceoas.oregonstate.edu/settings.php b/docroot/sites/transboundarywaters.ceoas.oregonstate.edu/settings.php deleted file mode 100644 index 6cfd55e..0000000 --- a/docroot/sites/transboundarywaters.ceoas.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/transboundarywaters_ceoas_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/transportation.oregonstate.edu/settings.php b/docroot/sites/transportation.oregonstate.edu/settings.php deleted file mode 100644 index 7ba1616..0000000 --- a/docroot/sites/transportation.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/transportation_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/trio.oregonstate.edu/settings.php b/docroot/sites/trio.oregonstate.edu/settings.php deleted file mode 100644 index ab7a771..0000000 --- a/docroot/sites/trio.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/trio_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/uesp.oregonstate.edu/settings.php b/docroot/sites/uesp.oregonstate.edu/settings.php deleted file mode 100644 index affdd46..0000000 --- a/docroot/sites/uesp.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/uesp_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/uhds.oregonstate.edu/settings.php b/docroot/sites/uhds.oregonstate.edu/settings.php deleted file mode 100644 index eeaf5ea..0000000 --- a/docroot/sites/uhds.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/uhds_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/uit.oregonstate.edu/settings.php b/docroot/sites/uit.oregonstate.edu/settings.php deleted file mode 100644 index 113dd56..0000000 --- a/docroot/sites/uit.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/uit_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/vannormk.cws.oregonstate.edu/settings.php b/docroot/sites/vannormk.cws.oregonstate.edu/settings.php deleted file mode 100644 index 9a49056..0000000 --- a/docroot/sites/vannormk.cws.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/vannormk_cws_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/veterans.oregonstate.edu/settings.php b/docroot/sites/veterans.oregonstate.edu/settings.php deleted file mode 100644 index c028ee8..0000000 --- a/docroot/sites/veterans.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/veterans_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/vetmed.oregonstate.edu/settings.php b/docroot/sites/vetmed.oregonstate.edu/settings.php deleted file mode 100644 index 93ec98a..0000000 --- a/docroot/sites/vetmed.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/vetmed_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/visitosu.oregonstate.edu/settings.php b/docroot/sites/visitosu.oregonstate.edu/settings.php deleted file mode 100644 index 0711ecc..0000000 --- a/docroot/sites/visitosu.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/visitosu_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/welcome.oregonstate.edu/settings.php b/docroot/sites/welcome.oregonstate.edu/settings.php deleted file mode 100644 index 02c3edb..0000000 --- a/docroot/sites/welcome.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/welcome_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/wellnessnook.oregonstate.edu/settings.php b/docroot/sites/wellnessnook.oregonstate.edu/settings.php deleted file mode 100644 index 53201af..0000000 --- a/docroot/sites/wellnessnook.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/wellnessnook_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/wellwater.oregonstate.edu/settings.php b/docroot/sites/wellwater.oregonstate.edu/settings.php deleted file mode 100644 index 0876076..0000000 --- a/docroot/sites/wellwater.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/wellwater_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/wic.oregonstate.edu/settings.php b/docroot/sites/wic.oregonstate.edu/settings.php deleted file mode 100644 index 7349ea6..0000000 --- a/docroot/sites/wic.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/wic_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -} diff --git a/docroot/sites/yourpath.oregonstate.edu/settings.php b/docroot/sites/yourpath.oregonstate.edu/settings.php deleted file mode 100644 index 1cf7b27..0000000 --- a/docroot/sites/yourpath.oregonstate.edu/settings.php +++ /dev/null @@ -1,907 +0,0 @@ - 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'port' => '3306', - * 'driver' => 'mysql', - * 'prefix' => '', - * 'collation' => 'utf8mb4_general_ci', - * ]; - * @endcode - */ -$databases = []; - -/** - * Customizing database settings. - * - * Many of the values of the $databases array can be customized for your - * particular database system. Refer to the sample in the section above as a - * starting point. - * - * The "driver" property indicates what Drupal database driver the - * connection should use. This is usually the same as the name of the - * database type, such as mysql or sqlite, but not always. The other - * properties will vary depending on the driver. For SQLite, you must - * specify a database file name in a directory that is writable by the - * webserver. For most other drivers, you must specify a - * username, password, host, and database name. - * - * Drupal core implements drivers for mysql, pgsql, and sqlite. Other drivers - * can be provided by contributed or custom modules. To use a contributed or - * custom driver, the "namespace" property must be set to the namespace of the - * driver. The code in this namespace must be autoloadable prior to connecting - * to the database, and therefore, prior to when module root namespaces are - * added to the autoloader. To add the driver's namespace to the autoloader, - * set the "autoload" property to the PSR-4 base directory of the driver's - * namespace. This is optional for projects managed with Composer if the - * driver's namespace is in Composer's autoloader. - * - * For each database, you may optionally specify multiple "target" databases. - * A target database allows Drupal to try to send certain queries to a - * different database if it can but fall back to the default connection if not. - * That is useful for primary/replica replication, as Drupal may try to connect - * to a replica server when appropriate and if one is not available will simply - * fall back to the single primary server (The terms primary/replica are - * traditionally referred to as master/slave in database server documentation). - * - * The general format for the $databases array is as follows: - * @code - * $databases['default']['default'] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['default']['replica'][] = $info_array; - * $databases['extra']['default'] = $info_array; - * @endcode - * - * In the above example, $info_array is an array of settings described above. - * The first line sets a "default" database that has one primary database - * (the second level default). The second and third lines create an array - * of potential replica databases. Drupal will select one at random for a given - * request as needed. The fourth line creates a new database with a name of - * "extra". - * - * For MySQL, MariaDB or equivalent databases the 'isolation_level' option can - * be set. The recommended transaction isolation level for Drupal sites is - * 'READ COMMITTED'. The 'REPEATABLE READ' option is supported but can result - * in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'. - * They are available but not supported; use them at your own risk. For more - * info: - * https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html - * - * On your settings.php, change the isolation level: - * @code - * $databases['default']['default']['init_commands'] = [ - * 'isolation_level' => 'SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED', - * ]; - * @endcode - * - * You can optionally set a prefix for all database table names by using the - * 'prefix' setting. If a prefix is specified, the table name will be prepended - * with its value. Be sure to use valid database characters only, usually - * alphanumeric and underscore. If no prefix is desired, do not set the 'prefix' - * key or set its value to an empty string ''. - * - * For example, to have all database table prefixed with 'main_', set: - * @code - * 'prefix' => 'main_', - * @endcode - * - * Advanced users can add or override initial commands to execute when - * connecting to the database server, as well as PDO connection settings. For - * example, to enable MySQL SELECT queries to exceed the max_join_size system - * variable, and to reduce the database connection timeout to 5 seconds: - * @code - * $databases['default']['default'] = [ - * 'init_commands' => [ - * 'big_selects' => 'SET SQL_BIG_SELECTS=1', - * ], - * 'pdo' => [ - * PDO::ATTR_TIMEOUT => 5, - * ], - * ]; - * @endcode - * - * WARNING: The above defaults are designed for database portability. Changing - * them may cause unexpected behavior, including potential data loss. See - * https://www.drupal.org/developing/api/database/configuration for more - * information on these defaults and the potential issues. - * - * More details can be found in the constructor methods for each driver: - * - \Drupal\mysql\Driver\Database\mysql\Connection::__construct() - * - \Drupal\pgsql\Driver\Database\pgsql\Connection::__construct() - * - \Drupal\sqlite\Driver\Database\sqlite\Connection::__construct() - * - * Sample Database configuration format for PostgreSQL (pgsql): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'pgsql', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for SQLite (sqlite): - * @code - * $databases['default']['default'] = [ - * 'driver' => 'sqlite', - * 'database' => '/path/to/database_filename', - * ]; - * @endcode - * - * Sample Database configuration format for a driver in a contributed module: - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * ]; - * @endcode - * - * Sample Database configuration format for a driver that is extending another - * database driver. - * @code - * $databases['default']['default'] = [ - * 'driver' => 'my_driver', - * 'namespace' => 'Drupal\my_module\Driver\Database\my_driver', - * 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/', - * 'database' => 'databasename', - * 'username' => 'sql_username', - * 'password' => 'sql_password', - * 'host' => 'localhost', - * 'prefix' => '', - * 'dependencies' => [ - * 'parent_module' => [ - * 'namespace' => 'Drupal\parent_module', - * 'autoload' => 'core/modules/parent_module/src/', - * ], - * ], - * ]; - * @endcode - */ - -/** - * Location of the site configuration files. - * - * The $settings['config_sync_directory'] specifies the location of file system - * directory used for syncing configuration data. On install, the directory is - * created. This is used for configuration imports. - * - * The default location for this directory is inside a randomly-named - * directory in the public files path. The setting below allows you to set - * its location. - */ -# $settings['config_sync_directory'] = '/directory/outside/webroot'; - -/** - * Settings: - * - * $settings contains environment-specific configuration, such as the files - * directory and reverse proxy address, and temporary configuration, such as - * security overrides. - * - * @see \Drupal\Core\Site\Settings::get() - */ - -/** - * Salt for one-time login links, cancel links, form tokens, etc. - * - * This variable will be set to a random value by the installer. All one-time - * login links will be invalidated if the value is changed. Note that if your - * site is deployed on a cluster of web servers, you must ensure that this - * variable has the same value on each server. - * - * For enhanced security, you may set this variable to the contents of a file - * outside your document root, and vary the value across environments (like - * production and development); you should also ensure that this file is not - * stored with backups of your database. - * - * Example: - * @code - * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt'); - * @endcode - */ -$settings['hash_salt'] = ''; - -/** - * Deployment identifier. - * - * Drupal's dependency injection container will be automatically invalidated and - * rebuilt when the Drupal core version changes. When updating contributed or - * custom code that changes the container, changing this identifier will also - * allow the container to be invalidated as soon as code is deployed. - */ -# $settings['deployment_identifier'] = \Drupal::VERSION; - -/** - * Access control for update.php script. - * - * If you are updating your Drupal installation using the update.php script but - * are not logged in using either an account with the "Administer software - * updates" permission or the site maintenance account (the account that was - * created during installation), you will need to modify the access check - * statement below. Change the FALSE to a TRUE to disable the access check. - * After finishing the upgrade, be sure to open this file again and change the - * TRUE back to a FALSE! - */ -$settings['update_free_access'] = FALSE; - -/** - * Fallback to HTTP for Update Manager and for fetching security advisories. - * - * If your site fails to connect to updates.drupal.org over HTTPS (either when - * fetching data on available updates, or when fetching the feed of critical - * security announcements), you may uncomment this setting and set it to TRUE to - * allow an insecure fallback to HTTP. Note that doing so will open your site up - * to a potential man-in-the-middle attack. You should instead attempt to - * resolve the issues before enabling this option. - * @see https://www.drupal.org/docs/system-requirements/php-requirements#openssl - * @see https://en.wikipedia.org/wiki/Man-in-the-middle_attack - * @see \Drupal\update\UpdateFetcher - * @see \Drupal\system\SecurityAdvisories\SecurityAdvisoriesFetcher - */ -# $settings['update_fetch_with_http_fallback'] = TRUE; - -/** - * External access proxy settings: - * - * If your site must access the Internet via a web proxy then you can enter the - * proxy settings here. Set the full URL of the proxy, including the port, in - * variables: - * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP - * requests. - * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS - * requests. - * You can pass in the user name and password for basic authentication in the - * URLs in these settings. - * - * You can also define an array of host names that can be accessed directly, - * bypassing the proxy, in $settings['http_client_config']['proxy']['no']. - */ -# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080'; -# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost']; - -/** - * Reverse Proxy Configuration: - * - * Reverse proxy servers are often used to enhance the performance - * of heavily visited sites and may also provide other site caching, - * security, or encryption benefits. In an environment where Drupal - * is behind a reverse proxy, the real IP address of the client should - * be determined such that the correct client IP address is available - * to Drupal's logging, statistics, and access management systems. In - * the most simple scenario, the proxy server will add an - * X-Forwarded-For header to the request that contains the client IP - * address. However, HTTP headers are vulnerable to spoofing, where a - * malicious client could bypass restrictions by setting the - * X-Forwarded-For header directly. Therefore, Drupal's proxy - * configuration requires the IP addresses of all remote proxies to be - * specified in $settings['reverse_proxy_addresses'] to work correctly. - * - * Enable this setting to get Drupal to determine the client IP from the - * X-Forwarded-For header. If you are unsure about this setting, do not have a - * reverse proxy, or Drupal operates in a shared hosting environment, this - * setting should remain commented out. - * - * In order for this setting to be used you must specify every possible - * reverse proxy IP address in $settings['reverse_proxy_addresses']. - * If a complete list of reverse proxies is not available in your - * environment (for example, if you use a CDN) you may set the - * $_SERVER['REMOTE_ADDR'] variable directly in settings.php. - * Be aware, however, that it is likely that this would allow IP - * address spoofing unless more advanced precautions are taken. - */ -# $settings['reverse_proxy'] = TRUE; - -/** - * Reverse proxy addresses. - * - * Specify every reverse proxy IP address in your environment, as an array of - * IPv4/IPv6 addresses or subnets in CIDR notation. This setting is required if - * $settings['reverse_proxy'] is TRUE. - */ -# $settings['reverse_proxy_addresses'] = ['a.b.c.d', 'e.f.g.h/24', ...]; - -/** - * Reverse proxy trusted headers. - * - * Sets which headers to trust from your reverse proxy. - * - * Common values are: - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * - \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * - \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * - * Note the default value of - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @endcode - * is not secure by default. The value should be set to only the specific - * headers the reverse proxy uses. For example: - * @code - * \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @endcode - * This would trust the following headers: - * - X_FORWARDED_FOR - * - X_FORWARDED_HOST - * - X_FORWARDED_PROTO - * - X_FORWARDED_PORT - * - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT - * @see \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO - * @see \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED - * @see \Symfony\Component\HttpFoundation\Request::setTrustedProxies - */ -# $settings['reverse_proxy_trusted_headers'] = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_HOST | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_FORWARDED; - - -/** - * Page caching: - * - * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page - * views. This tells a HTTP proxy that it may return a page from its local - * cache without contacting the web server, if the user sends the same Cookie - * header as the user who originally requested the cached page. Without "Vary: - * Cookie", authenticated users would also be served the anonymous page from - * the cache. If the site has mostly anonymous users except a few known - * editors/administrators, the Vary header can be omitted. This allows for - * better caching in HTTP proxies (including reverse proxies), i.e. even if - * clients send different cookies, they still get content served from the cache. - * However, authenticated users should access the site directly (i.e. not use an - * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid - * getting cached pages from the proxy. - */ -# $settings['omit_vary_cookie'] = TRUE; - - -/** - * Cache TTL for client error (4xx) responses. - * - * Items cached per-URL tend to result in a large number of cache items, and - * this can be problematic on 404 pages which by their nature are unbounded. A - * fixed TTL can be set for these items, defaulting to one hour, so that cache - * backends which do not support LRU can purge older entries. To disable caching - * of client error responses set the value to 0. Currently applies only to - * page_cache module. - */ -# $settings['cache_ttl_4xx'] = 3600; - -/** - * Expiration of cached forms. - * - * Drupal's Form API stores details of forms in a cache and these entries are - * kept for at least 6 hours by default. Expired entries are cleared by cron. - * - * @see \Drupal\Core\Form\FormCache::setCache() - */ -# $settings['form_cache_expiration'] = 21600; - -/** - * Class Loader. - * - * If the APCu extension is detected, the classloader will be optimized to use - * it. Set to FALSE to disable this. - * - * @see https://getcomposer.org/doc/articles/autoloader-optimization.md - */ -# $settings['class_loader_auto_detect'] = FALSE; - -/** - * Authorized file system operations: - * - * The Update Manager module included with Drupal provides a mechanism for - * site administrators to securely install missing updates for the site - * directly through the web user interface. On securely-configured servers, - * the Update manager will require the administrator to provide SSH or FTP - * credentials before allowing the installation to proceed; this allows the - * site to update the new files as the user who owns all the Drupal files, - * instead of as the user the webserver is running as. On servers where the - * webserver user is itself the owner of the Drupal files, the administrator - * will not be prompted for SSH or FTP credentials (note that these server - * setups are common on shared hosting, but are inherently insecure). - * - * Some sites might wish to disable the above functionality, and only update - * the code directly via SSH or FTP themselves. This setting completely - * disables all functionality related to these authorized file operations. - * - * @see https://www.drupal.org/node/244924 - * - * Remove the leading hash signs to disable. - */ -# $settings['allow_authorize_operations'] = FALSE; - -/** - * Default mode for directories and files written by Drupal. - * - * Value should be in PHP Octal Notation, with leading zero. - */ -# $settings['file_chmod_directory'] = 0775; -# $settings['file_chmod_file'] = 0664; - -/** - * Optimized assets path: - * - * A local file system path where optimized assets will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_assets_path'] = 'sites/default/files'; - -/** - * Public file base URL: - * - * An alternative base URL to be used for serving public files. This must - * include any leading directory path. - * - * A different value from the domain used by Drupal to be used for accessing - * public files. This can be used for a simple CDN integration, or to improve - * security by serving user-uploaded files from a different domain or subdomain - * pointing to the same server. Do not include a trailing slash. - */ -# $settings['file_public_base_url'] = 'http://downloads.example.com/files'; - -/** - * Public file path: - * - * A local file system path where public files will be stored. This directory - * must exist and be writable by Drupal. This directory must be relative to - * the Drupal installation directory and be accessible over the web. - */ -# $settings['file_public_path'] = 'sites/default/files'; - -/** - * Additional public file schemes: - * - * Public schemes are URI schemes that allow download access to all users for - * all files within that scheme. - * - * The "public" scheme is always public, and the "private" scheme is always - * private, but other schemes, such as "https", "s3", "example", or others, - * can be either public or private depending on the site. By default, they're - * private, and access to individual files is controlled via - * hook_file_download(). - * - * Typically, if a scheme should be public, a module makes it public by - * implementing hook_file_download(), and granting access to all users for all - * files. This could be either the same module that provides the stream wrapper - * for the scheme, or a different module that decides to make the scheme - * public. However, in cases where a site needs to make a scheme public, but - * is unable to add code in a module to do so, the scheme may be added to this - * variable, the result of which is that system_file_download() grants public - * access to all files within that scheme. - */ -# $settings['file_additional_public_schemes'] = ['example']; - -/** - * File schemes whose paths should not be normalized: - * - * Normally, Drupal normalizes '/./' and '/../' segments in file URIs in order - * to prevent unintended file access. For example, 'private://css/../image.png' - * is normalized to 'private://image.png' before checking access to the file. - * - * On Windows, Drupal also replaces '\' with '/' in URIs for the local - * filesystem. - * - * If file URIs with one or more scheme should not be normalized like this, then - * list the schemes here. For example, if 'porcelain://china/./plate.png' should - * not be normalized to 'porcelain://china/plate.png', then add 'porcelain' to - * this array. In this case, make sure that the module providing the 'porcelain' - * scheme does not allow unintended file access when using '/../' to move up the - * directory tree. - */ -# $settings['file_sa_core_2023_005_schemes'] = ['porcelain']; - -/** - * Configuration for phpinfo() admin status report. - * - * Drupal's admin UI includes a report at admin/reports/status/php which shows - * the output of phpinfo(). The full output can contain sensitive information - * so by default Drupal removes some sections. - * - * This behavior can be configured by setting this variable to a different - * value corresponding to the flags parameter of phpinfo(). - * - * If you need to expose more information in the report - for example to debug a - * problem - consider doing so temporarily. - * - * @see https://www.php.net/manual/function.phpinfo.php - */ -# $settings['sa_core_2023_004_phpinfo_flags'] = ~ (INFO_VARIABLES | INFO_ENVIRONMENT); - -/** - * Private file path: - * - * A local file system path where private files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * Note: Caches need to be cleared when this value is changed to make the - * private:// stream wrapper available to the system. - * - * See https://www.drupal.org/documentation/modules/file for more information - * about securing private files. - */ -# $settings['file_private_path'] = ''; - -/** - * Temporary file path: - * - * A local file system path where temporary files will be stored. This directory - * must be absolute, outside of the Drupal installation directory and not - * accessible over the web. - * - * If this is not set, the default for the operating system will be used. - * - * @see \Drupal\Component\FileSystem\FileSystem::getOsTemporaryDirectory() - */ -# $settings['file_temp_path'] = '/tmp'; - -/** - * Session write interval: - * - * Set the minimum interval between each session write to database. - * For performance reasons it defaults to 180. - */ -# $settings['session_write_interval'] = 180; - -/** - * String overrides: - * - * To override specific strings on your site with or without enabling the Locale - * module, add an entry to this list. This functionality allows you to change - * a small number of your site's default English language interface strings. - * - * Remove the leading hash signs to enable. - * - * The "en" part of the variable name, is dynamic and can be any langcode of - * any added language. (eg locale_custom_strings_de for german). - */ -# $settings['locale_custom_strings_en'][''] = [ -# 'Home' => 'Front page', -# '@count min' => '@count minutes', -# ]; - -/** - * A custom theme for the offline page: - * - * This applies when the site is explicitly set to maintenance mode through the - * administration page or when the database is inactive due to an error. - * The template file should also be copied into the theme. It is located inside - * 'core/modules/system/templates/maintenance-page.html.twig'. - * - * Note: This setting does not apply to installation and update pages. - */ -# $settings['maintenance_theme'] = 'claro'; - -/** - * PHP settings: - * - * To see what PHP settings are possible, including whether they can be set at - * runtime (by using ini_set()), read the PHP documentation: - * http://php.net/manual/ini.list.php - * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime - * settings and the .htaccess file for non-runtime settings. - * Settings defined there should not be duplicated here so as to avoid conflict - * issues. - */ - -/** - * If you encounter a situation where users post a large amount of text, and - * the result is stripped out upon viewing but can still be edited, Drupal's - * output filter may not have sufficient memory to process it. If you - * experience this issue, you may wish to uncomment the following two lines - * and increase the limits of these variables. For more information, see - * http://php.net/manual/pcre.configuration.php. - */ -# ini_set('pcre.backtrack_limit', 200000); -# ini_set('pcre.recursion_limit', 200000); - -/** - * Configuration overrides. - * - * To globally override specific configuration values for this site, - * set them here. You usually don't need to use this feature. This is - * useful in a configuration file for a vhost or directory, rather than - * the default settings.php. - * - * Note that any values you provide in these variable overrides will not be - * viewable from the Drupal administration interface. The administration - * interface displays the values stored in configuration so that you can stage - * changes to other environments that don't have the overrides. - * - * There are particular configuration values that are risky to override. For - * example, overriding the list of installed modules in 'core.extension' is not - * supported as module install or uninstall has not occurred. Other examples - * include field storage configuration, because it has effects on database - * structure, and 'core.menu.static_menu_link_overrides' since this is cached in - * a way that is not config override aware. Also, note that changing - * configuration values in settings.php will not fire any of the configuration - * change events. - */ -# $config['system.site']['name'] = 'My Drupal site'; -# $config['user.settings']['anonymous'] = 'Visitor'; - -/** - * Load services definition file. - */ -$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml'; - -/** - * Override the default service container class. - * - * This is useful for example to trace the service container for performance - * tracking purposes, for testing a service container with an error condition or - * to test a service container that throws an exception. - */ -# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container'; - -/** - * Override the default yaml parser class. - * - * Provide a fully qualified class name here if you would like to provide an - * alternate implementation YAML parser. The class must implement the - * \Drupal\Component\Serialization\SerializationInterface interface. - */ -# $settings['yaml_parser_class'] = NULL; - -/** - * Trusted host configuration. - * - * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host - * header spoofing. - * - * To enable the trusted host mechanism, you enable your allowable hosts - * in $settings['trusted_host_patterns']. This should be an array of regular - * expression patterns, without delimiters, representing the hosts you would - * like to allow. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^www\.example\.com$', - * ]; - * @endcode - * will allow the site to only run from www.example.com. - * - * If you are running multisite, or if you are running your site from - * different domain names (eg, you don't redirect http://www.example.com to - * http://example.com), you should specify all of the host patterns that are - * allowed by your site. - * - * For example: - * @code - * $settings['trusted_host_patterns'] = [ - * '^example\.com$', - * '^.+\.example\.com$', - * '^example\.org$', - * '^.+\.example\.org$', - * ]; - * @endcode - * will allow the site to run off of all variants of example.com and - * example.org, with all subdomains included. - * - * @see https://www.drupal.org/docs/installing-drupal/trusted-host-settings - */ -# $settings['trusted_host_patterns'] = []; - -/** - * The default list of directories that will be ignored by Drupal's file API. - * - * By default ignore node_modules and bower_components folders to avoid issues - * with common frontend tools and recursive scanning of directories looking for - * extensions. - * - * @see \Drupal\Core\File\FileSystemInterface::scanDirectory() - * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory() - */ -$settings['file_scan_ignore_directories'] = [ - 'node_modules', - 'bower_components', -]; - -/** - * The default number of entities to update in a batch process. - * - * This is used by update and post-update functions that need to go through and - * change all the entities on a site, so it is useful to increase this number - * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a - * larger number of entities to be processed in a single batch run. - */ -$settings['entity_update_batch_size'] = 50; - -/** - * Entity update backup. - * - * This is used to inform the entity storage handler that the backup tables as - * well as the original entity type and field storage definitions should be - * retained after a successful entity update process. - */ -$settings['entity_update_backup'] = TRUE; - -/** - * Node migration type. - * - * This is used to force the migration system to use the classic node migrations - * instead of the default complete node migrations. The migration system will - * use the classic node migration only if there are existing migrate_map tables - * for the classic node migrations and they contain data. These tables may not - * exist if you are developing custom migrations and do not want to use the - * complete node migrations. Set this to TRUE to force the use of the classic - * node migrations. - */ -$settings['migrate_node_migrate_type_classic'] = FALSE; - -/** - * The default settings for migration sources. - * - * These settings are used as the default settings on the Credential form at - * /upgrade/credentials. - * - * - migrate_source_version - The version of the source database. This can be - * '6' or '7'. Defaults to '7'. - * - migrate_source_connection - The key in the $databases array for the source - * site. - * - migrate_file_public_path - The location of the source Drupal 6 or Drupal 7 - * public files. This can be a local file directory containing the source - * Drupal 6 or Drupal 7 site (e.g /var/www/docroot), or the site address - * (e.g http://example.com). - * - migrate_file_private_path - The location of the source Drupal 7 private - * files. This can be a local file directory containing the source Drupal 7 - * site (e.g /var/www/docroot), or empty to use the same value as Public - * files directory. - * - * Sample configuration for a drupal 6 source site with the source files in a - * local directory. - * - * @code - * $settings['migrate_source_version'] = '6'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = '/var/www/drupal6'; - * @endcode - * - * Sample configuration for a drupal 7 source site with public source files on - * the source site and the private files in a local directory. - * - * @code - * $settings['migrate_source_version'] = '7'; - * $settings['migrate_source_connection'] = 'migrate'; - * $settings['migrate_file_public_path'] = 'https://drupal7.com'; - * $settings['migrate_file_private_path'] = '/var/www/drupal7'; - * @endcode - */ -# $settings['migrate_source_connection'] = ''; -# $settings['migrate_source_version'] = ''; -# $settings['migrate_file_public_path'] = ''; -# $settings['migrate_file_private_path'] = ''; - -/** - * Load local development override configuration, if available. - * - * Create a settings.local.php file to override variables on secondary (staging, - * development, etc.) installations of this site. - * - * Typical uses of settings.local.php include: - * - Disabling caching. - * - Disabling JavaScript/CSS compression. - * - Rerouting outgoing emails. - * - * Keep this code block at the end of this file to take full effect. - */ - -if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) { - include $app_root . '/' . $site_path . '/settings.local.php'; -} -// Newrelic Multisite -if (extension_loaded('newrelic')) { - $exploded_path = explode('/', dirname(__FILE__)); - $site_domain = array_pop($exploded_path); - newrelic_set_appname("$site_domain;d8cws", '', 'true'); -} -// Acquia specific settings. -if (file_exists('/var/www/site-php')) { - require '/var/www/site-php/' . $_ENV['AH_SITE_GROUP'] . '/yourpath_oregonstate_edu-settings.inc'; - if (isset($_ENV['AH_SITE_ENVIRONMENT'])) { - $settings['file_temp_path'] = "/mnt/gfs/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/tmp"; - $settings['file_private_path'] = '/mnt/files/' . $_ENV['AH_SITE_GROUP'] . '.' . $_ENV['AH_SITE_ENVIRONMENT'] . '/' . $site_path . '/files-private'; - } - // Acquia cloud secrets file. - $secrets_file = "/mnt/files/{$_ENV['AH_SITE_GROUP']}.{$_ENV['AH_SITE_ENVIRONMENT']}/secrets.settings.php"; - if (file_exists($secrets_file)) { - require $secrets_file; - } - // Memcached settings for Acquia Hosting - $memcache_settings_file = DRUPAL_ROOT . "/../vendor/acquia/memcache-settings/memcache.settings.php"; - if (file_exists($memcache_settings_file)) { - require_once $memcache_settings_file; - } -}