Search moodle.org's
Developer Documentation

See Release Notes
Long Term Support Release

  • Bug fixes for general core bugs in 4.1.x will end 13 November 2023 (12 months).
  • Bug fixes for security issues in 4.1.x will end 10 November 2025 (36 months).
  • PHP version: minimum PHP 7.4.0 Note: minimum PHP version has increased since Moodle 4.0. PHP 8.0.x is supported too.
/ -> config-dist.php (source)

Differences Between: [Versions 310 and 401] [Versions 311 and 401] [Versions 39 and 401] [Versions 400 and 401] [Versions 401 and 402] [Versions 401 and 403]

   1  <?php
   2  ///////////////////////////////////////////////////////////////////////////
   3  //                                                                       //
   4  // Moodle configuration file                                             //
   5  //                                                                       //
   6  // This file should be renamed "config.php" in the top-level directory   //
   7  //                                                                       //
   8  ///////////////////////////////////////////////////////////////////////////
   9  //                                                                       //
  10  // NOTICE OF COPYRIGHT                                                   //
  11  //                                                                       //
  12  // Moodle - Modular Object-Oriented Dynamic Learning Environment         //
  13  //          http://moodle.org                                            //
  14  //                                                                       //
  15  // Copyright (C) 1999 onwards  Martin Dougiamas  http://moodle.com       //
  16  //                                                                       //
  17  // This program is free software; you can redistribute it and/or modify  //
  18  // it under the terms of the GNU General Public License as published by  //
  19  // the Free Software Foundation; either version 3 of the License, or     //
  20  // (at your option) any later version.                                   //
  21  //                                                                       //
  22  // This program is distributed in the hope that it will be useful,       //
  23  // but WITHOUT ANY WARRANTY; without even the implied warranty of        //
  24  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the         //
  25  // GNU General Public License for more details:                          //
  26  //                                                                       //
  27  //          http://www.gnu.org/copyleft/gpl.html                         //
  28  //                                                                       //
  29  ///////////////////////////////////////////////////////////////////////////
  30  unset($CFG);  // Ignore this line
  31  global $CFG;  // This is necessary here for PHPUnit execution
  32  $CFG = new stdClass();
  33  
  34  //=========================================================================
  35  // 1. DATABASE SETUP
  36  //=========================================================================
  37  // First, you need to configure the database where all Moodle data       //
  38  // will be stored.  This database must already have been created         //
  39  // and a username/password created to access it.                         //
  40  
  41  $CFG->dbtype    = 'pgsql';      // 'pgsql', 'mariadb', 'mysqli', 'auroramysql', 'sqlsrv' or 'oci'
  42  $CFG->dblibrary = 'native';     // 'native' only at the moment
  43  $CFG->dbhost    = 'localhost';  // eg 'localhost' or 'db.isp.com' or IP
  44  $CFG->dbname    = 'moodle';     // database name, eg moodle
  45  $CFG->dbuser    = 'username';   // your database username
  46  $CFG->dbpass    = 'password';   // your database password
  47  $CFG->prefix    = 'mdl_';       // prefix to use for all table names
  48  $CFG->dboptions = array(
  49      'dbpersist' => false,       // should persistent database connections be
  50                                  //  used? set to 'false' for the most stable
  51                                  //  setting, 'true' can improve performance
  52                                  //  sometimes
  53      'dbsocket'  => false,       // should connection via UNIX socket be used?
  54                                  //  if you set it to 'true' or custom path
  55                                  //  here set dbhost to 'localhost',
  56                                  //  (please note mysql is always using socket
  57                                  //  if dbhost is 'localhost' - if you need
  58                                  //  local port connection use '127.0.0.1')
  59      'dbport'    => '',          // the TCP port number to use when connecting
  60                                  //  to the server. keep empty string for the
  61                                  //  default port
  62      'dbhandlesoptions' => false,// On PostgreSQL poolers like pgbouncer don't
  63                                  // support advanced options on connection.
  64                                  // If you set those in the database then
  65                                  // the advanced settings will not be sent.
  66      'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
  67                                  // support. If you wish to use partial UTF-8
  68                                  // (three bytes) then set this option to
  69                                  // 'utf8_unicode_ci', otherwise this option
  70                                  // can be removed for MySQL (by default it will
  71                                  // use 'utf8mb4_unicode_ci'. This option should
  72                                  // be removed for all other databases.
  73      // 'extrainfo' => [],       // Extra information for the DB driver, e.g. SQL Server,
  74                                  // has additional configuration according to its environment,
  75                                  // which the administrator can specify to alter and
  76                                  // override any connection options.
  77      // 'fetchbuffersize' => 100000, // On PostgreSQL, this option sets a limit
  78                                  // on the number of rows that are fetched into
  79                                  // memory when doing a large recordset query
  80                                  // (e.g. search indexing). Default is 100000.
  81                                  // Uncomment and set to a value to change it,
  82                                  // or zero to turn off the limit. You need to
  83                                  // set to zero if you are using pg_bouncer in
  84                                  // 'transaction' mode (it is fine in 'session'
  85                                  // mode).
  86      /*
  87      'connecttimeout' => null, // Set connect timeout in seconds. Not all drivers support it.
  88      'readonly' => [          // Set to read-only slave details, to get safe reads
  89                               // from there instead of the master node. Optional.
  90                               // Currently supported by pgsql and mysqli variety classes.
  91                               // If not supported silently ignored.
  92        'instance' => [        // Readonly slave connection parameters
  93          [
  94            'dbhost' => 'slave.dbhost',
  95            'dbport' => '',    // Defaults to master port
  96            'dbuser' => '',    // Defaults to master user
  97            'dbpass' => '',    // Defaults to master password
  98          ],
  99          [...],
 100        ],
 101  
 102      Instance(s) can alternatively be specified as:
 103  
 104        'instance' => 'slave.dbhost',
 105        'instance' => ['slave.dbhost1', 'slave.dbhost2'],
 106        'instance' => ['dbhost' => 'slave.dbhost', 'dbport' => '', 'dbuser' => '', 'dbpass' => ''],
 107  
 108        'connecttimeout' => 2, // Set read-only slave connect timeout in seconds. See above.
 109        'latency' => 0.5,      // Set read-only slave sync latency in seconds.
 110                               // When 'latency' seconds have lapsed after an update to a table
 111                               // it is deemed safe to use readonly slave for reading from the table.
 112                               // It is optional, defaults to 1 second. If you want once written to a table
 113                               // to always use master handle for reading set it to something ridiculosly big,
 114                               // eg 10.
 115                               // Lower values increase the performance, but setting it too low means
 116                               // missing the master-slave sync.
 117        'exclude_tables' => [  // Tables to exclude from read-only slave feature.
 118            'table1',          // Should not be used, unless in rare cases when some area of the system
 119            'table2',          // is malfunctioning and you still want to use readonly feature.
 120        ],                     // Then one can exclude offending tables while investigating.
 121  
 122      More info available in lib/dml/moodle_read_slave_trait.php where the feature is implemented.
 123      ]
 124       */
 125  // For all database config settings see https://docs.moodle.org/en/Database_settings
 126  );
 127  
 128  
 129  //=========================================================================
 130  // 2. WEB SITE LOCATION
 131  //=========================================================================
 132  // Now you need to tell Moodle where it is located. Specify the full
 133  // web address to where moodle has been installed.  If your web site
 134  // is accessible via multiple URLs then choose the most natural one
 135  // that your students would use.  Do not include a trailing slash
 136  //
 137  // If you need both intranet and Internet access please read
 138  // http://docs.moodle.org/en/masquerading
 139  
 140  $CFG->wwwroot   = 'http://example.com/moodle';
 141  
 142  
 143  //=========================================================================
 144  // 3. DATA FILES LOCATION
 145  //=========================================================================
 146  // Now you need a place where Moodle can save uploaded files.  This
 147  // directory should be readable AND WRITEABLE by the web server user
 148  // (usually 'nobody' or 'apache'), but it should not be accessible
 149  // directly via the web.
 150  //
 151  // - On hosting systems you might need to make sure that your "group" has
 152  //   no permissions at all, but that "others" have full permissions.
 153  //
 154  // - On Windows systems you might specify something like 'c:\moodledata'
 155  
 156  $CFG->dataroot  = '/home/example/moodledata';
 157  
 158  
 159  //=========================================================================
 160  // 4. DATA FILES PERMISSIONS
 161  //=========================================================================
 162  // The following parameter sets the permissions of new directories
 163  // created by Moodle within the data directory.  The format is in
 164  // octal format (as used by the Unix utility chmod, for example).
 165  // The default is usually OK, but you may want to change it to 0750
 166  // if you are concerned about world-access to the files (you will need
 167  // to make sure the web server process (eg Apache) can access the files.
 168  // NOTE: the prefixed 0 is important, and don't use quotes.
 169  
 170  $CFG->directorypermissions = 02777;
 171  
 172  
 173  //=========================================================================
 174  // 5. ADMIN DIRECTORY LOCATION  (deprecated)
 175  //=========================================================================
 176  // Please note: Support from this feature has been deprecated and it will be
 177  // removed after Moodle 4.2.
 178  //
 179  // A very few webhosts use /admin as a special URL for you to access a
 180  // control panel or something.  Unfortunately this conflicts with the
 181  // standard location for the Moodle admin pages.  You can work around this
 182  // by renaming the admin directory in your installation, and putting that
 183  // new name here.  eg "moodleadmin".  This should fix all admin links in Moodle.
 184  // After any change you need to visit your new admin directory
 185  // and purge all caches.
 186  
 187  $CFG->admin = 'admin';
 188  
 189  
 190  //=========================================================================
 191  // 6. OTHER MISCELLANEOUS SETTINGS (ignore these for new installations)
 192  //=========================================================================
 193  //
 194  // These are additional tweaks for which no GUI exists in Moodle yet.
 195  //
 196  // Starting in PHP 5.3 administrators should specify default timezone
 197  // in PHP.ini, you can also specify it here if needed.
 198  // See details at: http://php.net/manual/en/function.date-default-timezone-set.php
 199  // List of time zones at: http://php.net/manual/en/timezones.php
 200  //     date_default_timezone_set('Australia/Perth');
 201  //
 202  // Change the key pair lifetime for Moodle Networking
 203  // The default is 28 days. You would only want to change this if the key
 204  // was not getting regenerated for any reason. You would probably want
 205  // make it much longer. Note that you'll need to delete and manually update
 206  // any existing key.
 207  //      $CFG->mnetkeylifetime = 28;
 208  //
 209  // Not recommended: Set the following to true to allow the use
 210  // off non-Moodle standard characters in usernames.
 211  //      $CFG->extendedusernamechars = true;
 212  //
 213  // Allow user passwords to be included in backup files. Very dangerous
 214  // setting as far as it publishes password hashes that can be unencrypted
 215  // if the backup file is publicy available. Use it only if you can guarantee
 216  // that all your backup files remain only privacy available and are never
 217  // shared out from your site/institution!
 218  //      $CFG->includeuserpasswordsinbackup = true;
 219  //
 220  // Completely disable user creation when restoring a course, bypassing any
 221  // permissions granted via roles and capabilities. Enabling this setting
 222  // results in the restore process stopping when a user attempts to restore a
 223  // course requiring users to be created.
 224  //     $CFG->disableusercreationonrestore = true;
 225  //
 226  // Keep the temporary directories used by backup and restore without being
 227  // deleted at the end of the process. Use it if you want to debug / view
 228  // all the information stored there after the process has ended. Note that
 229  // those directories may be deleted (after some ttl) both by cron and / or
 230  // by new backup / restore invocations.
 231  //     $CFG->keeptempdirectoriesonbackup = true;
 232  //
 233  // Modify the restore process in order to force the "user checks" to assume
 234  // that the backup originated from a different site, so detection of matching
 235  // users is performed with different (more "relaxed") rules. Note that this is
 236  // only useful if the backup file has been created using Moodle < 1.9.4 and the
 237  // site has been rebuilt from scratch using backup files (not the best way btw).
 238  // If you obtain user conflicts on restore, rather than enabling this setting
 239  // permanently, try restoring the backup on a different site, back it up again
 240  // and then restore on the target server.
 241  //    $CFG->forcedifferentsitecheckingusersonrestore = true;
 242  //
 243  // Force the backup system to continue to create backups in the legacy zip
 244  // format instead of the new tgz format. Does not affect restore, which
 245  // auto-detects the underlying file format.
 246  //    $CFG->usezipbackups = true;
 247  //
 248  // Prevent stats processing and hide the GUI
 249  //      $CFG->disablestatsprocessing = true;
 250  //
 251  // Setting this to true will enable admins to edit any post at any time
 252  //      $CFG->admineditalways = true;
 253  //
 254  // These variables define DEFAULT block variables for new courses
 255  // If this one is set it overrides all others and is the only one used.
 256  //      $CFG->defaultblocks_override = 'activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
 257  //
 258  // These variables define the specific settings for defined course formats.
 259  // They override any settings defined in the formats own config file.
 260  //      $CFG->defaultblocks_site = 'site_main_menu,course_list:course_summary,calendar_month';
 261  //      $CFG->defaultblocks_social = 'search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,course_list';
 262  //      $CFG->defaultblocks_topics = 'activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
 263  //      $CFG->defaultblocks_weeks = 'activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
 264  //
 265  // These blocks are used when no other default setting is found.
 266  //      $CFG->defaultblocks = 'activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
 267  //
 268  // You can specify a different class to be created for the $PAGE global, and to
 269  // compute which blocks appear on each page. However, I cannot think of any good
 270  // reason why you would need to change that. It just felt wrong to hard-code the
 271  // the class name. You are strongly advised not to use these to settings unless
 272  // you are absolutely sure you know what you are doing.
 273  //      $CFG->moodlepageclass = 'moodle_page';
 274  //      $CFG->moodlepageclassfile = "$CFG->dirroot/local/myplugin/mypageclass.php";
 275  //      $CFG->blockmanagerclass = 'block_manager';
 276  //      $CFG->blockmanagerclassfile = "$CFG->dirroot/local/myplugin/myblockamanagerclass.php";
 277  //
 278  // Seconds for files to remain in caches. Decrease this if you are worried
 279  // about students being served outdated versions of uploaded files.
 280  //     $CFG->filelifetime = 60*60*6;
 281  //
 282  // Some web servers can offload the file serving from PHP process,
 283  // comment out one the following options to enable it in Moodle:
 284  //     $CFG->xsendfile = 'X-Sendfile';           // Apache {@see https://tn123.org/mod_xsendfile/}
 285  //     $CFG->xsendfile = 'X-LIGHTTPD-send-file'; // Lighttpd {@see http://redmine.lighttpd.net/projects/lighttpd/wiki/X-LIGHTTPD-send-file}
 286  //     $CFG->xsendfile = 'X-Accel-Redirect';     // Nginx {@see http://wiki.nginx.org/XSendfile}
 287  // If your X-Sendfile implementation (usually Nginx) uses directory aliases specify them
 288  // in the following array setting:
 289  //     $CFG->xsendfilealiases = array(
 290  //         '/dataroot/' => $CFG->dataroot,
 291  //         '/cachedir/' => '/var/www/moodle/cache',    // for custom $CFG->cachedir locations
 292  //         '/localcachedir/' => '/var/local/cache',    // for custom $CFG->localcachedir locations
 293  //         '/tempdir/'  => '/var/www/moodle/temp',     // for custom $CFG->tempdir locations
 294  //         '/filedir'   => '/var/www/moodle/filedir',  // for custom $CFG->filedir locations
 295  //     );
 296  //
 297  // YUI caching may be sometimes improved by slasharguments:
 298  //     $CFG->yuislasharguments = 1;
 299  // Some servers may need a special rewrite rule to work around internal path length limitations:
 300  // RewriteRule (^.*/theme/yui_combo\.php)(/.*) $1?file=$2
 301  //
 302  //
 303  // Following settings may be used to select session driver, uncomment only one of the handlers.
 304  //   Database session handler (not compatible with MyISAM):
 305  //      $CFG->session_handler_class = '\core\session\database';
 306  //      $CFG->session_database_acquire_lock_timeout = 120;
 307  //
 308  //   File session handler (file system locking required):
 309  //      $CFG->session_handler_class = '\core\session\file';
 310  //      $CFG->session_file_save_path = $CFG->dataroot.'/sessions';
 311  //
 312  //   Memcached session handler (requires memcached server and extension):
 313  //      $CFG->session_handler_class = '\core\session\memcached';
 314  //      $CFG->session_memcached_save_path = '127.0.0.1:11211';
 315  //      $CFG->session_memcached_prefix = 'memc.sess.key.';
 316  //      $CFG->session_memcached_acquire_lock_timeout = 120;
 317  //      $CFG->session_memcached_lock_expire = 7200;       // Ignored if PECL memcached is below version 2.2.0
 318  //      $CFG->session_memcached_lock_retry_sleep = 150;   // Spin-lock retry sleeptime (msec). Only effective
 319  //                                                        // for tuning php-memcached 3.0.x (PHP 7)
 320  //
 321  //   Redis session handler (requires redis server and redis extension):
 322  //      $CFG->session_handler_class = '\core\session\redis';
 323  //      $CFG->session_redis_host = '127.0.0.1';
 324  //      $CFG->session_redis_port = 6379;                     // Optional.
 325  //      $CFG->session_redis_database = 0;                    // Optional, default is db 0.
 326  //      $CFG->session_redis_auth = '';                       // Optional, default is don't set one.
 327  //      $CFG->session_redis_prefix = '';                     // Optional, default is don't set one.
 328  //      $CFG->session_redis_acquire_lock_timeout = 120;      // Default is 2 minutes.
 329  //      $CFG->session_redis_acquire_lock_warn = 0;           // If set logs early warning if a lock has not been acquried.
 330  //      $CFG->session_redis_lock_expire = 7200;              // Optional, defaults to session timeout.
 331  //      $CFG->session_redis_lock_retry = 100;                // Optional wait between lock attempts in ms, default is 100.
 332  //                                                           // After 5 seconds it will throttle down to once per second.
 333  //
 334  //      Use the igbinary serializer instead of the php default one. Note that phpredis must be compiled with
 335  //      igbinary support to make the setting to work. Also, if you change the serializer you have to flush the database!
 336  //      $CFG->session_redis_serializer_use_igbinary = false; // Optional, default is PHP builtin serializer.
 337  //      $CFG->session_redis_compressor = 'none';             // Optional, possible values are:
 338  //                                                           // 'gzip' - PHP GZip compression
 339  //                                                           // 'zstd' - PHP Zstandard compression
 340  //
 341  // Please be aware that when selecting Memcached for sessions that it is advised to use a dedicated
 342  // memcache server. The memcached extension does not provide isolated environments for individual uses.
 343  // Using the same server for other purposes (MUC for example) can lead to sessions being prematurely removed should
 344  // the other uses of the server purge the cache.
 345  //
 346  // Following setting allows you to alter how frequently is timemodified updated in sessions table.
 347  //      $CFG->session_update_timemodified_frequency = 20; // In seconds.
 348  //
 349  // If this setting is set to true, then Moodle will track the IP of the
 350  // current user to make sure it hasn't changed during a session.  This
 351  // will prevent the possibility of sessions being hijacked via XSS, but it
 352  // may break things for users coming using proxies that change all the time,
 353  // like AOL.
 354  //      $CFG->tracksessionip = true;
 355  //
 356  // The following lines are for handling email bounces.
 357  //      $CFG->handlebounces = true;
 358  //      $CFG->minbounces = 10;
 359  //      $CFG->bounceratio = .20;
 360  // The next lines are needed both for bounce handling and any other email to module processing.
 361  // mailprefix must be EXACTLY four characters.
 362  // Uncomment and customise this block for Postfix
 363  //      $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix.
 364  //      $CFG->mailprefix = 'mdl-'; // - is the separator for qmail
 365  //      $CFG->maildomain = 'youremaildomain.com';
 366  //
 367  // Enable when setting up advanced reverse proxy load balancing configurations,
 368  // it may be also necessary to enable this when using port forwarding.
 369  //      $CFG->reverseproxy = true;
 370  //
 371  // Enable when using external SSL appliance for performance reasons.
 372  // Please note that site may be accessible via http: or https:, but not both!
 373  //      $CFG->sslproxy = true;
 374  //
 375  // This setting will cause the userdate() function not to fix %d in
 376  // date strings, and just let them show with a zero prefix.
 377  //      $CFG->nofixday = true;
 378  //
 379  // This setting will make some graphs (eg user logs) use lines instead of bars
 380  //      $CFG->preferlinegraphs = true;
 381  //
 382  // This setting allows you to specify a class to rewrite outgoing urls
 383  // enabling 'clean urls' in conjunction with an apache / nginx handler.
 384  // The handler must implement \core\output\url_rewriter.
 385  //      $CFG->urlrewriteclass = '\local_cleanurls\url_rewriter';
 386  //
 387  // Enabling this will allow custom scripts to replace existing moodle scripts.
 388  // For example: if $CFG->customscripts/course/view.php exists then
 389  // it will be used instead of $CFG->wwwroot/course/view.php
 390  // At present this will only work for files that include config.php and are called
 391  // as part of the url (index.php is implied).
 392  // Some examples are:
 393  //      http://my.moodle.site/course/view.php
 394  //      http://my.moodle.site/index.php
 395  //      http://my.moodle.site/admin            (index.php implied)
 396  // Custom scripts should not include config.php
 397  // Warning: Replacing standard moodle scripts may pose security risks and/or may not
 398  // be compatible with upgrades. Use this option only if you are aware of the risks
 399  // involved.
 400  // Specify the full directory path to the custom scripts
 401  //      $CFG->customscripts = '/home/example/customscripts';
 402  //
 403  // Performance profiling
 404  //
 405  //   If you set Debug to "Yes" in the Configuration->Variables page some
 406  //   performance profiling data will show up on your footer (in default theme).
 407  //   With these settings you get more granular control over the capture
 408  //   and printout of the data
 409  //
 410  //   Capture performance profiling data
 411  //   define('MDL_PERF'  , true);
 412  //
 413  //   Capture additional data from DB
 414  //   define('MDL_PERFDB'  , true);
 415  //
 416  //   Print to log (for passive profiling of production servers)
 417  //   define('MDL_PERFTOLOG'  , true);
 418  //
 419  //   Print to footer (works with the default theme)
 420  //   define('MDL_PERFTOFOOT', true);
 421  //
 422  //   Print additional data to log of included files
 423  //   define('MDL_PERFINC', true);
 424  //
 425  //   Enable earlier profiling that causes more code to be covered
 426  //   on every request (db connections, config load, other inits...).
 427  //   Requires extra configuration to be defined in config.php like:
 428  //   profilingincluded, profilingexcluded, profilingautofrec,
 429  //   profilingallowme, profilingallowall, profilinglifetime
 430  //       $CFG->earlyprofilingenabled = true;
 431  //
 432  // Disable database storage for profile data.
 433  // When using an exernal plugin to store profiling data it is often
 434  // desirable to not store the data in the database.
 435  //
 436  //      $CFG->disableprofilingtodatabase = true;
 437  //
 438  // Force displayed usernames
 439  //   A little hack to anonymise user names for all students.  If you set these
 440  //   then all non-teachers will always see these for every person.
 441  //       $CFG->forcefirstname = 'Bruce';
 442  //       $CFG->forcelastname  = 'Simpson';
 443  //
 444  // The following setting will turn on username logging into Apache log. For full details regarding setting
 445  // up of this function please refer to the install section of the document.
 446  //     $CFG->apacheloguser = 0; // Turn this feature off. Default value.
 447  //     $CFG->apacheloguser = 1; // Log user id.
 448  //     $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
 449  //     $CFG->apacheloguser = 3; // Log username.
 450  // To get the values logged in Apache's log, add to your httpd.conf
 451  // the following statements. In the General part put:
 452  //     LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat
 453  // And in the part specific to your Moodle install / virtualhost:
 454  //     CustomLog "/your/path/to/log" moodleformat
 455  //
 456  // Alternatively for other webservers such as nginx, you can instead have the username sent via a http header
 457  // 'X-MOODLEUSER' which can be saved in the logfile and then stripped out before being sent to the browser:
 458  //     $CFG->headerloguser = 0; // Turn this feature off. Default value.
 459  //     $CFG->headerloguser = 1; // Log user id.
 460  //     $CFG->headerloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
 461  //     $CFG->headerloguser = 3; // Log username.
 462  //
 463  // CAUTION: Use of this option will expose usernames in the Apache / nginx log,
 464  // If you are going to publish your log, or the output of your web stats analyzer
 465  // this will weaken the security of your website.
 466  //
 467  // Email database connection errors to someone.  If Moodle cannot connect to the
 468  // database, then email this address with a notice.
 469  //
 470  //     $CFG->emailconnectionerrorsto = 'your@emailaddress.com';
 471  //
 472  // Set the priority of themes from highest to lowest. This is useful (for
 473  // example) in sites where the user theme should override all other theme
 474  // settings for accessibility reasons. You can also disable types of themes
 475  // (other than site)  by removing them from the array. The default setting is:
 476  //
 477  //     $CFG->themeorder = array('course', 'category', 'session', 'user', 'cohort', 'site');
 478  //
 479  // NOTE: course, category, session, user, cohort themes still require the
 480  // respective settings to be enabled
 481  //
 482  // It is possible to add extra themes directory stored outside of $CFG->dirroot.
 483  // This local directory does not have to be accessible from internet.
 484  //
 485  //     $CFG->themedir = '/location/of/extra/themes';
 486  //
 487  // It is possible to specify different cache and temp directories, use local fast filesystem
 488  // for normal web servers. Server clusters MUST use shared filesystem for cachedir!
 489  // Localcachedir is intended for server clusters, it does not have to be shared by cluster nodes.
 490  // The directories must not be accessible via web.
 491  //
 492  //     $CFG->tempdir = '/var/www/moodle/temp';        // Directory MUST BE SHARED by all cluster nodes.
 493  //     $CFG->cachedir = '/var/www/moodle/cache';      // Directory MUST BE SHARED by all cluster nodes, locking required.
 494  //     $CFG->localcachedir = '/var/local/cache';      // Intended for local node caching.
 495  //     $CFG->localrequestdir = '/tmp';                // Intended for local only temporary files. The defaults uses sys_get_temp_dir().
 496  //
 497  // It is possible to specify a different backup temp directory, use local fast filesystem
 498  // for normal web servers. Server clusters MUST use shared filesystem for backuptempdir!
 499  // The directory must not be accessible via web.
 500  //
 501  //     $CFG->backuptempdir = '/var/www/moodle/backuptemp';  // Directory MUST BE SHARED by all cluster nodes.
 502  //
 503  // Some filesystems such as NFS may not support file locking operations.
 504  // Locking resolves race conditions and is strongly recommended for production servers.
 505  //     $CFG->preventfilelocking = false;
 506  //
 507  // Site default language can be set via standard administration interface. If you
 508  // want to have initial error messages for eventual database connection problems
 509  // localized too, you have to set your language code here.
 510  //
 511  //     $CFG->lang = 'yourlangcode'; // for example 'cs'
 512  //
 513  // When Moodle is about to perform an intensive operation it raises PHP's memory
 514  // limit. The following setting should be used on large sites to set the raised
 515  // memory limit to something higher.
 516  // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G
 517  //
 518  //     $CFG->extramemorylimit = '1024M';
 519  //
 520  // Moodle 2.4 introduced a new cache API.
 521  // The cache API stores a configuration file within the Moodle data directory and
 522  // uses that rather than the database in order to function in a stand-alone manner.
 523  // Using altcacheconfigpath you can change the location where this config file is
 524  // looked for.
 525  // It can either be a directory in which to store the file, or the full path to the
 526  // file if you want to take full control. Either way it must be writable by the
 527  // webserver.
 528  //
 529  //     $CFG->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php
 530  //
 531  // Use the following flag to completely disable the Available update notifications
 532  // feature and hide it from the server administration UI.
 533  //
 534  //      $CFG->disableupdatenotifications = true;
 535  //
 536  // Use the following flag to completely disable the installation of plugins
 537  // (new plugins, available updates and missing dependencies) and related
 538  // features (such as cancelling the plugin installation or upgrade) via the
 539  // server administration web interface.
 540  //
 541  //      $CFG->disableupdateautodeploy = true;
 542  //
 543  // Use the following flag to disable the warning on the system notifications page
 544  // about present development libraries. This flag will not disable the warning within
 545  // the security overview report. Use this flag only if you really have prohibited web
 546  // access to the development libraries in your webserver configuration.
 547  //
 548  //      $CFG->disabledevlibdirscheck = true;
 549  //
 550  // Use the following flag to disable modifications to scheduled tasks
 551  // whilst still showing the state of tasks.
 552  //
 553  //      $CFG->preventscheduledtaskchanges = true;
 554  //
 555  // As of version 2.4 Moodle serves icons as SVG images if the users browser appears
 556  // to support SVG.
 557  // For those wanting to control the serving of SVG images the following setting can
 558  // be defined in your config.php.
 559  // If it is not defined then the default (browser detection) will occur.
 560  //
 561  // To ensure they are always used when available:
 562  //      $CFG->svgicons = true;
 563  //
 564  // To ensure they are never used even when available:
 565  //      $CFG->svgicons = false;
 566  //
 567  // Some administration options allow setting the path to executable files. This can
 568  // potentially cause a security risk. Set this option to true to disable editing
 569  // those config settings via the web. They will need to be set explicitly in the
 570  // config.php file
 571  //      $CFG->preventexecpath = true;
 572  //
 573  // Use the following flag to set userid for noreply user. If not set then moodle will
 574  // create dummy user and use -ve value as user id.
 575  //      $CFG->noreplyuserid = -10;
 576  //
 577  // As of version 2.6 Moodle supports admin to set support user. If not set, all mails
 578  // will be sent to supportemail.
 579  //      $CFG->supportuserid = -20;
 580  //
 581  // Moodle 2.7 introduces a locking api for critical tasks (e.g. cron).
 582  // The default locking system to use is DB locking for Postgres, MySQL, MariaDB and
 583  // file locking for Oracle and SQLServer. If $CFG->preventfilelocking is set, then the
 584  // default will always be DB locking. It can be manually set to one of the lock
 585  // factory classes listed below, or one of your own custom classes implementing the
 586  // \core\lock\lock_factory interface.
 587  //
 588  //      $CFG->lock_factory = "auto";
 589  //
 590  // The list of available lock factories is:
 591  //
 592  // "\\core\\lock\\file_lock_factory" - File locking
 593  //      Uses lock files stored by default in the dataroot. Whether this
 594  //      works on clusters depends on the file system used for the dataroot.
 595  //
 596  // "\\core\\lock\\db_record_lock_factory" - DB locking based on table rows.
 597  //
 598  // "\\core\\lock\\mysql_lock_factory" - DB locking based on MySQL / MariaDB locks.
 599  //
 600  // "\\core\\lock\\postgres_lock_factory" - DB locking based on postgres advisory locks.
 601  //
 602  // Settings used by the lock factories
 603  //
 604  // Location for lock files used by the File locking factory. This must exist
 605  // on a shared file system that supports locking.
 606  //      $CFG->file_lock_root = $CFG->dataroot . '/lock';
 607  //
 608  //
 609  // Alternative task logging.
 610  // Since Moodle 3.7 the output of al scheduled and adhoc tasks is stored in the database and it is possible to use an
 611  // alternative task logging mechanism.
 612  // To set the alternative task logging mechanism in config.php you can use the following settings, providing the
 613  // alternative class name that will be auto-loaded.
 614  //
 615  //      $CFG->task_log_class = '\\local_mytasklogger\\logger';
 616  //
 617  // Moodle 2.9 allows administrators to customise the list of supported file types.
 618  // To add a new filetype or override the definition of an existing one, set the
 619  // customfiletypes variable like this:
 620  //
 621  // $CFG->customfiletypes = array(
 622  //     (object)array(
 623  //         'extension' => 'frog',
 624  //         'icon' => 'archive',
 625  //         'type' => 'application/frog',
 626  //         'customdescription' => 'Amphibian-related file archive'
 627  //     )
 628  // );
 629  //
 630  // The extension, icon, and type fields are required. The icon field can refer to
 631  // any icon inside the pix/f folder. You can also set the customdescription field
 632  // (shown above) and (for advanced use) the groups, string, and defaulticon fields.
 633  //
 634  // Upgrade key
 635  //
 636  // If the upgrade key is defined here, then the value must be provided every time
 637  // the site is being upgraded though the web interface, regardless of whether the
 638  // administrator is logged in or not. This prevents anonymous access to the upgrade
 639  // screens where the real authentication and authorization mechanisms can not be
 640  // relied on.
 641  //
 642  // It is strongly recommended to use a value different from your real account
 643  // password.
 644  //
 645  //      $CFG->upgradekey = 'put_some_password-like_value_here';
 646  //
 647  // Font used in exported PDF files. When generating a PDF, Moodle embeds a subset of
 648  // the font in the PDF file so it will be readable on the widest range of devices.
 649  // The default font is 'freesans' which is part of the GNU FreeFont collection.
 650  //
 651  //      $CFG->pdfexportfont = 'freesans';
 652  //
 653  // Use the following flag to enable messagingallusers and set the default preference
 654  // value for existing users to allow them to be contacted by other site users.
 655  //
 656  //      $CFG->keepmessagingallusersenabled = true;
 657  //
 658  // Disable login token validation for login pages. Login token validation is enabled
 659  // by default unless $CFG->alternateloginurl is set.
 660  //
 661  //      $CFG->disablelogintoken = true;
 662  //
 663  // Moodle 3.7+ checks that cron is running frequently. If the time between cron runs
 664  // is greater than this value (in seconds), you get a warning on the admin page. (This
 665  // setting only controls whether or not the warning appears, it has no other effect.)
 666  //
 667  //      $CFG->expectedcronfrequency = 200;
 668  //
 669  // Moodle 3.9+ checks how old tasks are in the ad hoc queue and warns at 10 minutes
 670  // and errors at 4 hours. Set these to override these limits:
 671  //
 672  //      $CFG->adhoctaskagewarn = 10 * 60;
 673  //      $CFG->adhoctaskageerror = 4 * 60 * 60;
 674  //
 675  // Session lock warning threshold. Long running pages should release the session using \core\session\manager::write_close().
 676  // Set this threshold to any value greater than 0 to add developer warnings when a page locks the session for too long.
 677  // The session should rarely be locked for more than 1 second. The input should be in seconds and may be a float.
 678  //
 679  //      $CFG->debugsessionlock = 5;
 680  //
 681  // There are times when a session lock is not required during a request. For a page/service to opt-in whether or not a
 682  // session lock is required this setting must first be set to 'true'.
 683  // This is an experimental issue. The session store can not be in the session, please
 684  // see https://docs.moodle.org/en/Session_handling#Read_only_sessions.
 685  //
 686  //      $CFG->enable_read_only_sessions = true;
 687  //
 688  // To help expose all the edge cases bugs a debug mode is available which shows the same
 689  // runtime write during readonly errors without actually turning on the readonly sessions:
 690  //
 691  //      $CFG->enable_read_only_sessions_debug = true;
 692  //
 693  // Uninstall plugins from CLI only. This stops admins from uninstalling plugins from the graphical admin
 694  // user interface, and forces plugins to be uninstalled from the Command Line tool only, found at
 695  // admin/cli/plugin_uninstall.php.
 696  //
 697  //      $CFG->uninstallclionly = true;
 698  //
 699  // Course and category sorting
 700  //
 701  // If the number of courses in a category exceeds $CFG->maxcoursesincategory (10000 by default), it may lead to duplicate
 702  // sort orders of courses in separated categories. For example:
 703  // - Category A has the sort order of 10000, and has 10000 courses. The last course will have the sort order of 20000.
 704  // - Category B has the sort order of 20000, and has a course with the sort order of 20001.
 705  // - If we add another course in category A, it will have a sort order of 20001,
 706  // which is the same as the course in category B
 707  // The duplicate will cause sorting issue and hence we need to increase $CFG->maxcoursesincategory
 708  // to fix the duplicate sort order
 709  // Please also make sure $CFG->maxcoursesincategory * MAX_COURSE_CATEGORIES less than max integer.
 710  //
 711  // $CFG->maxcoursesincategory = 10000;
 712  //
 713  // Admin setting encryption
 714  //
 715  //      $CFG->secretdataroot = '/var/www/my_secret_folder';
 716  //
 717  // Location to store encryption keys. By default this is $CFG->dataroot/secret; set this if
 718  // you want to use a different location for increased security (e.g. if too many people have access
 719  // to the main dataroot, or if you want to avoid using shared storage). Your web server user needs
 720  // read access to this location, and write access unless you manually create the keys.
 721  //
 722  //      $CFG->nokeygeneration = false;
 723  //
 724  // If you change this to true then the server will give an error if keys don't exist, instead of
 725  // automatically generating them. This is only needed if you want to ensure that keys are consistent
 726  // across a cluster when not using shared storage. If you stop the server generating keys, you will
 727  // need to manually generate them by running 'php admin/cli/generate_key.php'.
 728  //
 729  // H5P crossorigin
 730  //
 731  //      $CFG->h5pcrossorigin = 'anonymous';
 732  //
 733  // Settings this to anonymous will enable CORS requests for media elements to have the credentials
 734  // flag set to 'same-origin'. This may be needed when using tool_objectfs as an alternative file
 735  // system with CloudFront configured.
 736  //
 737  // Enrolments sync interval
 738  //
 739  // The minimum time in seconds between re-synchronization of enrollment via enrol_check_plugins which is
 740  // a potentially expensive operation and otherwise happens every time a user is authenticated. This only
 741  // applies to web requests without a session such as webservice calls, tokenpluginfile.php and rss links
 742  // where the user is re-authenticated on every request. Set it to 0 to force enrollment checking constantly
 743  // and increase this number to improve performance at the cost of adding a latency for enrollment updates.
 744  // Defaults to 60 minutes.
 745  //
 746  //      $CFG->enrolments_sync_interval = 3600
 747  
 748  //=========================================================================
 749  // 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
 750  //=========================================================================
 751  //
 752  // Force a debugging mode regardless the settings in the site administration
 753  // @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
 754  // @ini_set('display_errors', '1');    // NOT FOR PRODUCTION SERVERS!
 755  // $CFG->debug = (E_ALL | E_STRICT);   // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
 756  // $CFG->debugdisplay = 1;             // NOT FOR PRODUCTION SERVERS!
 757  //
 758  // You can specify a comma separated list of user ids that that always see
 759  // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
 760  // for these users only.
 761  // $CFG->debugusers = '2';
 762  //
 763  // Prevent theme caching
 764  // $CFG->themedesignermode = true; // NOT FOR PRODUCTION SERVERS!
 765  //
 766  // Enable verbose debug information during fetching of email messages from IMAP server.
 767  // $CFG->debugimap = true;
 768  //
 769  // Enable verbose debug information during sending of email messages to SMTP server.
 770  // Note: also requires $CFG->debug set to DEBUG_DEVELOPER.
 771  // $CFG->debugsmtp = true;
 772  //
 773  // Prevent JS caching
 774  // $CFG->cachejs = false; // NOT FOR PRODUCTION SERVERS!
 775  //
 776  // Prevent Template caching
 777  // $CFG->cachetemplates = false; // NOT FOR PRODUCTION SERVERS!
 778  //
 779  // Restrict which YUI logging statements are shown in the browser console.
 780  // For details see the upstream documentation:
 781  //   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logInclude
 782  //   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logExclude
 783  // $CFG->yuiloginclude = array(
 784  //     'moodle-course-categoryexpander' => true,
 785  // );
 786  // $CFG->yuilogexclude = array(
 787  //     'moodle-core-notification' => true,
 788  // );
 789  //
 790  // Set the minimum log level for YUI logging statements.
 791  // For details see the upstream documentation:
 792  //   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logLevel
 793  // $CFG->yuiloglevel = 'debug';
 794  //
 795  // Prevent core_string_manager application caching
 796  // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!
 797  //
 798  // When working with production data on test servers, no emails or other messages
 799  // should ever be send to real users
 800  // $CFG->noemailever = true;    // NOT FOR PRODUCTION SERVERS!
 801  //
 802  // Divert all outgoing emails to this address to test and debug emailing features
 803  // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
 804  //
 805  // Except for certain email addresses you want to let through for testing. Accepts
 806  // a comma separated list of regexes.
 807  // $CFG->divertallemailsexcept = 'tester@dev.com, fred(\+.*)?@example.com'; // NOT FOR PRODUCTION SERVERS!
 808  //
 809  // Uncomment if you want to allow empty comments when modifying install.xml files.
 810  // $CFG->xmldbdisablecommentchecking = true;    // NOT FOR PRODUCTION SERVERS!
 811  //
 812  // Since 2.0 sql queries are not shown during upgrade by default.
 813  // Please note that this setting may produce very long upgrade page on large sites.
 814  // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!
 815  //
 816  // Add SQL queries to the output of cron, just before their execution
 817  // $CFG->showcronsql = true;
 818  //
 819  // Force developer level debug and add debug info to the output of cron
 820  // $CFG->showcrondebugging = true;
 821  //
 822  // Force result of checks used to determine whether a site is considered "public" or not (such as for site registration).
 823  // $CFG->site_is_public = false;
 824  //
 825  //=========================================================================
 826  // 8. FORCED SETTINGS
 827  //=========================================================================
 828  // It is possible to specify normal admin settings here, the point is that
 829  // they can not be changed through the standard admin settings pages any more.
 830  //
 831  // Core settings are specified directly via assignment to $CFG variable.
 832  // Example:
 833  //   $CFG->somecoresetting = 'value';
 834  //
 835  // Plugin settings have to be put into a special array.
 836  // Example:
 837  //   $CFG->forced_plugin_settings = array('pluginname'  => array('settingname' => 'value', 'secondsetting' => 'othervalue'),
 838  //                                        'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));
 839  // Module default settings with advanced/locked checkboxes can be set too. To do this, add
 840  // an extra config with '_adv' or '_locked' as a suffix and set the value to true or false.
 841  // Example:
 842  //   $CFG->forced_plugin_settings = array('pluginname'  => array('settingname' => 'value', 'settingname_locked' => true, 'settingname_adv' => true));
 843  //
 844  //=========================================================================
 845  // 9. PHPUNIT SUPPORT
 846  //=========================================================================
 847  // $CFG->phpunit_prefix = 'phpu_';
 848  // $CFG->phpunit_dataroot = '/home/example/phpu_moodledata';
 849  // $CFG->phpunit_directorypermissions = 02777; // optional
 850  // $CFG->phpunit_profilingenabled = true; // optional to profile PHPUnit runs.
 851  //
 852  //
 853  //=========================================================================
 854  // 10. SECRET PASSWORD SALT
 855  //=========================================================================
 856  // A site-wide password salt is no longer used in new installations.
 857  // If upgrading from 2.6 or older, keep all existing salts in config.php file.
 858  //
 859  // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1';
 860  //
 861  // You may also have some alternative salts to allow migration from previously
 862  // used salts.
 863  //
 864  // $CFG->passwordsaltalt1 = '';
 865  // $CFG->passwordsaltalt2 = '';
 866  // $CFG->passwordsaltalt3 = '';
 867  // ....
 868  // $CFG->passwordsaltalt19 = '';
 869  // $CFG->passwordsaltalt20 = '';
 870  //
 871  //
 872  //=========================================================================
 873  // 11. BEHAT SUPPORT
 874  //=========================================================================
 875  // Behat test site needs a unique www root, data directory and database prefix:
 876  //
 877  // $CFG->behat_wwwroot = 'http://127.0.0.1/moodle';
 878  // $CFG->behat_prefix = 'bht_';
 879  // $CFG->behat_dataroot = '/home/example/bht_moodledata';
 880  // $CFG->behat_dbname = 'behat'; // optional
 881  // $CFG->behat_dbuser = 'username'; // optional
 882  // $CFG->behat_dbpass = 'password'; // optional
 883  // $CFG->behat_dbhost = 'localhost'; // optional
 884  //
 885  // You can override default Moodle configuration for Behat and add your own
 886  // params; here you can add more profiles, use different Mink drivers than Selenium...
 887  // These params would be merged with the default Moodle behat.yml, giving priority
 888  // to the ones specified here. The array format is YAML, following the Behat
 889  // params hierarchy. More info: http://docs.behat.org/guides/7.config.html
 890  // Example:
 891  //   $CFG->behat_config = array(
 892  //       'Mac-Firefox' => array(
 893  //           'suites' => array (
 894  //               'default' => array(
 895  //                   'filters' => array(
 896  //                      'tags' => '~@_file_upload'
 897  //                   ),
 898  //               ),
 899  //           ),
 900  //           'extensions' => array(
 901  //               'Behat\MinkExtension' => array(
 902  //                   'webddriver' => array(
 903  //                       'browser' => 'firefox',
 904  //                       'capabilities' => array(
 905  //                           'platform' => 'OS X 10.6',
 906  //                           'version' => 20
 907  //                       )
 908  //                   )
 909  //               )
 910  //           )
 911  //       ),
 912  //       'Mac-Safari' => array(
 913  //           'extensions' => array(
 914  //               'Behat\MinkExtension' => array(
 915  //                   'webddriver' => array(
 916  //                       'browser' => 'safari',
 917  //                       'capabilities' => array(
 918  //                           'platform' => 'OS X 10.8',
 919  //                           'version' => 6
 920  //                       )
 921  //                   )
 922  //               )
 923  //           )
 924  //       )
 925  //   );
 926  // You can also use the following config to override default Moodle configuration for Behat.
 927  // This config is limited to default suite and will be supported in later versions.
 928  // It will have precedence over $CFG->behat_config.
 929  // $CFG->behat_profiles = array(
 930  //     'phantomjs' => array(
 931  //         'browser' => 'phantomjs',
 932  //         'tags' => '~@_file_upload&&~@_alert&&~@_bug_phantomjs',
 933  //         'wd_host' => 'http://127.0.0.1:4443/wd/hub',
 934  //         'capabilities' => array(
 935  //             'platform' => 'Linux',
 936  //             'version' => 2.1
 937  //         )
 938  //     ),
 939  // );
 940  //
 941  // All this page's extra Moodle settings are compared against a white list of allowed settings
 942  // (the basic and behat_* ones) to avoid problems with production environments. This setting can be
 943  // used to expand the default white list with an array of extra settings.
 944  // Example:
 945  //   $CFG->behat_extraallowedsettings = array('somecoresetting', ...);
 946  //
 947  // You should explicitly allow the usage of the deprecated behat steps, otherwise an exception will
 948  // be thrown when using them. The setting is disabled by default.
 949  // Example:
 950  //   $CFG->behat_usedeprecated = true;
 951  //
 952  // If you are using a slow machine, it may help to increase the timeouts that Behat uses. The
 953  // following example will increase timeouts by a factor of 3 (using 30 seconds instead of 10
 954  // seconds, for instance).
 955  // Example:
 956  //   $CFG->behat_increasetimeout = 3;
 957  //
 958  // Yon can specify a window size modifier for Behat, which is applied to any window szie changes.
 959  // For example, if a window size of 640x768 is specified, with a modifier of 2, then the final size is 1280x1536.
 960  // This is particularly useful for behat reruns to eliminate issues with window sizing.
 961  // Example:
 962  //   $CFG->behat_window_size_modifier = 1;
 963  //
 964  // Including feature files from directories outside the dirroot is possible if required. The setting
 965  // requires that the running user has executable permissions on all parent directories in the paths.
 966  // Example:
 967  //   $CFG->behat_additionalfeatures = array('/home/developer/code/wipfeatures');
 968  //
 969  // You can make behat save several dumps when a scenario fails. The dumps currently saved are:
 970  // * a dump of the DOM in it's state at the time of failure; and
 971  // * a screenshot (JavaScript is required for the screenshot functionality, so not all browsers support this option)
 972  // Example:
 973  //   $CFG->behat_faildump_path = '/my/path/to/save/failure/dumps';
 974  //
 975  // You can make behat pause upon failure to help you diagnose and debug problems with your tests.
 976  //
 977  //   $CFG->behat_pause_on_fail = true;
 978  //
 979  // You can specify db, selenium wd_host etc. for behat parallel run by setting following variable.
 980  // Example:
 981  //   $CFG->behat_parallel_run = array (
 982  //       array (
 983  //           'dbtype' => 'mysqli',
 984  //           'dblibrary' => 'native',
 985  //           'dbhost' => 'localhost',
 986  //           'dbname' => 'moodletest',
 987  //           'dbuser' => 'moodle',
 988  //           'dbpass' => 'moodle',
 989  //           'behat_prefix' => 'mdl_',
 990  //           'wd_host' => 'http://127.0.0.1:4444/wd/hub',
 991  //           'behat_wwwroot' => 'http://127.0.0.1/moodle',
 992  //           'behat_dataroot' => '/home/example/bht_moodledata'
 993  //       ),
 994  //   );
 995  //
 996  // To change name of behat parallel run site, define BEHAT_PARALLEL_SITE_NAME and parallel run sites will be suffixed
 997  // with this value
 998  // Example:
 999  //   define('BEHAT_PARALLEL_SITE_NAME', 'behatparallelsite');
1000  //
1001  // Command line output for parallel behat install is limited to 80 chars, if you are installing more then 4 sites and
1002  // want to expand output to more then 80 chars, then define BEHAT_MAX_CMD_LINE_OUTPUT
1003  // Example:
1004  //   define('BEHAT_MAX_CMD_LINE_OUTPUT', 120);
1005  //
1006  // Behat feature files will be distributed randomly between the processes by default. If you have timing file or want
1007  // to create timing file then define BEHAT_FEATURE_TIMING_FILE with path to timing file. It will be updated for each
1008  // run with latest time taken to execute feature.
1009  // Example:
1010  //   define('BEHAT_FEATURE_TIMING_FILE', '/PATH_TO_TIMING_FILE/timing.json');
1011  //
1012  // If you don't have timing file and want some stable distribution of features, then you can use step counts to
1013  // distribute the features. You can generate step file by executing php admin/tool/behat/cli/util.php --updatesteps
1014  // this will update step file which is defined by BEHAT_FEATURE_STEP_FILE.
1015  // Example:
1016  //   define('BEHAT_FEATURE_STEP_FILE', '/PATH_TO_FEATURE_STEP_COUNT_FILE/stepcount.json');
1017  //
1018  // Feature distribution for each process is displayed as histogram. you can disable it by setting
1019  // BEHAT_DISABLE_HISTOGRAM
1020  // Example:
1021  //   define('BEHAT_DISABLE_HISTOGRAM', true);
1022  //
1023  // Mobile app Behat testing requires this option, pointing to the url where the Ionic application is served:
1024  //   $CFG->behat_ionic_wwwroot = 'http://localhost:8100';
1025  //
1026  //=========================================================================
1027  // 12. DEVELOPER DATA GENERATOR
1028  //=========================================================================
1029  //
1030  // The developer data generator tool is intended to be used only in development or testing sites and
1031  // it's usage in production environments is not recommended; if it is used to create JMeter test plans
1032  // is even less recommended as JMeter needs to log in as site course users. JMeter needs to know the
1033  // users passwords but would be dangerous to have a default password as everybody would know it, which would
1034  // be specially dangerouse if somebody uses this tool in a production site, so in order to prevent unintended
1035  // uses of the tool and undesired accesses as well, is compulsory to set a password for the users
1036  // generated by this tool, but only in case you want to generate a JMeter test. The value should be a string.
1037  // Example:
1038  //   $CFG->tool_generator_users_password = 'examplepassword';
1039  //
1040  //=========================================================================
1041  // 13. SYSTEM PATHS (You need to set following, depending on your system)
1042  //=========================================================================
1043  // Ghostscript path.
1044  // On most Linux installs, this can be left as '/usr/bin/gs'.
1045  // On Windows it will be something like 'c:\gs\bin\gswin32c.exe' (make sure
1046  // there are no spaces in the path - if necessary copy the files 'gswin32c.exe'
1047  // and 'gsdll32.dll' to a new folder without a space in the path)
1048  //      $CFG->pathtogs = '/usr/bin/gs';
1049  //
1050  // Path to PHP CLI.
1051  // Probably something like /usr/bin/php. If you enter this, cron scripts can be
1052  // executed from admin web interface.
1053  // $CFG->pathtophp = '';
1054  //
1055  // Path to du.
1056  // Probably something like /usr/bin/du. If you enter this, pages that display
1057  // directory contents will run much faster for directories with a lot of files.
1058  //      $CFG->pathtodu = '';
1059  //
1060  // Path to aspell.
1061  // To use spell-checking within the editor, you MUST have aspell 0.50 or later
1062  // installed on your server, and you must specify the correct path to access the
1063  // aspell binary. On Unix/Linux systems, this path is usually /usr/bin/aspell,
1064  // but it might be something else.
1065  //      $CFG->aspellpath = '';
1066  //
1067  // Path to dot.
1068  // Probably something like /usr/bin/dot. To be able to generate graphics from
1069  // DOT files, you must have installed the dot executable and point to it here.
1070  // Note that, for now, this only used by the profiling features
1071  // (Development->Profiling) built into Moodle.
1072  //      $CFG->pathtodot = '';
1073  //
1074  // Path to unoconv.
1075  // Probably something like /usr/bin/unoconv. Used as a fallback to convert between document formats.
1076  // Unoconv is used convert between file formats supported by LibreOffice.
1077  // Use a recent version of unoconv ( >= 0.7 ), older versions have trouble running from a webserver.
1078  //      $CFG->pathtounoconv = '';
1079  //
1080  //=========================================================================
1081  // 14. ALTERNATIVE FILE SYSTEM SETTINGS
1082  //=========================================================================
1083  //
1084  // Alternative file system.
1085  // Since 3.3 it is possible to override file_storage and file_system API and use alternative storage systems (e.g. S3,
1086  // Rackspace Cloud Files, Google Cloud Storage, Azure Storage, etc.).
1087  // To set the alternative file storage system in config.php you can use the following setting, providing the
1088  // alternative system class name that will be auto-loaded by file_storage API.
1089  //
1090  //      $CFG->alternative_file_system_class = '\\local_myfilestorage\\file_system';
1091  //
1092  //=========================================================================
1093  // 15. CAMPAIGN CONTENT
1094  //=========================================================================
1095  //
1096  // We have added a campaign content to the notifications page, in case you want to hide that from your site you just
1097  // need to set showcampaigncontent setting to false.
1098  //
1099  //      $CFG->showcampaigncontent = true;
1100  //
1101  //=========================================================================
1102  // 16. ALTERNATIVE CACHE CONFIG SETTINGS
1103  //=========================================================================
1104  //
1105  // Alternative cache config.
1106  // Since 3.10 it is possible to override the cache_factory class with an alternative caching factory.
1107  // This overridden factory can provide alternative classes for caching such as cache_config,
1108  // cache_config_writer and core_cache\local\administration_display_helper.
1109  // The autoloaded factory class name can be specified to use.
1110  //
1111  //      $CFG->alternative_cache_factory_class = 'tool_alternativecache_cache_factory';
1112  //
1113  //=========================================================================
1114  // 17. SCHEDULED TASK OVERRIDES
1115  //=========================================================================
1116  //
1117  // It is now possible to define scheduled tasks directly within config.
1118  // The overridden value will take precedence over the values that have been set VIA the UI from the
1119  // next time the task is run.
1120  //
1121  // Tasks are configured as an array of tasks that can override a task's schedule, as well as setting
1122  // the task as disabled. I.e:
1123  //
1124  //      $CFG->scheduled_tasks = [
1125  //          '\local_plugin\task\my_task' => [
1126  //              'schedule' => '*/15 0 0 0 0',
1127  //              'disabled' => 0,
1128  //          ],
1129  //      ];
1130  //
1131  // The format for the schedule definition is: '{minute} {hour} {day} {month} {dayofweek}'.
1132  //
1133  // The classname of the task also supports wildcards:
1134  //
1135  //      $CFG->scheduled_tasks = [
1136  //          '\local_plugin\*' => [
1137  //              'schedule' => '*/15 0 0 0 0',
1138  //              'disabled' => 0,
1139  //          ],
1140  //          '*' => [
1141  //              'schedule' => '0 0 0 0 0',
1142  //              'disabled' => 0,
1143  //          ],
1144  //      ];
1145  //
1146  // In this example, any task classnames matching '\local_plugin\*' would match the first rule and
1147  // use that schedule the next time the task runs. Note that even though the 'local_plugin' tasks match
1148  // the second rule as well, the highest rule takes precedence. Therefore, the second rule would be
1149  // applied to all tasks, except for tasks within '\local_plugin\'.
1150  //
1151  // When the full classname is used, this rule always takes priority over any wildcard rules.
1152  //
1153  //=========================================================================
1154  // 18. SITE ADMIN PRESETS
1155  //=========================================================================
1156  //
1157  // The site admin presets plugin has been integrated in Moodle LMS. You can use a setting in case you
1158  // want to apply a preset during the installation:
1159  //
1160  //      $CFG->setsitepresetduringinstall = 'starter';
1161  //
1162  // This setting accepts the following values:
1163  // - One of the core preset names (i.e "starter" or "full").
1164  // - The path of a valid XML preset file, that will be imported and applied. Absolute paths are recommended, to
1165  //   guarantee the file is found: i.e."MOODLEPATH/admin/presets/tests/fixtures/import_settings_plugins.xml".
1166  //
1167  // This setting is only used during the installation process. So once the Moodle site is installed, it is ignored.
1168  //
1169  //=========================================================================
1170  // 19. SERVICES AND SUPPORT CONTENT
1171  //=========================================================================
1172  //
1173  // We have added services and support content to the notifications page, in case you want to hide that from your site
1174  // you just need to set showservicesandsupportcontent setting to false.
1175  //
1176  //      $CFG->showservicesandsupportcontent = false;
1177  //
1178  //=========================================================================
1179  // ALL DONE!  To continue installation, visit your main page with a browser
1180  //=========================================================================
1181  
1182  require_once (__DIR__ . '/lib/setup.php'); // Do not edit
1183  
1184  // There is no php closing tag in this file,
1185  // it is intentional because it prevents trailing whitespace problems!