weekly release 3.4.6+
[moodle.git] / config-dist.php
blobe817c53675c3d44d60a1fa0dbd3dacca1a37b2f9
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();
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. //
41 $CFG->dbtype = 'pgsql'; // 'pgsql', 'mariadb', 'mysqli', 'mssql', '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 // 'fetchbuffersize' => 100000, // On PostgreSQL, this option sets a limit
74 // on the number of rows that are fetched into
75 // memory when doing a large recordset query
76 // (e.g. search indexing).
77 // By default, this feature is disabled in
78 // Moodle 3.4, using a value of zero. In Moodle
79 // 3.5 and up the feature is enabled by default
80 // with a buffer size of 100000.
81 // Uncomment and set a positive value to enable it,
82 // noting that you need to keep it to zero
83 // if you are using pg_bouncer in 'transaction'
84 // mode (it is fine in 'session' mode).
88 //=========================================================================
89 // 2. WEB SITE LOCATION
90 //=========================================================================
91 // Now you need to tell Moodle where it is located. Specify the full
92 // web address to where moodle has been installed. If your web site
93 // is accessible via multiple URLs then choose the most natural one
94 // that your students would use. Do not include a trailing slash
96 // If you need both intranet and Internet access please read
97 // http://docs.moodle.org/en/masquerading
99 $CFG->wwwroot = 'http://example.com/moodle';
102 //=========================================================================
103 // 3. DATA FILES LOCATION
104 //=========================================================================
105 // Now you need a place where Moodle can save uploaded files. This
106 // directory should be readable AND WRITEABLE by the web server user
107 // (usually 'nobody' or 'apache'), but it should not be accessible
108 // directly via the web.
110 // - On hosting systems you might need to make sure that your "group" has
111 // no permissions at all, but that "others" have full permissions.
113 // - On Windows systems you might specify something like 'c:\moodledata'
115 $CFG->dataroot = '/home/example/moodledata';
118 //=========================================================================
119 // 4. DATA FILES PERMISSIONS
120 //=========================================================================
121 // The following parameter sets the permissions of new directories
122 // created by Moodle within the data directory. The format is in
123 // octal format (as used by the Unix utility chmod, for example).
124 // The default is usually OK, but you may want to change it to 0750
125 // if you are concerned about world-access to the files (you will need
126 // to make sure the web server process (eg Apache) can access the files.
127 // NOTE: the prefixed 0 is important, and don't use quotes.
129 $CFG->directorypermissions = 02777;
132 //=========================================================================
133 // 5. DIRECTORY LOCATION (most people can just ignore this setting)
134 //=========================================================================
135 // A very few webhosts use /admin as a special URL for you to access a
136 // control panel or something. Unfortunately this conflicts with the
137 // standard location for the Moodle admin pages. You can work around this
138 // by renaming the admin directory in your installation, and putting that
139 // new name here. eg "moodleadmin". This should fix all admin links in Moodle.
140 // After any change you need to visit your new admin directory
141 // and purge all caches.
143 $CFG->admin = 'admin';
146 //=========================================================================
147 // 6. OTHER MISCELLANEOUS SETTINGS (ignore these for new installations)
148 //=========================================================================
150 // These are additional tweaks for which no GUI exists in Moodle yet.
152 // Starting in PHP 5.3 administrators should specify default timezone
153 // in PHP.ini, you can also specify it here if needed.
154 // See details at: http://php.net/manual/en/function.date-default-timezone-set.php
155 // List of time zones at: http://php.net/manual/en/timezones.php
156 // date_default_timezone_set('Australia/Perth');
158 // Change the key pair lifetime for Moodle Networking
159 // The default is 28 days. You would only want to change this if the key
160 // was not getting regenerated for any reason. You would probably want
161 // make it much longer. Note that you'll need to delete and manually update
162 // any existing key.
163 // $CFG->mnetkeylifetime = 28;
165 // Not recommended: Set the following to true to allow the use
166 // off non-Moodle standard characters in usernames.
167 // $CFG->extendedusernamechars = true;
169 // Allow user passwords to be included in backup files. Very dangerous
170 // setting as far as it publishes password hashes that can be unencrypted
171 // if the backup file is publicy available. Use it only if you can guarantee
172 // that all your backup files remain only privacy available and are never
173 // shared out from your site/institution!
174 // $CFG->includeuserpasswordsinbackup = true;
176 // Completely disable user creation when restoring a course, bypassing any
177 // permissions granted via roles and capabilities. Enabling this setting
178 // results in the restore process stopping when a user attempts to restore a
179 // course requiring users to be created.
180 // $CFG->disableusercreationonrestore = true;
182 // Keep the temporary directories used by backup and restore without being
183 // deleted at the end of the process. Use it if you want to debug / view
184 // all the information stored there after the process has ended. Note that
185 // those directories may be deleted (after some ttl) both by cron and / or
186 // by new backup / restore invocations.
187 // $CFG->keeptempdirectoriesonbackup = true;
189 // Modify the restore process in order to force the "user checks" to assume
190 // that the backup originated from a different site, so detection of matching
191 // users is performed with different (more "relaxed") rules. Note that this is
192 // only useful if the backup file has been created using Moodle < 1.9.4 and the
193 // site has been rebuilt from scratch using backup files (not the best way btw).
194 // If you obtain user conflicts on restore, rather than enabling this setting
195 // permanently, try restoring the backup on a different site, back it up again
196 // and then restore on the target server.
197 // $CFG->forcedifferentsitecheckingusersonrestore = true;
199 // Force the backup system to continue to create backups in the legacy zip
200 // format instead of the new tgz format. Does not affect restore, which
201 // auto-detects the underlying file format.
202 // $CFG->usezipbackups = true;
204 // Prevent stats processing and hide the GUI
205 // $CFG->disablestatsprocessing = true;
207 // Setting this to true will enable admins to edit any post at any time
208 // $CFG->admineditalways = true;
210 // These variables define DEFAULT block variables for new courses
211 // If this one is set it overrides all others and is the only one used.
212 // $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
214 // These variables define the specific settings for defined course formats.
215 // They override any settings defined in the formats own config file.
216 // $CFG->defaultblocks_site = 'site_main_menu,course_list:course_summary,calendar_month';
217 // $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,course_list';
218 // $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
219 // $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
221 // These blocks are used when no other default setting is found.
222 // $CFG->defaultblocks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
224 // You can specify a different class to be created for the $PAGE global, and to
225 // compute which blocks appear on each page. However, I cannot think of any good
226 // reason why you would need to change that. It just felt wrong to hard-code the
227 // the class name. You are strongly advised not to use these to settings unless
228 // you are absolutely sure you know what you are doing.
229 // $CFG->moodlepageclass = 'moodle_page';
230 // $CFG->moodlepageclassfile = "$CFG->dirroot/local/myplugin/mypageclass.php";
231 // $CFG->blockmanagerclass = 'block_manager';
232 // $CFG->blockmanagerclassfile = "$CFG->dirroot/local/myplugin/myblockamanagerclass.php";
234 // Seconds for files to remain in caches. Decrease this if you are worried
235 // about students being served outdated versions of uploaded files.
236 // $CFG->filelifetime = 60*60*6;
238 // Some web servers can offload the file serving from PHP process,
239 // comment out one the following options to enable it in Moodle:
240 // $CFG->xsendfile = 'X-Sendfile'; // Apache {@see https://tn123.org/mod_xsendfile/}
241 // $CFG->xsendfile = 'X-LIGHTTPD-send-file'; // Lighttpd {@see http://redmine.lighttpd.net/projects/lighttpd/wiki/X-LIGHTTPD-send-file}
242 // $CFG->xsendfile = 'X-Accel-Redirect'; // Nginx {@see http://wiki.nginx.org/XSendfile}
243 // If your X-Sendfile implementation (usually Nginx) uses directory aliases specify them
244 // in the following array setting:
245 // $CFG->xsendfilealiases = array(
246 // '/dataroot/' => $CFG->dataroot,
247 // '/cachedir/' => '/var/www/moodle/cache', // for custom $CFG->cachedir locations
248 // '/localcachedir/' => '/var/local/cache', // for custom $CFG->localcachedir locations
249 // '/tempdir/' => '/var/www/moodle/temp', // for custom $CFG->tempdir locations
250 // '/filedir' => '/var/www/moodle/filedir', // for custom $CFG->filedir locations
251 // );
253 // YUI caching may be sometimes improved by slasharguments:
254 // $CFG->yuislasharguments = 1;
255 // Some servers may need a special rewrite rule to work around internal path length limitations:
256 // RewriteRule (^.*/theme/yui_combo\.php)(/.*) $1?file=$2
259 // Following settings may be used to select session driver, uncomment only one of the handlers.
260 // Database session handler (not compatible with MyISAM):
261 // $CFG->session_handler_class = '\core\session\database';
262 // $CFG->session_database_acquire_lock_timeout = 120;
264 // File session handler (file system locking required):
265 // $CFG->session_handler_class = '\core\session\file';
266 // $CFG->session_file_save_path = $CFG->dataroot.'/sessions';
268 // Memcached session handler (requires memcached server and extension):
269 // $CFG->session_handler_class = '\core\session\memcached';
270 // $CFG->session_memcached_save_path = '127.0.0.1:11211';
271 // $CFG->session_memcached_prefix = 'memc.sess.key.';
272 // $CFG->session_memcached_acquire_lock_timeout = 120;
273 // $CFG->session_memcached_lock_expire = 7200; // Ignored if PECL memcached is below version 2.2.0
274 // $CFG->session_memcached_lock_retry_sleep = 150; // Spin-lock retry sleeptime (msec). Only effective
275 // // for tuning php-memcached 3.0.x (PHP 7)
277 // Redis session handler (requires redis server and redis extension):
278 // $CFG->session_handler_class = '\core\session\redis';
279 // $CFG->session_redis_host = '127.0.0.1';
280 // $CFG->session_redis_port = 6379; // Optional.
281 // $CFG->session_redis_database = 0; // Optional, default is db 0.
282 // $CFG->session_redis_auth = ''; // Optional, default is don't set one.
283 // $CFG->session_redis_prefix = ''; // Optional, default is don't set one.
284 // $CFG->session_redis_acquire_lock_timeout = 120;
285 // $CFG->session_redis_lock_expire = 7200;
286 // Use the igbinary serializer instead of the php default one. Note that phpredis must be compiled with
287 // igbinary support to make the setting to work. Also, if you change the serializer you have to flush the database!
288 // $CFG->session_redis_serializer_use_igbinary = false; // Optional, default is PHP builtin serializer.
290 // Memcache session handler (requires memcached server and memcache extension):
291 // $CFG->session_handler_class = '\core\session\memcache';
292 // $CFG->session_memcache_save_path = '127.0.0.1:11211';
293 // $CFG->session_memcache_acquire_lock_timeout = 120;
294 // ** NOTE: Memcache extension has less features than memcached and may be
295 // less reliable. Use memcached where possible or if you encounter
296 // session problems. **
298 // Please be aware that when selecting either Memcached or Memcache for sessions that it is advised to use a dedicated
299 // memcache server. The memcache and memcached extensions do not provide isolated environments for individual uses.
300 // Using the same server for other purposes (MUC for example) can lead to sessions being prematurely removed should
301 // the other uses of the server purge the cache.
303 // Following setting allows you to alter how frequently is timemodified updated in sessions table.
304 // $CFG->session_update_timemodified_frequency = 20; // In seconds.
306 // If this setting is set to true, then Moodle will track the IP of the
307 // current user to make sure it hasn't changed during a session. This
308 // will prevent the possibility of sessions being hijacked via XSS, but it
309 // may break things for users coming using proxies that change all the time,
310 // like AOL.
311 // $CFG->tracksessionip = true;
313 // The following lines are for handling email bounces.
314 // $CFG->handlebounces = true;
315 // $CFG->minbounces = 10;
316 // $CFG->bounceratio = .20;
317 // The next lines are needed both for bounce handling and any other email to module processing.
318 // mailprefix must be EXACTLY four characters.
319 // Uncomment and customise this block for Postfix
320 // $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix.
321 // $CFG->mailprefix = 'mdl-'; // - is the separator for qmail
322 // $CFG->maildomain = 'youremaildomain.com';
324 // Enable when setting up advanced reverse proxy load balancing configurations,
325 // it may be also necessary to enable this when using port forwarding.
326 // $CFG->reverseproxy = true;
328 // Enable when using external SSL appliance for performance reasons.
329 // Please note that site may be accessible via http: or https:, but not both!
330 // $CFG->sslproxy = true;
332 // This setting will cause the userdate() function not to fix %d in
333 // date strings, and just let them show with a zero prefix.
334 // $CFG->nofixday = true;
336 // This setting will make some graphs (eg user logs) use lines instead of bars
337 // $CFG->preferlinegraphs = true;
339 // This setting allows you to specify a class to rewrite outgoing urls
340 // enabling 'clean urls' in conjunction with an apache / nginx handler.
341 // The handler must implement \core\output\url_rewriter.
342 // $CFG->urlrewriteclass = '\local_cleanurls\url_rewriter';
344 // Enabling this will allow custom scripts to replace existing moodle scripts.
345 // For example: if $CFG->customscripts/course/view.php exists then
346 // it will be used instead of $CFG->wwwroot/course/view.php
347 // At present this will only work for files that include config.php and are called
348 // as part of the url (index.php is implied).
349 // Some examples are:
350 // http://my.moodle.site/course/view.php
351 // http://my.moodle.site/index.php
352 // http://my.moodle.site/admin (index.php implied)
353 // Custom scripts should not include config.php
354 // Warning: Replacing standard moodle scripts may pose security risks and/or may not
355 // be compatible with upgrades. Use this option only if you are aware of the risks
356 // involved.
357 // Specify the full directory path to the custom scripts
358 // $CFG->customscripts = '/home/example/customscripts';
360 // Performance profiling
362 // If you set Debug to "Yes" in the Configuration->Variables page some
363 // performance profiling data will show up on your footer (in default theme).
364 // With these settings you get more granular control over the capture
365 // and printout of the data
367 // Capture performance profiling data
368 // define('MDL_PERF' , true);
370 // Capture additional data from DB
371 // define('MDL_PERFDB' , true);
373 // Print to log (for passive profiling of production servers)
374 // define('MDL_PERFTOLOG' , true);
376 // Print to footer (works with the default theme)
377 // define('MDL_PERFTOFOOT', true);
379 // Enable earlier profiling that causes more code to be covered
380 // on every request (db connections, config load, other inits...).
381 // Requires extra configuration to be defined in config.php like:
382 // profilingincluded, profilingexcluded, profilingautofrec,
383 // profilingallowme, profilingallowall, profilinglifetime
384 // $CFG->earlyprofilingenabled = true;
386 // Force displayed usernames
387 // A little hack to anonymise user names for all students. If you set these
388 // then all non-teachers will always see these for every person.
389 // $CFG->forcefirstname = 'Bruce';
390 // $CFG->forcelastname = 'Simpson';
392 // The following setting will turn on username logging into Apache log. For full details regarding setting
393 // up of this function please refer to the install section of the document.
394 // $CFG->apacheloguser = 0; // Turn this feature off. Default value.
395 // $CFG->apacheloguser = 1; // Log user id.
396 // $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
397 // $CFG->apacheloguser = 3; // Log username.
398 // To get the values logged in Apache's log, add to your httpd.conf
399 // the following statements. In the General part put:
400 // LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat
401 // And in the part specific to your Moodle install / virtualhost:
402 // CustomLog "/your/path/to/log" moodleformat
404 // Alternatively for other webservers such as nginx, you can instead have the username sent via a http header
405 // 'X-MOODLEUSER' which can be saved in the logfile and then stripped out before being sent to the browser:
406 // $CFG->headerloguser = 0; // Turn this feature off. Default value.
407 // $CFG->headerloguser = 1; // Log user id.
408 // $CFG->headerloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
409 // $CFG->headerloguser = 3; // Log username.
411 // CAUTION: Use of this option will expose usernames in the Apache / nginx log,
412 // If you are going to publish your log, or the output of your web stats analyzer
413 // this will weaken the security of your website.
415 // Email database connection errors to someone. If Moodle cannot connect to the
416 // database, then email this address with a notice.
418 // $CFG->emailconnectionerrorsto = 'your@emailaddress.com';
420 // Set the priority of themes from highest to lowest. This is useful (for
421 // example) in sites where the user theme should override all other theme
422 // settings for accessibility reasons. You can also disable types of themes
423 // (other than site) by removing them from the array. The default setting is:
424 // $CFG->themeorder = array('course', 'category', 'session', 'user', 'site');
425 // NOTE: course, category, session, user themes still require the
426 // respective settings to be enabled
428 // It is possible to add extra themes directory stored outside of $CFG->dirroot.
429 // This local directory does not have to be accessible from internet.
431 // $CFG->themedir = '/location/of/extra/themes';
433 // It is possible to specify different cache and temp directories, use local fast filesystem
434 // for normal web servers. Server clusters MUST use shared filesystem for cachedir!
435 // Localcachedir is intended for server clusters, it does not have to be shared by cluster nodes.
436 // The directories must not be accessible via web.
438 // $CFG->tempdir = '/var/www/moodle/temp'; // Directory MUST BE SHARED by all clsuter nodes.
439 // $CFG->cachedir = '/var/www/moodle/cache'; // Directory MUST BE SHARED by all cluster nodes, locking required.
440 // $CFG->localcachedir = '/var/local/cache'; // Intended for local node caching.
442 // Some filesystems such as NFS may not support file locking operations.
443 // Locking resolves race conditions and is strongly recommended for production servers.
444 // $CFG->preventfilelocking = false;
446 // Site default language can be set via standard administration interface. If you
447 // want to have initial error messages for eventual database connection problems
448 // localized too, you have to set your language code here.
450 // $CFG->lang = 'yourlangcode'; // for example 'cs'
452 // When Moodle is about to perform an intensive operation it raises PHP's memory
453 // limit. The following setting should be used on large sites to set the raised
454 // memory limit to something higher.
455 // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G
457 // $CFG->extramemorylimit = '1024M';
459 // Moodle 2.4 introduced a new cache API.
460 // The cache API stores a configuration file within the Moodle data directory and
461 // uses that rather than the database in order to function in a stand-alone manner.
462 // Using altcacheconfigpath you can change the location where this config file is
463 // looked for.
464 // It can either be a directory in which to store the file, or the full path to the
465 // file if you want to take full control. Either way it must be writable by the
466 // webserver.
468 // $CFG->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php
470 // Use the following flag to completely disable the Available update notifications
471 // feature and hide it from the server administration UI.
473 // $CFG->disableupdatenotifications = true;
475 // Use the following flag to completely disable the installation of plugins
476 // (new plugins, available updates and missing dependencies) and related
477 // features (such as cancelling the plugin installation or upgrade) via the
478 // server administration web interface.
480 // $CFG->disableupdateautodeploy = true;
482 // Use the following flag to disable the warning on the system notifications page
483 // about present development libraries. This flag will not disable the warning within
484 // the security overview report. Use this flag only if you really have prohibited web
485 // access to the development libraries in your webserver configuration.
487 // $CFG->disabledevlibdirscheck = true;
489 // Use the following flag to disable modifications to scheduled tasks
490 // whilst still showing the state of tasks.
492 // $CFG->preventscheduledtaskchanges = true;
494 // As of version 2.4 Moodle serves icons as SVG images if the users browser appears
495 // to support SVG.
496 // For those wanting to control the serving of SVG images the following setting can
497 // be defined in your config.php.
498 // If it is not defined then the default (browser detection) will occur.
500 // To ensure they are always used when available:
501 // $CFG->svgicons = true;
503 // To ensure they are never used even when available:
504 // $CFG->svgicons = false;
506 // Some administration options allow setting the path to executable files. This can
507 // potentially cause a security risk. Set this option to true to disable editing
508 // those config settings via the web. They will need to be set explicitly in the
509 // config.php file
510 // $CFG->preventexecpath = true;
512 // Use the following flag to set userid for noreply user. If not set then moodle will
513 // create dummy user and use -ve value as user id.
514 // $CFG->noreplyuserid = -10;
516 // As of version 2.6 Moodle supports admin to set support user. If not set, all mails
517 // will be sent to supportemail.
518 // $CFG->supportuserid = -20;
520 // Moodle 2.7 introduces a locking api for critical tasks (e.g. cron).
521 // The default locking system to use is DB locking for Postgres, and file locking for
522 // MySQL, Oracle and SQLServer. If $CFG->preventfilelocking is set, then the default
523 // will always be DB locking. It can be manually set to one of the lock
524 // factory classes listed below, or one of your own custom classes implementing the
525 // \core\lock\lock_factory interface.
527 // $CFG->lock_factory = "auto";
529 // The list of available lock factories is:
531 // "\\core\\lock\\file_lock_factory" - File locking
532 // Uses lock files stored by default in the dataroot. Whether this
533 // works on clusters depends on the file system used for the dataroot.
535 // "\\core\\lock\\db_record_lock_factory" - DB locking based on table rows.
537 // "\\core\\lock\\postgres_lock_factory" - DB locking based on postgres advisory locks.
539 // Settings used by the lock factories
541 // Location for lock files used by the File locking factory. This must exist
542 // on a shared file system that supports locking.
543 // $CFG->lock_file_root = $CFG->dataroot . '/lock';
545 // Moodle 2.9 allows administrators to customise the list of supported file types.
546 // To add a new filetype or override the definition of an existing one, set the
547 // customfiletypes variable like this:
549 // $CFG->customfiletypes = array(
550 // (object)array(
551 // 'extension' => 'frog',
552 // 'icon' => 'archive',
553 // 'type' => 'application/frog',
554 // 'customdescription' => 'Amphibian-related file archive'
555 // )
556 // );
558 // The extension, icon, and type fields are required. The icon field can refer to
559 // any icon inside the pix/f folder. You can also set the customdescription field
560 // (shown above) and (for advanced use) the groups, string, and defaulticon fields.
562 // Upgrade key
564 // If the upgrade key is defined here, then the value must be provided every time
565 // the site is being upgraded though the web interface, regardless of whether the
566 // administrator is logged in or not. This prevents anonymous access to the upgrade
567 // screens where the real authentication and authorization mechanisms can not be
568 // relied on.
570 // It is strongly recommended to use a value different from your real account
571 // password.
573 // $CFG->upgradekey = 'put_some_password-like_value_here';
575 // Font used in exported PDF files. When generating a PDF, Moodle embeds a subset of
576 // the font in the PDF file so it will be readable on the widest range of devices.
577 // The default font is 'freesans' which is part of the GNU FreeFont collection.
579 // $CFG->pdfexportfont = 'freesans';
581 // Disable login token validation for login pages. Login token validation is enabled
582 // by default unless $CFG->alternateloginurl is set.
584 // $CFG->disablelogintoken = true;
586 //=========================================================================
587 // 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
588 //=========================================================================
590 // Force a debugging mode regardless the settings in the site administration
591 // @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
592 // @ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
593 // $CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
594 // $CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS!
596 // You can specify a comma separated list of user ids that that always see
597 // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
598 // for these users only.
599 // $CFG->debugusers = '2';
601 // Prevent theme caching
602 // $CFG->themedesignermode = true; // NOT FOR PRODUCTION SERVERS!
604 // Enable verbose debug information during fetching of email messages from IMAP server.
605 // $CFG->debugimap = true;
607 // Prevent JS caching
608 // $CFG->cachejs = false; // NOT FOR PRODUCTION SERVERS!
610 // Restrict which YUI logging statements are shown in the browser console.
611 // For details see the upstream documentation:
612 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logInclude
613 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logExclude
614 // $CFG->yuiloginclude = array(
615 // 'moodle-core-dock-loader' => true,
616 // 'moodle-course-categoryexpander' => true,
617 // );
618 // $CFG->yuilogexclude = array(
619 // 'moodle-core-dock' => true,
620 // 'moodle-core-notification' => true,
621 // );
623 // Set the minimum log level for YUI logging statements.
624 // For details see the upstream documentation:
625 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logLevel
626 // $CFG->yuiloglevel = 'debug';
628 // Prevent core_string_manager application caching
629 // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!
631 // When working with production data on test servers, no emails or other messages
632 // should ever be send to real users
633 // $CFG->noemailever = true; // NOT FOR PRODUCTION SERVERS!
635 // Divert all outgoing emails to this address to test and debug emailing features
636 // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
638 // Except for certain email addresses you want to let through for testing. Accepts
639 // a comma separated list of regexes.
640 // $CFG->divertallemailsexcept = 'tester@dev.com, fred(\+.*)?@example.com'; // NOT FOR PRODUCTION SERVERS!
642 // Uncomment if you want to allow empty comments when modifying install.xml files.
643 // $CFG->xmldbdisablecommentchecking = true; // NOT FOR PRODUCTION SERVERS!
645 // Since 2.0 sql queries are not shown during upgrade by default.
646 // Please note that this setting may produce very long upgrade page on large sites.
647 // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!
649 // Add SQL queries to the output of cron, just before their execution
650 // $CFG->showcronsql = true;
652 // Force developer level debug and add debug info to the output of cron
653 // $CFG->showcrondebugging = true;
655 //=========================================================================
656 // 8. FORCED SETTINGS
657 //=========================================================================
658 // It is possible to specify normal admin settings here, the point is that
659 // they can not be changed through the standard admin settings pages any more.
661 // Core settings are specified directly via assignment to $CFG variable.
662 // Example:
663 // $CFG->somecoresetting = 'value';
665 // Plugin settings have to be put into a special array.
666 // Example:
667 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'secondsetting' => 'othervalue'),
668 // 'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));
669 // Module default settings with advanced/locked checkboxes can be set too. To do this, add
670 // an extra config with '_adv' or '_locked' as a suffix and set the value to true or false.
671 // Example:
672 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'settingname_locked' => true, 'settingname_adv' => true));
674 //=========================================================================
675 // 9. PHPUNIT SUPPORT
676 //=========================================================================
677 // $CFG->phpunit_prefix = 'phpu_';
678 // $CFG->phpunit_dataroot = '/home/example/phpu_moodledata';
679 // $CFG->phpunit_directorypermissions = 02777; // optional
680 // $CFG->phpunit_profilingenabled = true; // optional to profile PHPUnit runs.
683 //=========================================================================
684 // 10. SECRET PASSWORD SALT
685 //=========================================================================
686 // A site-wide password salt is no longer used in new installations.
687 // If upgrading from 2.6 or older, keep all existing salts in config.php file.
689 // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1';
691 // You may also have some alternative salts to allow migration from previously
692 // used salts.
694 // $CFG->passwordsaltalt1 = '';
695 // $CFG->passwordsaltalt2 = '';
696 // $CFG->passwordsaltalt3 = '';
697 // ....
698 // $CFG->passwordsaltalt19 = '';
699 // $CFG->passwordsaltalt20 = '';
702 //=========================================================================
703 // 11. BEHAT SUPPORT
704 //=========================================================================
705 // Behat test site needs a unique www root, data directory and database prefix:
707 // $CFG->behat_wwwroot = 'http://127.0.0.1/moodle';
708 // $CFG->behat_prefix = 'bht_';
709 // $CFG->behat_dataroot = '/home/example/bht_moodledata';
711 // You can override default Moodle configuration for Behat and add your own
712 // params; here you can add more profiles, use different Mink drivers than Selenium...
713 // These params would be merged with the default Moodle behat.yml, giving priority
714 // to the ones specified here. The array format is YAML, following the Behat
715 // params hierarchy. More info: http://docs.behat.org/guides/7.config.html
716 // Example:
717 // $CFG->behat_config = array(
718 // 'Mac-Firefox' => array(
719 // 'suites' => array (
720 // 'default' => array(
721 // 'filters' => array(
722 // 'tags' => '~@_file_upload'
723 // ),
724 // ),
725 // ),
726 // 'extensions' => array(
727 // 'Behat\MinkExtension' => array(
728 // 'selenium2' => array(
729 // 'browser' => 'firefox',
730 // 'capabilities' => array(
731 // 'platform' => 'OS X 10.6',
732 // 'version' => 20
733 // )
734 // )
735 // )
736 // )
737 // ),
738 // 'Mac-Safari' => array(
739 // 'extensions' => array(
740 // 'Behat\MinkExtension' => array(
741 // 'selenium2' => array(
742 // 'browser' => 'safari',
743 // 'capabilities' => array(
744 // 'platform' => 'OS X 10.8',
745 // 'version' => 6
746 // )
747 // )
748 // )
749 // )
750 // )
751 // );
752 // You can also use the following config to override default Moodle configuration for Behat.
753 // This config is limited to default suite and will be supported in later versions.
754 // It will have precedence over $CFG->behat_config.
755 // $CFG->behat_profiles = array(
756 // 'phantomjs' => array(
757 // 'browser' => 'phantomjs',
758 // 'tags' => '~@_file_upload&&~@_alert&&~@_bug_phantomjs',
759 // 'wd_host' => 'http://127.0.0.1:4443/wd/hub',
760 // 'capabilities' => array(
761 // 'platform' => 'Linux',
762 // 'version' => 2.1
763 // )
764 // ),
765 // );
767 // You can force the browser session (not user's sessions) to restart after N seconds. This could
768 // be useful if you are using a cloud-based service with time restrictions in the browser side.
769 // Setting this value the browser session that Behat is using will be restarted. Set the time in
770 // seconds. Is not recommended to use this setting if you don't explicitly need it.
771 // Example:
772 // $CFG->behat_restart_browser_after = 7200; // Restarts the browser session after 2 hours
774 // All this page's extra Moodle settings are compared against a white list of allowed settings
775 // (the basic and behat_* ones) to avoid problems with production environments. This setting can be
776 // used to expand the default white list with an array of extra settings.
777 // Example:
778 // $CFG->behat_extraallowedsettings = array('somecoresetting', ...);
780 // You should explicitly allow the usage of the deprecated behat steps, otherwise an exception will
781 // be thrown when using them. The setting is disabled by default.
782 // Example:
783 // $CFG->behat_usedeprecated = true;
785 // Including feature files from directories outside the dirroot is possible if required. The setting
786 // requires that the running user has executable permissions on all parent directories in the paths.
787 // Example:
788 // $CFG->behat_additionalfeatures = array('/home/developer/code/wipfeatures');
790 // You can make behat save several dumps when a scenario fails. The dumps currently saved are:
791 // * a dump of the DOM in it's state at the time of failure; and
792 // * a screenshot (JavaScript is required for the screenshot functionality, so not all browsers support this option)
793 // Example:
794 // $CFG->behat_faildump_path = '/my/path/to/save/failure/dumps';
796 // You can specify db, selenium wd_host etc. for behat parallel run by setting following variable.
797 // Example:
798 // $CFG->behat_parallel_run = array (
799 // array (
800 // 'dbtype' => 'mysqli',
801 // 'dblibrary' => 'native',
802 // 'dbhost' => 'localhost',
803 // 'dbname' => 'moodletest',
804 // 'dbuser' => 'moodle',
805 // 'dbpass' => 'moodle',
806 // 'behat_prefix' => 'mdl_',
807 // 'wd_host' => 'http://127.0.0.1:4444/wd/hub',
808 // 'behat_wwwroot' => 'http://127.0.0.1/moodle',
809 // 'behat_dataroot' => '/home/example/bht_moodledata'
810 // ),
811 // );
813 // To change name of behat parallel run site, define BEHAT_PARALLEL_SITE_NAME and parallel run sites will be suffixed
814 // with this value
815 // Example:
816 // define('BEHAT_PARALLEL_SITE_NAME', 'behatparallelsite');
818 // Command line output for parallel behat install is limited to 80 chars, if you are installing more then 4 sites and
819 // want to expand output to more then 80 chars, then define BEHAT_MAX_CMD_LINE_OUTPUT
820 // Example:
821 // define('BEHAT_MAX_CMD_LINE_OUTPUT', 120);
823 // Behat feature files will be distributed randomly between the processes by default. If you have timing file or want
824 // to create timing file then define BEHAT_FEATURE_TIMING_FILE with path to timing file. It will be updated for each
825 // run with latest time taken to execute feature.
826 // Example:
827 // define('BEHAT_FEATURE_TIMING_FILE', '/PATH_TO_TIMING_FILE/timing.json');
829 // If you don't have timing file and want some stable distribution of features, then you can use step counts to
830 // distribute the features. You can generate step file by executing php admin/tool/behat/cli/util.php --updatesteps
831 // this will update step file which is defined by BEHAT_FEATURE_STEP_FILE.
832 // Example:
833 // define('BEHAT_FEATURE_STEP_FILE', '/PATH_TO_FEATURE_STEP_COUNT_FILE/stepcount.json');
835 // Feature distribution for each process is displayed as histogram. you can disable it by setting
836 // BEHAT_DISABLE_HISTOGRAM
837 // Example:
838 // define('BEHAT_DISABLE_HISTOGRAM', true);
840 //=========================================================================
841 // 12. DEVELOPER DATA GENERATOR
842 //=========================================================================
844 // The developer data generator tool is intended to be used only in development or testing sites and
845 // it's usage in production environments is not recommended; if it is used to create JMeter test plans
846 // is even less recommended as JMeter needs to log in as site course users. JMeter needs to know the
847 // users passwords but would be dangerous to have a default password as everybody would know it, which would
848 // be specially dangerouse if somebody uses this tool in a production site, so in order to prevent unintended
849 // uses of the tool and undesired accesses as well, is compulsory to set a password for the users
850 // generated by this tool, but only in case you want to generate a JMeter test. The value should be a string.
851 // Example:
852 // $CFG->tool_generator_users_password = 'examplepassword';
854 //=========================================================================
855 // 13. SYSTEM PATHS (You need to set following, depending on your system)
856 //=========================================================================
857 // Ghostscript path.
858 // On most Linux installs, this can be left as '/usr/bin/gs'.
859 // On Windows it will be something like 'c:\gs\bin\gswin32c.exe' (make sure
860 // there are no spaces in the path - if necessary copy the files 'gswin32c.exe'
861 // and 'gsdll32.dll' to a new folder without a space in the path)
862 // $CFG->pathtogs = '/usr/bin/gs';
864 // Path to du.
865 // Probably something like /usr/bin/du. If you enter this, pages that display
866 // directory contents will run much faster for directories with a lot of files.
867 // $CFG->pathtodu = '';
869 // Path to aspell.
870 // To use spell-checking within the editor, you MUST have aspell 0.50 or later
871 // installed on your server, and you must specify the correct path to access the
872 // aspell binary. On Unix/Linux systems, this path is usually /usr/bin/aspell,
873 // but it might be something else.
874 // $CFG->aspellpath = '';
876 // Path to dot.
877 // Probably something like /usr/bin/dot. To be able to generate graphics from
878 // DOT files, you must have installed the dot executable and point to it here.
879 // Note that, for now, this only used by the profiling features
880 // (Development->Profiling) built into Moodle.
881 // $CFG->pathtodot = '';
883 // Path to unoconv.
884 // Probably something like /usr/bin/unoconv. Used as a fallback to convert between document formats.
885 // Unoconv is used convert between file formats supported by LibreOffice.
886 // Use a recent version of unoconv ( >= 0.7 ), older versions have trouble running from a webserver.
887 // $CFG->pathtounoconv = '';
889 //=========================================================================
890 // 14. ALTERNATIVE FILE SYSTEM SETTINGS
891 //=========================================================================
893 // Alternative file system.
894 // Since 3.3 it is possible to override file_storage and file_system API and use alternative storage systems (e.g. S3,
895 // Rackspace Cloud Files, Google Cloud Storage, Azure Storage, etc.).
896 // To set the alternative file storage system in config.php you can use the following setting, providing the
897 // alternative system class name that will be auto-loaded by file_storage API.
899 // $CFG->alternative_file_system_class = '\\local_myfilestorage\\file_system';
901 //=========================================================================
902 // ALL DONE! To continue installation, visit your main page with a browser
903 //=========================================================================
905 require_once(__DIR__ . '/lib/setup.php'); // Do not edit
907 // There is no php closing tag in this file,
908 // it is intentional because it prevents trailing whitespace problems!