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