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
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 work around this
115 // by renaming the admin directory in your installation, and putting that
116 // new name here. eg "moodleadmin". This should fix all admin links in Moodle.
117 // After any change you need to visit your new admin directory
118 // and purge all caches.
120 $CFG->admin
= 'admin';
123 //=========================================================================
124 // 6. OTHER MISCELLANEOUS SETTINGS (ignore these for new installations)
125 //=========================================================================
127 // These are additional tweaks for which no GUI exists in Moodle yet.
129 // Starting in PHP 5.3 administrators should specify default timezone
130 // in PHP.ini, you can also specify it here if needed.
131 // See details at: http://php.net/manual/en/function.date-default-timezone-set.php
132 // List of time zones at: http://php.net/manual/en/timezones.php
133 // date_default_timezone_set('Australia/Perth');
135 // Change the key pair lifetime for Moodle Networking
136 // The default is 28 days. You would only want to change this if the key
137 // was not getting regenerated for any reason. You would probably want
138 // make it much longer. Note that you'll need to delete and manually update
140 // $CFG->mnetkeylifetime = 28;
142 // Allow user passwords to be included in backup files. Very dangerous
143 // setting as far as it publishes password hashes that can be unencrypted
144 // if the backup file is publicy available. Use it only if you can guarantee
145 // that all your backup files remain only privacy available and are never
146 // shared out from your site/institution!
147 // $CFG->includeuserpasswordsinbackup = true;
149 // Completely disable user creation when restoring a course, bypassing any
150 // permissions granted via roles and capabilities. Enabling this setting
151 // results in the restore process stopping when a user attempts to restore a
152 // course requiring users to be created.
153 // $CFG->disableusercreationonrestore = true;
155 // Keep the temporary directories used by backup and restore without being
156 // deleted at the end of the process. Use it if you want to debug / view
157 // all the information stored there after the process has ended. Note that
158 // those directories may be deleted (after some ttl) both by cron and / or
159 // by new backup / restore invocations.
160 // $CFG->keeptempdirectoriesonbackup = true;
162 // Modify the restore process in order to force the "user checks" to assume
163 // that the backup originated from a different site, so detection of matching
164 // users is performed with different (more "relaxed") rules. Note that this is
165 // only useful if the backup file has been created using Moodle < 1.9.4 and the
166 // site has been rebuilt from scratch using backup files (not the best way btw).
167 // If you obtain user conflicts on restore, rather than enabling this setting
168 // permanently, try restoring the backup on a different site, back it up again
169 // and then restore on the target server.
170 // $CFG->forcedifferentsitecheckingusersonrestore = true;
172 // Prevent stats processing and hide the GUI
173 // $CFG->disablestatsprocessing = true;
175 // Setting this to true will enable admins to edit any post at any time
176 // $CFG->admineditalways = true;
178 // These variables define DEFAULT block variables for new courses
179 // If this one is set it overrides all others and is the only one used.
180 // $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
182 // These variables define the specific settings for defined course formats.
183 // They override any settings defined in the formats own config file.
184 // $CFG->defaultblocks_site = 'site_main_menu,course_list:course_summary,calendar_month';
185 // $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,course_list';
186 // $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
187 // $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
189 // These blocks are used when no other default setting is found.
190 // $CFG->defaultblocks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
192 // You can specify a different class to be created for the $PAGE global, and to
193 // compute which blocks appear on each page. However, I cannot think of any good
194 // reason why you would need to change that. It just felt wrong to hard-code the
195 // the class name. You are strongly advised not to use these to settings unless
196 // you are absolutely sure you know what you are doing.
197 // $CFG->moodlepageclass = 'moodle_page';
198 // $CFG->moodlepageclassfile = "$CFG->dirroot/local/myplugin/mypageclass.php";
199 // $CFG->blockmanagerclass = 'block_manager';
200 // $CFG->blockmanagerclassfile = "$CFG->dirroot/local/myplugin/myblockamanagerclass.php";
202 // Seconds for files to remain in caches. Decrease this if you are worried
203 // about students being served outdated versions of uploaded files.
204 // $CFG->filelifetime = 86400;
206 // Some web servers can offload the file serving from PHP process,
207 // comment out one the following options to enable it in Moodle:
208 // $CFG->xsendfile = 'X-Sendfile'; // Apache {@see https://tn123.org/mod_xsendfile/}
209 // $CFG->xsendfile = 'X-LIGHTTPD-send-file'; // Lighttpd {@see http://redmine.lighttpd.net/projects/lighttpd/wiki/X-LIGHTTPD-send-file}
210 // $CFG->xsendfile = 'X-Accel-Redirect'; // Nginx {@see http://wiki.nginx.org/XSendfile}
211 // If your X-Sendfile implementation (usually Nginx) uses directory aliases specify them
212 // in the following array setting:
213 // $CFG->xsendfilealiases = array(
214 // '/dataroot/' => $CFG->dataroot,
215 // '/cachedir/' => '/var/www/moodle/cache', // for custom $CFG->cachedir locations
216 // '/localcachedir/' => '/var/local/cache', // for custom $CFG->localcachedir locations
217 // '/tempdir/' => '/var/www/moodle/temp', // for custom $CFG->tempdir locations
218 // '/filedir' => '/var/www/moodle/filedir', // for custom $CFG->filedir locations
221 // YUI caching may be sometimes improved by slasharguments:
222 // $CFG->yuislasharguments = 1;
223 // Some servers may need a special rewrite rule to work around internal path length limitations:
224 // RewriteRule (^.*/theme/yui_combo\.php)(/.*) $1?file=$2
227 // Following settings may be used to select session driver, uncomment only one of the handlers.
228 // Database session handler (not compatible with MyISAM):
229 // $CFG->session_handler_class = '\core\session\database';
230 // $CFG->session_database_acquire_lock_timeout = 120;
232 // File session handler (file system locking required):
233 // $CFG->session_handler_class = '\core\session\file';
234 // $CFG->session_file_save_path = $CFG->dataroot.'/sessions';
236 // Memcached session handler (requires memcached server and extension):
237 // $CFG->session_handler_class = '\core\session\memcached';
238 // $CFG->session_memcached_save_path = '127.0.0.1:11211';
239 // $CFG->session_memcached_prefix = 'memc.sess.key.';
240 // $CFG->session_memcached_acquire_lock_timeout = 120;
241 // $CFG->session_memcached_lock_expire = 7200; // Ignored if memcached extension <= 2.1.0
243 // Following setting allows you to alter how frequently is timemodified updated in sessions table.
244 // $CFG->session_update_timemodified_frequency = 20; // In seconds.
246 // If this setting is set to true, then Moodle will track the IP of the
247 // current user to make sure it hasn't changed during a session. This
248 // will prevent the possibility of sessions being hijacked via XSS, but it
249 // may break things for users coming using proxies that change all the time,
251 // $CFG->tracksessionip = true;
253 // The following lines are for handling email bounces.
254 // $CFG->handlebounces = true;
255 // $CFG->minbounces = 10;
256 // $CFG->bounceratio = .20;
257 // The next lines are needed both for bounce handling and any other email to module processing.
258 // mailprefix must be EXACTLY four characters.
259 // Uncomment and customise this block for Postfix
260 // $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix.
261 // $CFG->mailprefix = 'mdl-'; // - is the separator for qmail
262 // $CFG->maildomain = 'youremaildomain.com';
264 // Enable when setting up advanced reverse proxy load balancing configurations,
265 // it may be also necessary to enable this when using port forwarding.
266 // $CFG->reverseproxy = true;
268 // Enable when using external SSL appliance for performance reasons.
269 // Please note that site may be accessible via https: or https:, but not both!
270 // $CFG->sslproxy = true;
272 // This setting will cause the userdate() function not to fix %d in
273 // date strings, and just let them show with a zero prefix.
274 // $CFG->nofixday = true;
276 // This setting will make some graphs (eg user logs) use lines instead of bars
277 // $CFG->preferlinegraphs = true;
279 // Enabling this will allow custom scripts to replace existing moodle scripts.
280 // For example: if $CFG->customscripts/course/view.php exists then
281 // it will be used instead of $CFG->wwwroot/course/view.php
282 // At present this will only work for files that include config.php and are called
283 // as part of the url (index.php is implied).
284 // Some examples are:
285 // http://my.moodle.site/course/view.php
286 // http://my.moodle.site/index.php
287 // http://my.moodle.site/admin (index.php implied)
288 // Custom scripts should not include config.php
289 // Warning: Replacing standard moodle scripts may pose security risks and/or may not
290 // be compatible with upgrades. Use this option only if you are aware of the risks
292 // Specify the full directory path to the custom scripts
293 // $CFG->customscripts = '/home/example/customscripts';
295 // Performance profiling
297 // If you set Debug to "Yes" in the Configuration->Variables page some
298 // performance profiling data will show up on your footer (in default theme).
299 // With these settings you get more granular control over the capture
300 // and printout of the data
302 // Capture performance profiling data
303 // define('MDL_PERF' , true);
305 // Capture additional data from DB
306 // define('MDL_PERFDB' , true);
308 // Print to log (for passive profiling of production servers)
309 // define('MDL_PERFTOLOG' , true);
311 // Print to footer (works with the default theme)
312 // define('MDL_PERFTOFOOT', true);
314 // Enable earlier profiling that causes more code to be covered
315 // on every request (db connections, config load, other inits...).
316 // Requires extra configuration to be defined in config.php like:
317 // profilingincluded, profilingexcluded, profilingautofrec,
318 // profilingallowme, profilingallowall, profilinglifetime
319 // $CFG->earlyprofilingenabled = true;
321 // Force displayed usernames
322 // A little hack to anonymise user names for all students. If you set these
323 // then all non-teachers will always see these for every person.
324 // $CFG->forcefirstname = 'Bruce';
325 // $CFG->forcelastname = 'Simpson';
327 // The following setting will turn SQL Error logging on. This will output an
328 // entry in apache error log indicating the position of the error and the statement
329 // called. This option will action disregarding error_reporting setting.
330 // $CFG->dblogerror = true;
332 // The following setting will log every database query to a table called adodb_logsql.
333 // Use this setting on a development server only, the table grows quickly!
334 // $CFG->logsql = true;
336 // The following setting will turn on username logging into Apache log. For full details regarding setting
337 // up of this function please refer to the install section of the document.
338 // $CFG->apacheloguser = 0; // Turn this feature off. Default value.
339 // $CFG->apacheloguser = 1; // Log user id.
340 // $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
341 // $CFG->apacheloguser = 3; // Log username.
342 // To get the values logged in Apache's log, add to your httpd.conf
343 // the following statements. In the General part put:
344 // LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat
345 // And in the part specific to your Moodle install / virtualhost:
346 // CustomLog "/your/path/to/log" moodleformat
347 // CAUTION: Use of this option will expose usernames in the Apache log,
348 // If you are going to publish your log, or the output of your web stats analyzer
349 // this will weaken the security of your website.
351 // Email database connection errors to someone. If Moodle cannot connect to the
352 // database, then email this address with a notice.
354 // $CFG->emailconnectionerrorsto = 'your@emailaddress.com';
356 // Set the priority of themes from highest to lowest. This is useful (for
357 // example) in sites where the user theme should override all other theme
358 // settings for accessibility reasons. You can also disable types of themes
359 // (other than site) by removing them from the array. The default setting is:
360 // $CFG->themeorder = array('course', 'category', 'session', 'user', 'site');
361 // NOTE: course, category, session, user themes still require the
362 // respective settings to be enabled
364 // It is possible to add extra themes directory stored outside of $CFG->dirroot.
365 // This local directory does not have to be accessible from internet.
367 // $CFG->themedir = '/location/of/extra/themes';
369 // It is possible to specify different cache and temp directories, use local fast filesystem
370 // for normal web servers. Server clusters MUST use shared filesystem for cachedir!
371 // Localcachedir is intended for server clusters, it does not have to be shared by cluster nodes.
372 // The directories must not be accessible via web.
374 // $CFG->tempdir = '/var/www/moodle/temp'; // Files used during one HTTP request only.
375 // $CFG->cachedir = '/var/www/moodle/cache'; // Directory MUST BE SHARED by all cluster nodes, locking required.
376 // $CFG->localcachedir = '/var/local/cache'; // Intended for local node caching.
378 // Some filesystems such as NFS may not support file locking operations.
379 // Locking resolves race conditions and is strongly recommended for production servers.
380 // $CFG->preventfilelocking = false;
382 // Site default language can be set via standard administration interface. If you
383 // want to have initial error messages for eventual database connection problems
384 // localized too, you have to set your language code here.
386 // $CFG->lang = 'yourlangcode'; // for example 'cs'
388 // When Moodle is about to perform an intensive operation it raises PHP's memory
389 // limit. The following setting should be used on large sites to set the raised
390 // memory limit to something higher.
391 // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G
393 // $CFG->extramemorylimit = '1024M';
395 // Moodle 2.4 introduced a new cache API.
396 // The cache API stores a configuration file within the Moodle data directory and
397 // uses that rather than the database in order to function in a stand-alone manner.
398 // Using altcacheconfigpath you can change the location where this config file is
400 // It can either be a directory in which to store the file, or the full path to the
401 // file if you want to take full control. Either way it must be writable by the
404 // $CFG->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php
406 // The CSS files the Moodle produces can be extremely large and complex, especially
407 // if you are using a custom theme that builds upon several other themes.
408 // In Moodle 2.3 a CSS optimiser was added as an experimental feature for advanced
409 // users. The CSS optimiser organises the CSS in order to reduce the overall number
410 // of rules and styles being sent to the client. It does this by collating the
411 // CSS before it is cached removing excess styles and rules and stripping out any
412 // extraneous content such as comments and empty rules.
413 // The following settings are used to enable and control the optimisation.
415 // Enable the CSS optimiser. This will only optimise the CSS if themedesignermode
416 // is not enabled. This can be set through the UI however it is noted here as well
417 // because the other CSS optimiser settings can not be set through the UI.
419 // $CFG->enablecssoptimiser = true;
421 // If set the CSS optimiser will add stats about the optimisation to the top of
422 // the optimised CSS file. You can then inspect the CSS to see the affect the CSS
423 // optimiser is having.
425 // $CFG->cssoptimiserstats = true;
427 // If set the CSS that is optimised will still retain a minimalistic formatting
428 // so that anyone wanting to can still clearly read it.
430 // $CFG->cssoptimiserpretty = true;
432 // Use the following flag to completely disable the Available update notifications
433 // feature and hide it from the server administration UI.
435 // $CFG->disableupdatenotifications = true;
437 // Use the following flag to completely disable the Automatic updates deployment
438 // feature and hide it from the server administration UI.
440 // $CFG->disableupdateautodeploy = true;
442 // Use the following flag to completely disable the On-click add-on installation
443 // feature and hide it from the server administration UI.
445 // $CFG->disableonclickaddoninstall = true;
447 // As of version 2.4 Moodle serves icons as SVG images if the users browser appears
449 // For those wanting to control the serving of SVG images the following setting can
450 // be defined in your config.php.
451 // If it is not defined then the default (browser detection) will occur.
453 // To ensure they are always used when available:
454 // $CFG->svgicons = true;
456 // To ensure they are never used even when available:
457 // $CFG->svgicons = false;
459 // Some administration options allow setting the path to executable files. This can
460 // potentially cause a security risk. Set this option to true to disable editing
461 // those config settings via the web. They will need to be set explicitly in the
463 // $CFG->preventexecpath = true;
465 // Use the following flag to set userid for noreply user. If not set then moodle will
466 // create dummy user and use -ve value as user id.
467 // $CFG->noreplyuserid = -10;
469 // As of version 2.6 Moodle supports admin to set support user. If not set, all mails
470 // will be sent to supportemail.
471 // $CFG->supportuserid = -20;
473 //=========================================================================
474 // 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
475 //=========================================================================
477 // Force a debugging mode regardless the settings in the site administration
478 // @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
479 // @ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
480 // $CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
481 // $CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS!
483 // You can specify a comma separated list of user ids that that always see
484 // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
485 // for these users only.
486 // $CFG->debugusers = '2';
488 // Prevent theme caching
489 // $CFG->themedesignermode = true; // NOT FOR PRODUCTION SERVERS!
491 // Prevent JS caching
492 // $CFG->cachejs = false; // NOT FOR PRODUCTION SERVERS!
494 // Restrict which YUI logging statements are shown in the browser console.
495 // For details see the upstream documentation:
496 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logInclude
497 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logExclude
498 // $CFG->yuiloginclude = array(
499 // 'moodle-core-dock-loader' => true,
500 // 'moodle-course-categoryexpander' => true,
502 // $CFG->yuilogexclude = array(
503 // 'moodle-core-dock' => true,
504 // 'moodle-core-notification' => true,
507 // Set the minimum log level for YUI logging statements.
508 // For details see the upstream documentation:
509 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logLevel
510 // $CFG->yuiloglevel = 'debug';
512 // Prevent core_string_manager application caching
513 // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!
515 // When working with production data on test servers, no emails or other messages
516 // should ever be send to real users
517 // $CFG->noemailever = true; // NOT FOR PRODUCTION SERVERS!
519 // Divert all outgoing emails to this address to test and debug emailing features
520 // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
522 // Uncomment if you want to allow empty comments when modifying install.xml files.
523 // $CFG->xmldbdisablecommentchecking = true; // NOT FOR PRODUCTION SERVERS!
525 // Since 2.0 sql queries are not shown during upgrade by default.
526 // Please note that this setting may produce very long upgrade page on large sites.
527 // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!
529 // Add SQL queries to the output of cron, just before their execution
530 // $CFG->showcronsql = true;
532 // Force developer level debug and add debug info to the output of cron
533 // $CFG->showcrondebugging = true;
535 //=========================================================================
536 // 8. FORCED SETTINGS
537 //=========================================================================
538 // It is possible to specify normal admin settings here, the point is that
539 // they can not be changed through the standard admin settings pages any more.
541 // Core settings are specified directly via assignment to $CFG variable.
543 // $CFG->somecoresetting = 'value';
545 // Plugin settings have to be put into a special array.
547 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'secondsetting' => 'othervalue'),
548 // 'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));
549 // Module default settings with advanced/locked checkboxes can be set too. To do this, add
550 // an extra config with '_adv' or '_locked' as a suffix and set the value to true or false.
552 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'settingname_locked' => true, 'settingname_adv' => true));
554 //=========================================================================
555 // 9. PHPUNIT SUPPORT
556 //=========================================================================
557 // $CFG->phpunit_prefix = 'phpu_';
558 // $CFG->phpunit_dataroot = '/home/example/phpu_moodledata';
559 // $CFG->phpunit_directorypermissions = 02777; // optional
562 //=========================================================================
563 // 10. SECRET PASSWORD SALT
564 //=========================================================================
565 // A single site-wide password salt is no longer required *unless* you are
566 // upgrading an older version of Moodle (prior to 2.5), or if you are using
567 // a PHP version below 5.3.7. If upgrading, keep any values from your old
568 // config.php file. If you are using PHP < 5.3.7 set to a long random string
571 // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1';
573 // You may also have some alternative salts to allow migration from previously
576 // $CFG->passwordsaltalt1 = '';
577 // $CFG->passwordsaltalt2 = '';
578 // $CFG->passwordsaltalt3 = '';
580 // $CFG->passwordsaltalt19 = '';
581 // $CFG->passwordsaltalt20 = '';
584 //=========================================================================
586 //=========================================================================
587 // Behat needs a separate data directory and unique database prefix:
589 // $CFG->behat_prefix = 'bht_';
590 // $CFG->behat_dataroot = '/home/example/bht_moodledata';
592 // Behat uses http://localhost:8000 as default URL to run
593 // the acceptance tests, you can override this value.
595 // $CFG->behat_wwwroot = 'http://192.168.1.250:8000';
597 // You can override default Moodle configuration for Behat and add your own
598 // params; here you can add more profiles, use different Mink drivers than Selenium...
599 // These params would be merged with the default Moodle behat.yml, giving priority
600 // to the ones specified here. The array format is YAML, following the Behat
601 // params hierarchy. More info: http://docs.behat.org/guides/7.config.html
603 // $CFG->behat_config = array(
604 // 'default' => array(
605 // 'formatter' => array(
606 // 'name' => 'pretty',
607 // 'parameters' => array(
608 // 'decorated' => true,
609 // 'verbose' => false
613 // 'Mac-Firefox' => array(
614 // 'extensions' => array(
615 // 'Behat\MinkExtension\Extension' => array(
616 // 'selenium2' => array(
617 // 'browser' => 'firefox',
618 // 'capabilities' => array(
619 // 'platform' => 'OS X 10.6',
626 // 'Mac-Safari' => array(
627 // 'extensions' => array(
628 // 'Behat\MinkExtension\Extension' => array(
629 // 'selenium2' => array(
630 // 'browser' => 'safari',
631 // 'capabilities' => array(
632 // 'platform' => 'OS X 10.8',
641 // You can completely switch to test environment when "php admin/tool/behat/cli/util --enable",
642 // this means that all the site accesses will be routed to the test environment instead of
643 // the regular one, so NEVER USE THIS SETTING IN PRODUCTION SITES. This setting is useful
644 // when working with cloud CI (continous integration) servers which requires public sites to run the
645 // tests, or in testing/development installations when you are developing in a pre-PHP 5.4 server.
646 // Note that with this setting enabled $CFG->behat_wwwroot is ignored and $CFG->behat_wwwroot
647 // value will be the regular $CFG->wwwroot value.
649 // $CFG->behat_switchcompletely = true;
651 // You can force the browser session (not user's sessions) to restart after N seconds. This could
652 // be useful if you are using a cloud-based service with time restrictions in the browser side.
653 // Setting this value the browser session that Behat is using will be restarted. Set the time in
654 // seconds. Is not recommended to use this setting if you don't explicitly need it.
656 // $CFG->behat_restart_browser_after = 7200; // Restarts the browser session after 2 hours
658 // All this page's extra Moodle settings are compared against a white list of allowed settings
659 // (the basic and behat_* ones) to avoid problems with production environments. This setting can be
660 // used to expand the default white list with an array of extra settings.
662 // $CFG->behat_extraallowedsettings = array('logsql', 'dblogerror');
664 //=========================================================================
665 // 12. DEVELOPER DATA GENERATOR
666 //=========================================================================
668 // The developer data generator tool is intended to be used only in development or testing sites and
669 // it's usage in production environments is not recommended; if it is used to create JMeter test plans
670 // is even less recommended as JMeter needs to log in as site course users. JMeter needs to know the
671 // users passwords but would be dangerous to have a default password as everybody would know it, which would
672 // be specially dangerouse if somebody uses this tool in a production site, so in order to prevent unintended
673 // uses of the tool and undesired accesses as well, is compulsory to set a password for the users
674 // generated by this tool, but only in case you want to generate a JMeter test. The value should be a string.
676 // $CFG->tool_generator_users_password = 'examplepassword';
678 //=========================================================================
679 // ALL DONE! To continue installation, visit your main page with a browser
680 //=========================================================================
682 require_once(dirname(__FILE__
) . '/lib/setup.php'); // Do not edit
684 // There is no php closing tag in this file,
685 // it is intentional because it prevents trailing whitespace problems!