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