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', '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
65 //=========================================================================
66 // 2. WEB SITE LOCATION
67 //=========================================================================
68 // Now you need to tell Moodle where it is located. Specify the full
69 // web address to where moodle has been installed. If your web site
70 // is accessible via multiple URLs then choose the most natural one
71 // that your students would use. Do not include a trailing slash
73 // If you need both intranet and Internet access please read
74 // http://docs.moodle.org/en/masquerading
76 $CFG->wwwroot
= 'http://example.com/moodle';
79 //=========================================================================
80 // 3. DATA FILES LOCATION
81 //=========================================================================
82 // Now you need a place where Moodle can save uploaded files. This
83 // directory should be readable AND WRITEABLE by the web server user
84 // (usually 'nobody' or 'apache'), but it should not be accessible
85 // directly via the web.
87 // - On hosting systems you might need to make sure that your "group" has
88 // no permissions at all, but that "others" have full permissions.
90 // - On Windows systems you might specify something like 'c:\moodledata'
92 $CFG->dataroot
= '/home/example/moodledata';
95 //=========================================================================
96 // 4. DATA FILES PERMISSIONS
97 //=========================================================================
98 // The following parameter sets the permissions of new directories
99 // created by Moodle within the data directory. The format is in
100 // octal format (as used by the Unix utility chmod, for example).
101 // The default is usually OK, but you may want to change it to 0750
102 // if you are concerned about world-access to the files (you will need
103 // to make sure the web server process (eg Apache) can access the files.
104 // NOTE: the prefixed 0 is important, and don't use quotes.
106 $CFG->directorypermissions
= 02777;
109 //=========================================================================
110 // 5. DIRECTORY LOCATION (most people can just ignore this setting)
111 //=========================================================================
112 // A very few webhosts use /admin as a special URL for you to access a
113 // control panel or something. Unfortunately this conflicts with the
114 // standard location for the Moodle admin pages. You can fix this by
115 // renaming the admin directory in your installation, and putting that
116 // new name here. eg "moodleadmin". This will fix admin links in Moodle.
118 $CFG->admin
= 'admin';
121 //=========================================================================
122 // 6. OTHER MISCELLANEOUS SETTINGS (ignore these for new installations)
123 //=========================================================================
125 // These are additional tweaks for which no GUI exists in Moodle yet.
127 // Starting in PHP 5.3 administrators should specify default timezone
128 // in PHP.ini, you can also specify it here if needed.
129 // See details at: http://php.net/manual/en/function.date-default-timezone-set.php
130 // List of time zones at: http://php.net/manual/en/timezones.php
131 // date_default_timezone_set('Australia/Perth');
133 // Change the key pair lifetime for Moodle Networking
134 // The default is 28 days. You would only want to change this if the key
135 // was not getting regenerated for any reason. You would probably want
136 // make it much longer. Note that you'll need to delete and manually update
138 // $CFG->mnetkeylifetime = 28;
140 // Allow user passwords to be included in backup files. Very dangerous
141 // setting as far as it publishes password hashes that can be unencrypted
142 // if the backup file is publicy available. Use it only if you can guarantee
143 // that all your backup files remain only privacy available and are never
144 // shared out from your site/institution!
145 // $CFG->includeuserpasswordsinbackup = true;
147 // Completely disable user creation when restoring a course, bypassing any
148 // permissions granted via roles and capabilities. Enabling this setting
149 // results in the restore process stopping when a user attempts to restore a
150 // course requiring users to be created.
151 // $CFG->disableusercreationonrestore = true;
153 // Keep the temporary directories used by backup and restore without being
154 // deleted at the end of the process. Use it if you want to debug / view
155 // all the information stored there after the process has ended. Note that
156 // those directories may be deleted (after some ttl) both by cron and / or
157 // by new backup / restore invocations.
158 // $CFG->keeptempdirectoriesonbackup = true;
160 // Modify the restore process in order to force the "user checks" to assume
161 // that the backup originated from a different site, so detection of matching
162 // users is performed with different (more "relaxed") rules. Note that this is
163 // only useful if the backup file has been created using Moodle < 1.9.4 and the
164 // site has been rebuilt from scratch using backup files (not the best way btw).
165 // If you obtain user conflicts on restore, rather than enabling this setting
166 // permanently, try restoring the backup on a different site, back it up again
167 // and then restore on the target server.
168 // $CFG->forcedifferentsitecheckingusersonrestore = true;
170 // Prevent stats processing and hide the GUI
171 // $CFG->disablestatsprocessing = true;
173 // Setting this to true will enable admins to edit any post at any time
174 // $CFG->admineditalways = true;
176 // These variables define DEFAULT block variables for new courses
177 // If this one is set it overrides all others and is the only one used.
178 // $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
180 // These variables define the specific settings for defined course formats.
181 // They override any settings defined in the formats own config file.
182 // $CFG->defaultblocks_site = 'site_main_menu,course_list:course_summary,calendar_month';
183 // $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,course_list';
184 // $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
185 // $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
187 // These blocks are used when no other default setting is found.
188 // $CFG->defaultblocks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
190 // You can specify a different class to be created for the $PAGE global, and to
191 // compute which blocks appear on each page. However, I cannot think of any good
192 // reason why you would need to change that. It just felt wrong to hard-code the
193 // the class name. You are strongly advised not to use these to settings unless
194 // you are absolutely sure you know what you are doing.
195 // $CFG->moodlepageclass = 'moodle_page';
196 // $CFG->moodlepageclassfile = "$CFG->dirroot/local/myplugin/mypageclass.php";
197 // $CFG->blockmanagerclass = 'block_manager';
198 // $CFG->blockmanagerclassfile = "$CFG->dirroot/local/myplugin/myblockamanagerclass.php";
200 // Seconds for files to remain in caches. Decrease this if you are worried
201 // about students being served outdated versions of uploaded files.
202 // $CFG->filelifetime = 86400;
204 // Some web servers can offload the file serving from PHP process,
205 // comment out one the following options to enable it in Moodle:
206 // $CFG->xsendfile = 'X-Sendfile'; // Apache {@see https://tn123.org/mod_xsendfile/}
207 // $CFG->xsendfile = 'X-LIGHTTPD-send-file'; // Lighttpd {@see http://redmine.lighttpd.net/projects/lighttpd/wiki/X-LIGHTTPD-send-file}
208 // $CFG->xsendfile = 'X-Accel-Redirect'; // Nginx {@see http://wiki.nginx.org/XSendfile}
209 // If your X-Sendfile implementation (usually Nginx) uses directory aliases specify them
210 // in the following array setting:
211 // $CFG->xsendfilealiases = array(
212 // '/dataroot/' => $CFG->dataroot,
213 // '/cachedir/' => '/var/www/moodle/cache', // for custom $CFG->cachedir locations
214 // '/tempdir/' => '/var/www/moodle/temp', // for custom $CFG->tempdir locations
215 // '/filedir' => '/var/www/moodle/filedir', // for custom $CFG->filedir locations
218 // YUI caching may be sometimes improved by slasharguments:
219 // $CFG->yuislasharguments = 1;
220 // Some servers may need a special rewrite rule to work around internal path length limitations:
221 // RewriteRule (^.*/theme/yui_combo\.php)(/.*) $1?file=$2
224 // This setting will prevent the 'My Courses' page being displayed when a student
225 // logs in. The site front page will always show the same (logged-out) view.
226 // $CFG->disablemycourses = true;
228 // By default all user sessions should be using locking, uncomment
229 // the following setting to prevent locking for guests and not-logged-in
230 // accounts. This may improve performance significantly.
231 // $CFG->sessionlockloggedinonly = 1;
233 // If this setting is set to true, then Moodle will track the IP of the
234 // current user to make sure it hasn't changed during a session. This
235 // will prevent the possibility of sessions being hijacked via XSS, but it
236 // may break things for users coming using proxies that change all the time,
238 // $CFG->tracksessionip = true;
240 // The following lines are for handling email bounces.
241 // $CFG->handlebounces = true;
242 // $CFG->minbounces = 10;
243 // $CFG->bounceratio = .20;
244 // The next lines are needed both for bounce handling and any other email to module processing.
245 // mailprefix must be EXACTLY four characters.
246 // Uncomment and customise this block for Postfix
247 // $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix.
248 // $CFG->mailprefix = 'mdl-'; // - is the separator for qmail
249 // $CFG->maildomain = 'youremaildomain.com';
251 // Enable when setting up advanced reverse proxy load balancing configurations,
252 // it may be also necessary to enable this when using port forwarding.
253 // $CFG->reverseproxy = true;
255 // Enable when using external SSL appliance for performance reasons.
256 // Please note that site may be accessible via https: or https:, but not both!
257 // $CFG->sslproxy = true;
259 // This setting will cause the userdate() function not to fix %d in
260 // date strings, and just let them show with a zero prefix.
261 // $CFG->nofixday = true;
263 // This setting will make some graphs (eg user logs) use lines instead of bars
264 // $CFG->preferlinegraphs = true;
266 // Enabling this will allow custom scripts to replace existing moodle scripts.
267 // For example: if $CFG->customscripts/course/view.php exists then
268 // it will be used instead of $CFG->wwwroot/course/view.php
269 // At present this will only work for files that include config.php and are called
270 // as part of the url (index.php is implied).
271 // Some examples are:
272 // http://my.moodle.site/course/view.php
273 // http://my.moodle.site/index.php
274 // http://my.moodle.site/admin (index.php implied)
275 // Custom scripts should not include config.php
276 // Warning: Replacing standard moodle scripts may pose security risks and/or may not
277 // be compatible with upgrades. Use this option only if you are aware of the risks
279 // Specify the full directory path to the custom scripts
280 // $CFG->customscripts = '/home/example/customscripts';
282 // Performance profiling
284 // If you set Debug to "Yes" in the Configuration->Variables page some
285 // performance profiling data will show up on your footer (in default theme).
286 // With these settings you get more granular control over the capture
287 // and printout of the data
289 // Capture performance profiling data
290 // define('MDL_PERF' , true);
292 // Capture additional data from DB
293 // define('MDL_PERFDB' , true);
295 // Print to log (for passive profiling of production servers)
296 // define('MDL_PERFTOLOG' , true);
298 // Print to footer (works with the default theme)
299 // define('MDL_PERFTOFOOT', true);
301 // Enable earlier profiling that causes more code to be covered
302 // on every request (db connections, config load, other inits...).
303 // Requires extra configuration to be defined in config.php like:
304 // profilingincluded, profilingexcluded, profilingautofrec,
305 // profilingallowme, profilingallowall, profilinglifetime
306 // $CFG->earlyprofilingenabled = true;
308 // Force displayed usernames
309 // A little hack to anonymise user names for all students. If you set these
310 // then all non-teachers will always see these for every person.
311 // $CFG->forcefirstname = 'Bruce';
312 // $CFG->forcelastname = 'Simpson';
314 // The following setting will turn SQL Error logging on. This will output an
315 // entry in apache error log indicating the position of the error and the statement
316 // called. This option will action disregarding error_reporting setting.
317 // $CFG->dblogerror = true;
319 // The following setting will log every database query to a table called adodb_logsql.
320 // Use this setting on a development server only, the table grows quickly!
321 // $CFG->logsql = true;
323 // The following setting will turn on username logging into Apache log. For full details regarding setting
324 // up of this function please refer to the install section of the document.
325 // $CFG->apacheloguser = 0; // Turn this feature off. Default value.
326 // $CFG->apacheloguser = 1; // Log user id.
327 // $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
328 // $CFG->apacheloguser = 3; // Log username.
329 // To get the values logged in Apache's log, add to your httpd.conf
330 // the following statements. In the General part put:
331 // LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat
332 // And in the part specific to your Moodle install / virtualhost:
333 // CustomLog "/your/path/to/log" moodleformat
334 // CAUTION: Use of this option will expose usernames in the Apache log,
335 // If you are going to publish your log, or the output of your web stats analyzer
336 // this will weaken the security of your website.
338 // Email database connection errors to someone. If Moodle cannot connect to the
339 // database, then email this address with a notice.
341 // $CFG->emailconnectionerrorsto = 'your@emailaddress.com';
343 // Set the priority of themes from highest to lowest. This is useful (for
344 // example) in sites where the user theme should override all other theme
345 // settings for accessibility reasons. You can also disable types of themes
346 // (other than site) by removing them from the array. The default setting is:
347 // $CFG->themeorder = array('course', 'category', 'session', 'user', 'site');
348 // NOTE: course, category, session, user themes still require the
349 // respective settings to be enabled
351 // It is possible to add extra themes directory stored outside of $CFG->dirroot.
352 // This local directory does not have to be accessible from internet.
354 // $CFG->themedir = '/location/of/extra/themes';
356 // It is possible to specify different cache and temp directories, use local fast filesystem
357 // for normal web servers. Server clusters MUST use shared filesystem for cachedir!
358 // The directories must not be accessible via web.
360 // $CFG->tempdir = '/var/www/moodle/temp';
361 // $CFG->cachedir = '/var/www/moodle/cache';
363 // Some filesystems such as NFS may not support file locking operations.
364 // Locking resolves race conditions and is strongly recommended for production servers.
365 // $CFG->preventfilelocking = false;
367 // If $CFG->langstringcache is enabled (which should always be in production
368 // environment), Moodle keeps aggregated strings in its own internal format
369 // optimised for performance. By default, this on-disk cache is created in
370 // $CFG->cachedir/lang. In cluster environment, you may wish to specify
371 // an alternative location of this cache so that each web server in the cluster
372 // uses its own local cache and does not need to access the shared dataroot.
373 // Make sure that the web server process has write permission to this location
374 // and that it has permission to remove the folder, too (so that the cache can
377 // $CFG->langcacheroot = '/var/www/moodle/htdocs/altcache/lang';
379 // If $CFG->langcache is enabled (which should always be in production
380 // environment), Moodle stores the list of available languages in a cache file.
381 // By default, the file $CFG->dataroot/languages is used. You may wish to
382 // specify an alternative location of this cache file.
384 // $CFG->langmenucachefile = '/var/www/moodle/htdocs/altcache/languages';
386 // Site default language can be set via standard administration interface. If you
387 // want to have initial error messages for eventual database connection problems
388 // localized too, you have to set your language code here.
390 // $CFG->lang = 'yourlangcode'; // for example 'cs'
392 // When Moodle is about to perform an intensive operation it raises PHP's memory
393 // limit. The following setting should be used on large sites to set the raised
394 // memory limit to something higher.
395 // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G
397 // $CFG->extramemorylimit = '1G';
399 // Moodle 2.4 introduced a new cache API.
400 // The cache API stores a configuration file within the Moodle data directory and
401 // uses that rather than the database in order to function in a stand-alone manner.
402 // Using altcacheconfigpath you can change the location where this config file is
404 // It can either be a directory in which to store the file, or the full path to the
405 // file if you want to take full control. Either way it must be writable by the
408 // $CFG->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php
410 // The CSS files the Moodle produces can be extremely large and complex, especially
411 // if you are using a custom theme that builds upon several other themes.
412 // In Moodle 2.3 a CSS optimiser was added as an experimental feature for advanced
413 // users. The CSS optimiser organises the CSS in order to reduce the overall number
414 // of rules and styles being sent to the client. It does this by collating the
415 // CSS before it is cached removing excess styles and rules and stripping out any
416 // extraneous content such as comments and empty rules.
417 // The following settings are used to enable and control the optimisation.
419 // Enable the CSS optimiser. This will only optimise the CSS if themedesignermode
420 // is not enabled. This can be set through the UI however it is noted here as well
421 // because the other CSS optimiser settings can not be set through the UI.
423 // $CFG->enablecssoptimiser = true;
425 // If set the CSS optimiser will add stats about the optimisation to the top of
426 // the optimised CSS file. You can then inspect the CSS to see the affect the CSS
427 // optimiser is having.
429 // $CFG->cssoptimiserstats = true;
431 // If set the CSS that is optimised will still retain a minimalistic formatting
432 // so that anyone wanting to can still clearly read it.
434 // $CFG->cssoptimiserpretty = true;
436 // Use the following flag to completely disable the Available update notifications
437 // feature and hide it from the server administration UI.
439 // $CFG->disableupdatenotifications = true;
441 // Use the following flag to completely disable the Automatic updates deployment
442 // feature and hide it from the server administration UI.
444 // $CFG->disableupdateautodeploy = true;
446 // Use the following flag to completely disable the On-click add-on installation
447 // feature and hide it from the server administration UI.
449 // $CFG->disableonclickaddoninstall = true;
451 // As of version 2.4 Moodle serves icons as SVG images if the users browser appears
453 // For those wanting to control the serving of SVG images the following setting can
454 // be defined in your config.php.
455 // If it is not defined then the default (browser detection) will occur.
457 // To ensure they are always used when available:
458 // $CFG->svgicons = true;
460 // To ensure they are never used even when available:
461 // $CFG->svgicons = false;
463 //=========================================================================
464 // 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
465 //=========================================================================
467 // Force a debugging mode regardless the settings in the site administration
468 // @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
469 // @ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
470 // $CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
471 // $CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS!
473 // You can specify a comma separated list of user ids that that always see
474 // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
475 // for these users only.
476 // $CFG->debugusers = '2';
478 // Prevent theme caching
479 // $CFG->themerev = -1; // NOT FOR PRODUCTION SERVERS!
481 // Prevent JS caching
482 // $CFG->jsrev = -1; // NOT FOR PRODUCTION SERVERS!
484 // Prevent core_string_manager on-disk cache
485 // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!
487 // When working with production data on test servers, no emails or other messages
488 // should ever be send to real users
489 // $CFG->noemailever = true; // NOT FOR PRODUCTION SERVERS!
491 // Divert all outgoing emails to this address to test and debug emailing features
492 // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
494 // Uncomment if you want to allow empty comments when modifying install.xml files.
495 // $CFG->xmldbdisablecommentchecking = true; // NOT FOR PRODUCTION SERVERS!
497 // Since 2.0 sql queries are not shown during upgrade by default.
498 // Please note that this setting may produce very long upgrade page on large sites.
499 // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!
501 // Add SQL queries to the output of cron, just before their execution
502 // $CFG->showcronsql = true;
504 // Force developer level debug and add debug info to the output of cron
505 // $CFG->showcrondebugging = true;
507 //=========================================================================
508 // 8. FORCED SETTINGS
509 //=========================================================================
510 // It is possible to specify normal admin settings here, the point is that
511 // they can not be changed through the standard admin settings pages any more.
513 // Core settings are specified directly via assignment to $CFG variable.
515 // $CFG->somecoresetting = 'value';
517 // Plugin settings have to be put into a special array.
519 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'secondsetting' => 'othervalue'),
520 // 'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));
522 //=========================================================================
523 // 9. PHPUNIT SUPPORT
524 //=========================================================================
525 // $CFG->phpunit_prefix = 'phpu_';
526 // $CFG->phpunit_dataroot = '/home/example/phpu_moodledata';
527 // $CFG->phpunit_directorypermissions = 02777; // optional
530 //=========================================================================
531 // 10. SECRET PASSWORD SALT
532 //=========================================================================
533 // A single site-wide password salt is no longer required *unless* you are
534 // upgrading an older version of Moodle (prior to 2.5), or if you are using
535 // a PHP version below 5.3.7. If upgrading, keep any values from your old
536 // config.php file. If you are using PHP < 5.3.7 set to a long random string
539 // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1';
541 // You may also have some alternative salts to allow migration from previously
544 // $CFG->passwordsaltalt1 = '';
545 // $CFG->passwordsaltalt2 = '';
546 // $CFG->passwordsaltalt3 = '';
548 // $CFG->passwordsaltalt19 = '';
549 // $CFG->passwordsaltalt20 = '';
552 //=========================================================================
554 //=========================================================================
555 // Behat uses http://localhost:8000 as default URL to run
556 // the acceptance tests, you can override this value.
558 // $CFG->behat_wwwroot = 'http://192.168.1.250:8000';
560 // You can override default Moodle configuration for Behat and add your own
561 // params; here you can add more profiles, use different Mink drivers than Selenium...
562 // These params would be merged with the default Moodle behat.yml, giving priority
563 // to the ones specified here. The array format is YAML, following the Behat
564 // params hierarchy. More info: http://docs.behat.org/guides/7.config.html
566 // $CFG->behat_config = array(
567 // 'default' => array(
568 // 'formatter' => array(
569 // 'name' => 'pretty',
570 // 'parameters' => array(
571 // 'decorated' => true,
572 // 'verbose' => false
578 // You can completely switch to test environment when "php admin/tool/behat/cli/util --enable",
579 // this means that all the site accesses will be routed to the test environment instead of
580 // the regular one, so NEVER USE THIS SETTING IN PRODUCTION SITES. This setting is useful
581 // when working with cloud CI (continous integration) servers which requires public sites to run the
582 // tests, or in testing/development installations when you are developing in a pre-PHP 5.4 server.
583 // Note that with this setting enabled $CFG->behat_wwwroot is ignored and $CFG->behat_wwwroot
584 // value will be the regular $CFG->wwwroot value.
586 // $CFG->behat_switchcompletely = true;
589 //=========================================================================
590 // ALL DONE! To continue installation, visit your main page with a browser
591 //=========================================================================
593 require_once(dirname(__FILE__
) . '/lib/setup.php'); // Do not edit
595 // There is no php closing tag in this file,
596 // it is intentional because it prevents trailing whitespace problems!