webmaster@1: 'main_', webmaster@1: * 'users' => 'shared_', webmaster@1: * 'sessions' => 'shared_', webmaster@1: * 'role' => 'shared_', webmaster@1: * 'authmap' => 'shared_', webmaster@1: * ); webmaster@1: * webmaster@1: * Database URL format: webmaster@1: * $db_url = 'mysql://username:password@localhost/databasename'; webmaster@1: * $db_url = 'mysqli://username:password@localhost/databasename'; webmaster@1: * $db_url = 'pgsql://username:password@localhost/databasename'; webmaster@1: */ webmaster@1: $db_url = 'mysql://username:password@localhost/databasename'; webmaster@1: $db_prefix = ''; webmaster@1: webmaster@1: /** webmaster@1: * Access control for update.php script webmaster@1: * webmaster@1: * If you are updating your Drupal installation using the update.php script webmaster@1: * being not logged in as administrator, you will need to modify the access webmaster@1: * check statement below. Change the FALSE to a TRUE to disable the access webmaster@1: * check. After finishing the upgrade, be sure to open this file again webmaster@1: * and change the TRUE back to a FALSE! webmaster@1: */ webmaster@1: $update_free_access = FALSE; webmaster@1: webmaster@1: /** webmaster@1: * Base URL (optional). webmaster@1: * webmaster@1: * If you are experiencing issues with different site domains, webmaster@1: * uncomment the Base URL statement below (remove the leading hash sign) webmaster@1: * and fill in the URL to your Drupal installation. webmaster@1: * webmaster@1: * You might also want to force users to use a given domain. webmaster@1: * See the .htaccess file for more information. webmaster@1: * webmaster@1: * Examples: webmaster@1: * $base_url = 'http://www.example.com'; webmaster@1: * $base_url = 'http://www.example.com:8888'; webmaster@1: * $base_url = 'http://www.example.com/drupal'; webmaster@1: * $base_url = 'https://www.example.com:8888/drupal'; webmaster@1: * webmaster@1: * It is not allowed to have a trailing slash; Drupal will add it webmaster@1: * for you. webmaster@1: */ webmaster@1: # $base_url = 'http://www.example.com'; // NO trailing slash! webmaster@1: webmaster@1: /** webmaster@1: * PHP settings: webmaster@1: * webmaster@1: * To see what PHP settings are possible, including whether they can webmaster@1: * be set at runtime (ie., when ini_set() occurs), read the PHP webmaster@1: * documentation at http://www.php.net/manual/en/ini.php#ini.list webmaster@1: * and take a look at the .htaccess file to see which non-runtime webmaster@1: * settings are used there. Settings defined here should not be webmaster@1: * duplicated there so as to avoid conflict issues. webmaster@1: */ webmaster@1: ini_set('arg_separator.output', '&'); webmaster@1: ini_set('magic_quotes_runtime', 0); webmaster@1: ini_set('magic_quotes_sybase', 0); webmaster@1: ini_set('session.cache_expire', 200000); webmaster@1: ini_set('session.cache_limiter', 'none'); webmaster@1: ini_set('session.cookie_lifetime', 2000000); webmaster@1: ini_set('session.gc_maxlifetime', 200000); webmaster@1: ini_set('session.save_handler', 'user'); webmaster@1: ini_set('session.use_only_cookies', 1); webmaster@1: ini_set('session.use_trans_sid', 0); webmaster@1: ini_set('url_rewriter.tags', ''); webmaster@1: webmaster@1: /** webmaster@1: * Drupal automatically generates a unique session cookie name for each site webmaster@1: * based on on its full domain name. If you have multiple domains pointing at webmaster@1: * the same Drupal site, you can either redirect them all to a single domain webmaster@1: * (see comment in .htaccess), or uncomment the line below and specify their webmaster@1: * shared base domain. Doing so assures that users remain logged in as they webmaster@1: * cross between your various domains. webmaster@1: */ webmaster@1: # $cookie_domain = 'example.com'; webmaster@1: webmaster@1: /** webmaster@1: * Variable overrides: webmaster@1: * webmaster@1: * To override specific entries in the 'variable' table for this site, webmaster@1: * set them here. You usually don't need to use this feature. This is webmaster@1: * useful in a configuration file for a vhost or directory, rather than webmaster@1: * the default settings.php. Any configuration setting from the 'variable' webmaster@1: * table can be given a new value. Note that any values you provide in webmaster@1: * these variable overrides will not be modifiable from the Drupal webmaster@1: * administration interface. webmaster@1: * webmaster@1: * Remove the leading hash signs to enable. webmaster@1: */ webmaster@1: # $conf = array( webmaster@1: # 'site_name' => 'My Drupal site', webmaster@1: # 'theme_default' => 'minnelli', webmaster@1: # 'anonymous' => 'Visitor', webmaster@1: /** webmaster@1: * A custom theme can be set for the off-line page. This applies when the site webmaster@1: * is explicitly set to off-line mode through the administration page or when webmaster@1: * the database is inactive due to an error. It can be set through the webmaster@1: * 'maintenance_theme' key. The template file should also be copied into the webmaster@1: * theme. It is located inside 'modules/system/maintenance-page.tpl.php'. webmaster@1: * Note: This setting does not apply to installation and update pages. webmaster@1: */ webmaster@1: # 'maintenance_theme' => 'minnelli', webmaster@1: /** webmaster@1: * reverse_proxy accepts a boolean value. webmaster@1: * webmaster@1: * Enable this setting to determine the correct IP address of the remote webmaster@1: * client by examining information stored in the X-Forwarded-For headers. webmaster@1: * X-Forwarded-For headers are a standard mechanism for identifying client webmaster@1: * systems connecting through a reverse proxy server, such as Squid or webmaster@1: * Pound. Reverse proxy servers are often used to enhance the performance webmaster@1: * of heavily visited sites and may also provide other site caching, webmaster@1: * security or encryption benefits. If this Drupal installation operates webmaster@1: * behind a reverse proxy, this setting should be enabled so that correct webmaster@1: * IP address information is captured in Drupal's session management, webmaster@1: * logging, statistics and access management systems; if you are unsure webmaster@1: * about this setting, do not have a reverse proxy, or Drupal operates in webmaster@1: * a shared hosting environment, this setting should be set to disabled. webmaster@1: */ webmaster@1: # 'reverse_proxy' => TRUE, webmaster@1: /** webmaster@1: * reverse_proxy accepts an array of IP addresses. webmaster@1: * webmaster@1: * Each element of this array is the IP address of any of your reverse webmaster@1: * proxies. Filling this array Drupal will trust the information stored webmaster@1: * in the X-Forwarded-For headers only if Remote IP address is one of webmaster@1: * these, that is the request reaches the web server from one of your webmaster@1: * reverse proxies. Otherwise, the client could directly connect to webmaster@1: * your web server spoofing the X-Forwarded-For headers. webmaster@1: */ webmaster@1: # 'reverse_proxy_addresses' => array('a.b.c.d', ...), webmaster@1: # ); webmaster@1: webmaster@1: /** webmaster@1: * String overrides: webmaster@1: * webmaster@1: * To override specific strings on your site with or without enabling locale webmaster@1: * module, add an entry to this list. This functionality allows you to change webmaster@1: * a small number of your site's default English language interface strings. webmaster@1: * webmaster@1: * Remove the leading hash signs to enable. webmaster@1: */ webmaster@1: # $conf['locale_custom_strings_en'] = array( webmaster@1: # 'forum' => 'Discussion board', webmaster@1: # '@count min' => '@count minutes', webmaster@1: # );