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