Search moodle.org's
Developer Documentation

See Release Notes

  • Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
  • Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).
  • PHP version: minimum PHP 7.3.0 Note: minimum PHP version has increased since Moodle 3.10. PHP 7.4.x is supported too.
/ -> config-dist.php (source)

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

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