moodle config-dist.php -> config.php 一切都在这里，需要的加点注释
做点说明
dbtype = 'pgsql'; // 'pgsql', 'mariadb', 'mysqli', 'mssql', 'sqlsrv' or 'oci'$cfg->dblibrary = 'native'; // 'native' only at the moment$cfg->dbhost = 'localhost'; // eg 'localhost' or 'db.isp.com' or ip$cfg->dbname = 'moodle'; // database name, eg moodle$cfg->dbuser = 'username'; // your database username$cfg->dbpass = 'password'; // your database password$cfg->prefix = 'mdl_'; // prefix to use for all table names$cfg->dboptions = array( 'dbpersist' => false, // should persistent database connections be // used? set to 'false' for the most stable // setting, 'true' can improve performance // sometimes 'dbsocket' => false, // should connection via unix socket be used? // if you set it to 'true' or custom path // here set dbhost to 'localhost', // (please note mysql is always using socket // if dbhost is 'localhost' - if you need // local port connection use '127.0.0.1') 'dbport' => '', // the tcp port number to use when connecting // to the server. keep empty string for the // default port);//=========================================================================// 2. web site location//=========================================================================// now you need to tell moodle where it is located. specify the full// web address to where moodle has been installed. if your web site// is accessible via multiple urls then choose the most natural one// that your students would use. do not include a trailing slash//// if you need both intranet and internet access please read// http://docs.moodle.org/en/masquerading$cfg->wwwroot = 'http://example.com/moodle';//=========================================================================// 3. data files location//=========================================================================// now you need a place where moodle can save uploaded files. this// directory should be readable and writeable by the web server user// (usually 'nobody' or 'apache'), but it should not be accessible// directly via the web.//// - on hosting systems you might need to make sure that your group has// no permissions at all, but that others have full permissions.//// - on windows systems you might specify something like 'c:\moodledata'$cfg->dataroot = '/home/example/moodledata';//=========================================================================// 4. data files permissions//=========================================================================// the following parameter sets the permissions of new directories// created by moodle within the data directory. the format is in// octal format (as used by the unix utility chmod, for example).// the default is usually ok, but you may want to change it to 0750// if you are concerned about world-access to the files (you will need// to make sure the web server process (eg apache) can access the files.// note: the prefixed 0 is important, and don't use quotes.$cfg->directorypermissions = 02777;//=========================================================================// 5. directory location (most people can just ignore this setting)//=========================================================================// a very few webhosts use /admin as a special url for you to access a// control panel or something. unfortunately this conflicts with the// standard location for the moodle admin pages. you can work around this// by renaming the admin directory in your installation, and putting that// new name here. eg moodleadmin. this should fix all admin links in moodle.// after any change you need to visit your new admin directory// and purge all caches.$cfg->admin = 'admin';//=========================================================================// 6. other miscellaneous settings (ignore these for new installations)//=========================================================================//// these are additional tweaks for which no gui exists in moodle yet.//// starting in php 5.3 administrators should specify default timezone// in php.ini, you can also specify it here if needed.// see details at: http://php.net/manual/en/function.date-default-timezone-set.php// list of time zones at: http://php.net/manual/en/timezones.php// date_default_timezone_set('australia/perth');//// change the key pair lifetime for moodle networking// the default is 28 days. you would only want to change this if the key// was not getting regenerated for any reason. you would probably want// make it much longer. note that you'll need to delete and manually update// any existing key.// $cfg->mnetkeylifetime = 28;//// not recommended: set the following to true to allow the use// off non-moodle standard characters in usernames.// $cfg->extendedusernamechars = true;//// allow user passwords to be included in backup files. very dangerous// setting as far as it publishes password hashes that can be unencrypted// if the backup file is publicy available. use it only if you can guarantee// that all your backup files remain only privacy available and are never// shared out from your site/institution!// $cfg->includeuserpasswordsinbackup = true;//// completely disable user creation when restoring a course, bypassing any// permissions granted via roles and capabilities. enabling this setting// results in the restore process stopping when a user attempts to restore a// course requiring users to be created.// $cfg->disableusercreationonrestore = true;//// keep the temporary directories used by backup and restore without being// deleted at the end of the process. use it if you want to debug / view// all the information stored there after the process has ended. note that// those directories may be deleted (after some ttl) both by cron and / or// by new backup / restore invocations.// $cfg->keeptempdirectoriesonbackup = true;//// modify the restore process in order to force the user checks to assume// that the backup originated from a different site, so detection of matching// users is performed with different (more relaxed) rules. note that this is// only useful if the backup file has been created using moodle forcedifferentsitecheckingusersonrestore = true;//// force the backup system to continue to create backups in the legacy zip// format instead of the new tgz format. does not affect restore, which// auto-detects the underlying file format.// $cfg->usezipbackups = true;//// prevent stats processing and hide the gui// $cfg->disablestatsprocessing = true;//// setting this to true will enable admins to edit any post at any time// $cfg->admineditalways = true;//// these variables define default block variables for new courses// if this one is set it overrides all others and is the only one used.// $cfg->defaultblocks_override = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';//// these variables define the specific settings for defined course formats.// they override any settings defined in the formats own config file.// $cfg->defaultblocks_site = 'site_main_menu,course_list:course_summary,calendar_month';// $cfg->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,course_list';// $cfg->defaultblocks_topics = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';// $cfg->defaultblocks_weeks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';//// these blocks are used when no other default setting is found.// $cfg->defaultblocks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';//// you can specify a different class to be created for the $page global, and to// compute which blocks appear on each page. however, i cannot think of any good// reason why you would need to change that. it just felt wrong to hard-code the// the class name. you are strongly advised not to use these to settings unless// you are absolutely sure you know what you are doing.// $cfg->moodlepageclass = 'moodle_page';// $cfg->moodlepageclassfile = $cfg->dirroot/local/myplugin/mypageclass.php;// $cfg->blockmanagerclass = 'block_manager';// $cfg->blockmanagerclassfile = $cfg->dirroot/local/myplugin/myblockamanagerclass.php;//// seconds for files to remain in caches. decrease this if you are worried// about students being served outdated versions of uploaded files.// $cfg->filelifetime = 60*60*6;//// some web servers can offload the file serving from php process,// comment out one the following options to enable it in moodle:// $cfg->xsendfile = 'x-sendfile'; // apache [email protected] https://tn123.org/mod_xsendfile/}// $cfg->xsendfile = 'x-lighttpd-send-file'; // lighttpd [email protected] http://redmine.lighttpd.net/projects/lighttpd/wiki/x-lighttpd-send-file}// $cfg->xsendfile = 'x-accel-redirect'; // nginx [email protected] http://wiki.nginx.org/xsendfile}// if your x-sendfile implementation (usually nginx) uses directory aliases specify them// in the following array setting:// $cfg->xsendfilealiases = array(// '/dataroot/' => $cfg->dataroot,// '/cachedir/' => '/var/www/moodle/cache', // for custom $cfg->cachedir locations// '/localcachedir/' => '/var/local/cache', // for custom $cfg->localcachedir locations// '/tempdir/' => '/var/www/moodle/temp', // for custom $cfg->tempdir locations// '/filedir' => '/var/www/moodle/filedir', // for custom $cfg->filedir locations// );//// yui caching may be sometimes improved by slasharguments:// $cfg->yuislasharguments = 1;// some servers may need a special rewrite rule to work around internal path length limitations:// rewriterule (^.*/theme/yui_combo\.php)(/.*) $1?file=$2////// following settings may be used to select session driver, uncomment only one of the handlers.// database session handler (not compatible with myisam):// $cfg->session_handler_class = '\core\session\database';// $cfg->session_database_acquire_lock_timeout = 120;//// file session handler (file system locking required):// $cfg->session_handler_class = '\core\session\file';// $cfg->session_file_save_path = $cfg->dataroot.'/sessions';//// memcached session handler (requires memcached server and extension):// $cfg->session_handler_class = '\core\session\memcached';// $cfg->session_memcached_save_path = '127.0.0.1:11211';// $cfg->session_memcached_prefix = 'memc.sess.key.';// $cfg->session_memcached_acquire_lock_timeout = 120;// $cfg->session_memcached_lock_expire = 7200; // ignored if pecl memcached is below version 2.2.0//// memcache session handler (requires memcached server and memcache extension):// $cfg->session_handler_class = '\core\session\memcache';// $cfg->session_memcache_save_path = '127.0.0.1:11211';// $cfg->session_memcache_acquire_lock_timeout = 120;// ** note: memcache extension has less features than memcached and may be// less reliable. use memcached where possible or if you encounter// session problems. **//// please be aware that when selecting either memcached or memcache for sessions that it is advised to use a dedicated// memcache server. the memcache and memcached extensions do not provide isolated environments for individual uses.// using the same server for other purposes (muc for example) can lead to sessions being prematurely removed should// the other uses of the server purge the cache.//// following setting allows you to alter how frequently is timemodified updated in sessions table.// $cfg->session_update_timemodified_frequency = 20; // in seconds.//// if this setting is set to true, then moodle will track the ip of the// current user to make sure it hasn't changed during a session. this// will prevent the possibility of sessions being hijacked via xss, but it// may break things for users coming using proxies that change all the time,// like aol.// $cfg->tracksessionip = true;//// the following lines are for handling email bounces.// $cfg->handlebounces = true;// $cfg->minbounces = 10;// $cfg->bounceratio = .20;// the next lines are needed both for bounce handling and any other email to module processing.// mailprefix must be exactly four characters.// uncomment and customise this block for postfix// $cfg->mailprefix = 'mdl+'; // + is the separator for exim and postfix.// $cfg->mailprefix = 'mdl-'; // - is the separator for qmail// $cfg->maildomain = 'youremaildomain.com';//// enable when setting up advanced reverse proxy load balancing configurations,// it may be also necessary to enable this when using port forwarding.// $cfg->reverseproxy = true;//// enable when using external ssl appliance for performance reasons.// please note that site may be accessible via http: or https:, but not both!// $cfg->sslproxy = true;//// this setting will cause the userdate() function not to fix %d in// date strings, and just let them show with a zero prefix.// $cfg->nofixday = true;//// this setting will make some graphs (eg user logs) use lines instead of bars// $cfg->preferlinegraphs = true;//// enabling this will allow custom scripts to replace existing moodle scripts.// for example: if $cfg->customscripts/course/view.php exists then// it will be used instead of $cfg->wwwroot/course/view.php// at present this will only work for files that include config.php and are called// as part of the url (index.php is implied).// some examples are:// http://my.moodle.site/course/view.php// http://my.moodle.site/index.php// http://my.moodle.site/admin (index.php implied)// custom scripts should not include config.php// warning: replacing standard moodle scripts may pose security risks and/or may not// be compatible with upgrades. use this option only if you are aware of the risks// involved.// specify the full directory path to the custom scripts// $cfg->customscripts = '/home/example/customscripts';//// performance profiling//// if you set debug to yes in the configuration->variables page some// performance profiling data will show up on your footer (in default theme).// with these settings you get more granular control over the capture// and printout of the data//// capture performance profiling data// define('mdl_perf' , true);//// capture additional data from db// define('mdl_perfdb' , true);//// print to log (for passive profiling of production servers)// define('mdl_perftolog' , true);//// print to footer (works with the default theme)// define('mdl_perftofoot', true);//// enable earlier profiling that causes more code to be covered// on every request (db connections, config load, other inits...).// requires extra configuration to be defined in config.php like:// profilingincluded, profilingexcluded, profilingautofrec,// profilingallowme, profilingallowall, profilinglifetime// $cfg->earlyprofilingenabled = true;//// force displayed usernames// a little hack to anonymise user names for all students. if you set these// then all non-teachers will always see these for every person.// $cfg->forcefirstname = 'bruce';// $cfg->forcelastname = 'simpson';//// the following setting will turn on username logging into apache log. for full details regarding setting// up of this function please refer to the install section of the document.// $cfg->apacheloguser = 0; // turn this feature off. default value.// $cfg->apacheloguser = 1; // log user id.// $cfg->apacheloguser = 2; // log full name in cleaned format. ie, darth vader will be displayed as darth_vader.// $cfg->apacheloguser = 3; // log username.// to get the values logged in apache's log, add to your httpd.conf// the following statements. in the general part put:// logformat %h %l %{moodleuser}n %t \%r\ %s %b \%{referer}i\ \%{user-agent}i\ moodleformat// and in the part specific to your moodle install / virtualhost:// customlog /your/path/to/log moodleformat// caution: use of this option will expose usernames in the apache log,// if you are going to publish your log, or the output of your web stats analyzer// this will weaken the security of your website.//// email database connection errors to someone. if moodle cannot connect to the// database, then email this address with a notice.//// $cfg->emailconnectionerrorsto = '[email protected]';//// set the priority of themes from highest to lowest. this is useful (for// example) in sites where the user theme should override all other theme// settings for accessibility reasons. you can also disable types of themes// (other than site) by removing them from the array. the default setting is:// $cfg->themeorder = array('course', 'category', 'session', 'user', 'site');// note: course, category, session, user themes still require the// respective settings to be enabled//// it is possible to add extra themes directory stored outside of $cfg->dirroot.// this local directory does not have to be accessible from internet.//// $cfg->themedir = '/location/of/extra/themes';//// it is possible to specify different cache and temp directories, use local fast filesystem// for normal web servers. server clusters must use shared filesystem for cachedir!// localcachedir is intended for server clusters, it does not have to be shared by cluster nodes.// the directories must not be accessible via web.//// $cfg->tempdir = '/var/www/moodle/temp'; // directory must be shared by all clsuter nodes.// $cfg->cachedir = '/var/www/moodle/cache'; // directory must be shared by all cluster nodes, locking required.// $cfg->localcachedir = '/var/local/cache'; // intended for local node caching.//// some filesystems such as nfs may not support file locking operations.// locking resolves race conditions and is strongly recommended for production servers.// $cfg->preventfilelocking = false;//// site default language can be set via standard administration interface. if you// want to have initial error messages for eventual database connection problems// localized too, you have to set your language code here.//// $cfg->lang = 'yourlangcode'; // for example 'cs'//// when moodle is about to perform an intensive operation it raises php's memory// limit. the following setting should be used on large sites to set the raised// memory limit to something higher.// the value for the settings should be a valid php memory value. e.g. 512m, 1g//// $cfg->extramemorylimit = '1024m';//// moodle 2.4 introduced a new cache api.// the cache api stores a configuration file within the moodle data directory and// uses that rather than the database in order to function in a stand-alone manner.// using altcacheconfigpath you can change the location where this config file is// looked for.// it can either be a directory in which to store the file, or the full path to the// file if you want to take full control. either way it must be writable by the// webserver.//// $cfg->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php//// the css files the moodle produces can be extremely large and complex, especially// if you are using a custom theme that builds upon several other themes.// in moodle 2.3 a css optimiser was added as an experimental feature for advanced// users. the css optimiser organises the css in order to reduce the overall number// of rules and styles being sent to the client. it does this by collating the// css before it is cached removing excess styles and rules and stripping out any// extraneous content such as comments and empty rules.// the following settings are used to enable and control the optimisation.//// enable the css optimiser. this will only optimise the css if themedesignermode// is not enabled. this can be set through the ui however it is noted here as well// because the other css optimiser settings can not be set through the ui.//// $cfg->enablecssoptimiser = true;//// if set the css optimiser will add stats about the optimisation to the top of// the optimised css file. you can then inspect the css to see the affect the css// optimiser is having.//// $cfg->cssoptimiserstats = true;//// if set the css that is optimised will still retain a minimalistic formatting// so that anyone wanting to can still clearly read it.//// $cfg->cssoptimiserpretty = true;//// use the following flag to completely disable the available update notifications// feature and hide it from the server administration ui.//// $cfg->disableupdatenotifications = true;//// use the following flag to completely disable the installation of plugins// (new plugins, available updates and missing dependencies) and related// features (such as cancelling the plugin installation or upgrade) via the// server administration web interface.//// $cfg->disableupdateautodeploy = true;//// use the following flag to disable modifications to scheduled tasks// whilst still showing the state of tasks.//// $cfg->preventscheduledtaskchanges = true;//// as of version 2.4 moodle serves icons as svg images if the users browser appears// to support svg.// for those wanting to control the serving of svg images the following setting can// be defined in your config.php.// if it is not defined then the default (browser detection) will occur.//// to ensure they are always used when available:// $cfg->svgicons = true;//// to ensure they are never used even when available:// $cfg->svgicons = false;//// some administration options allow setting the path to executable files. this can// potentially cause a security risk. set this option to true to disable editing// those config settings via the web. they will need to be set explicitly in the// config.php file// $cfg->preventexecpath = true;//// use the following flag to set userid for noreply user. if not set then moodle will// create dummy user and use -ve value as user id.// $cfg->noreplyuserid = -10;//// as of version 2.6 moodle supports admin to set support user. if not set, all mails// will be sent to supportemail.// $cfg->supportuserid = -20;//// moodle 2.7 introduces a locking api for critical tasks (e.g. cron).// the default locking system to use is db locking for postgres, and file locking for// mysql, oracle and sqlserver. if $cfg->preventfilelocking is set, then the default// will always be db locking. it can be manually set to one of the lock// factory classes listed below, or one of your own custom classes implementing the// \core\lock\lock_factory interface.//// $cfg->lock_factory = auto;//// the list of available lock factories is://// \\core\\lock\\file_lock_factory - file locking// uses lock files stored by default in the dataroot. whether this// works on clusters depends on the file system used for the dataroot.//// \\core\\lock\\db_record_lock_factory - db locking based on table rows.//// \\core\\lock\\postgres_lock_factory - db locking based on postgres advisory locks.//// settings used by the lock factories//// location for lock files used by the file locking factory. this must exist// on a shared file system that supports locking.// $cfg->lock_file_root = $cfg->dataroot . '/lock';//// moodle 2.9 allows administrators to customise the list of supported file types.// to add a new filetype or override the definition of an existing one, set the// customfiletypes variable like this://// $cfg->customfiletypes = array(// (object)array(// 'extension' => 'frog',// 'icon' => 'archive',// 'type' => 'application/frog',// 'customdescription' => 'amphibian-related file archive'// )// );//// the extension, icon, and type fields are required. the icon field can refer to// any icon inside the pix/f folder. you can also set the customdescription field// (shown above) and (for advanced use) the groups, string, and defaulticon fields.//// upgrade key//// if the upgrade key is defined here, then the value must be provided every time// the site is being upgraded though the web interface, regardless of whether the// administrator is logged in or not. this prevents anonymous access to the upgrade// screens where the real authentication and authorization mechanisms can not be// relied on.//// it is strongly recommended to use a value different from your real account// password.//// $cfg->upgradekey = 'put_some_password-like_value_here';////=========================================================================// 7. settings for development servers - not intended for production use!!!//=========================================================================//// force a debugging mode regardless the settings in the site administration// @error_reporting(e_all | e_strict); // not for production servers!// @ini_set('display_errors', '1'); // not for production servers!// $cfg->debug = (e_all | e_strict); // === debug_developer - not for production servers!// $cfg->debugdisplay = 1; // not for production servers!//// you can specify a comma separated list of user ids that that always see// debug messages, this overrides the debug flag in $cfg->debug and $cfg->debugdisplay// for these users only.// $cfg->debugusers = '2';//// prevent theme caching// $cfg->themedesignermode = true; // not for production servers!//// prevent js caching// $cfg->cachejs = false; // not for production servers!//// restrict which yui logging statements are shown in the browser console.// for details see the upstream documentation:// http://yuilibrary.com/yui/docs/api/classes/config.html#property_loginclude// http://yuilibrary.com/yui/docs/api/classes/config.html#property_logexclude// $cfg->yuiloginclude = array(// 'moodle-core-dock-loader' => true,// 'moodle-course-categoryexpander' => true,// );// $cfg->yuilogexclude = array(// 'moodle-core-dock' => true,// 'moodle-core-notification' => true,// );//// set the minimum log level for yui logging statements.// for details see the upstream documentation:// http://yuilibrary.com/yui/docs/api/classes/config.html#property_loglevel// $cfg->yuiloglevel = 'debug';//// prevent core_string_manager application caching// $cfg->langstringcache = false; // not for production servers!//// when working with production data on test servers, no emails or other messages// should ever be send to real users// $cfg->noemailever = true; // not for production servers!//// divert all outgoing emails to this address to test and debug emailing features// $cfg->divertallemailsto = '[email protected]'; // not for production servers!//// uncomment if you want to allow empty comments when modifying install.xml files.// $cfg->xmldbdisablecommentchecking = true; // not for production servers!//// since 2.0 sql queries are not shown during upgrade by default.// please note that this setting may produce very long upgrade page on large sites.// $cfg->upgradeshowsql = true; // not for production servers!//// add sql queries to the output of cron, just before their execution// $cfg->showcronsql = true;//// force developer level debug and add debug info to the output of cron// $cfg->showcrondebugging = true;////=========================================================================// 8. forced settings//=========================================================================// it is possible to specify normal admin settings here, the point is that// they can not be changed through the standard admin settings pages any more.//// core settings are specified directly via assignment to $cfg variable.// example:// $cfg->somecoresetting = 'value';//// plugin settings have to be put into a special array.// example:// $cfg->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'secondsetting' => 'othervalue'),// 'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));// module default settings with advanced/locked checkboxes can be set too. to do this, add// an extra config with '_adv' or '_locked' as a suffix and set the value to true or false.// example:// $cfg->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'settingname_locked' => true, 'settingname_adv' => true));////=========================================================================// 9. phpunit support//=========================================================================// $cfg->phpunit_prefix = 'phpu_';// $cfg->phpunit_dataroot = '/home/example/phpu_moodledata';// $cfg->phpunit_directorypermissions = 02777; // optional//////=========================================================================// 10. secret password salt//=========================================================================// a site-wide password salt is no longer used in new installations.// if upgrading from 2.6 or older, keep all existing salts in config.php file.//// $cfg->passwordsaltmain = '[email protected]&*1';//// you may also have some alternative salts to allow migration from previously// used salts.//// $cfg->passwordsaltalt1 = '';// $cfg->passwordsaltalt2 = '';// $cfg->passwordsaltalt3 = '';// ....// $cfg->passwordsaltalt19 = '';// $cfg->passwordsaltalt20 = '';//////=========================================================================// 11. behat support//=========================================================================// behat test site needs a unique www root, data directory and database prefix://// $cfg->behat_wwwroot = 'http://127.0.0.1/moodle';// $cfg->behat_prefix = 'bht_';// $cfg->behat_dataroot = '/home/example/bht_moodledata';//// you can override default moodle configuration for behat and add your own// params; here you can add more profiles, use different mink drivers than selenium...// these params would be merged with the default moodle behat.yml, giving priority// to the ones specified here. the array format is yaml, following the behat// params hierarchy. more info: http://docs.behat.org/guides/7.config.html// example:// $cfg->behat_config = array(// 'default' => array(// 'formatter' => array(// 'name' => 'pretty',// 'parameters' => array(// 'decorated' => true,// 'verbose' => false// )// )// ),// 'mac-firefox' => array(// 'extensions' => array(// 'behat\minkextension\extension' => array(// 'selenium2' => array(// 'browser' => 'firefox',// 'capabilities' => array(// 'platform' => 'os x 10.6',// 'version' => 20// )// )// )// )// ),// 'mac-safari' => array(// 'extensions' => array(// 'behat\minkextension\extension' => array(// 'selenium2' => array(// 'browser' => 'safari',// 'capabilities' => array(// 'platform' => 'os x 10.8',// 'version' => 6// )// )// )// )// )// );//// you can force the browser session (not user's sessions) to restart after n seconds. this could// be useful if you are using a cloud-based service with time restrictions in the browser side.// setting this value the browser session that behat is using will be restarted. set the time in// seconds. is not recommended to use this setting if you don't explicitly need it.// example:// $cfg->behat_restart_browser_after = 7200; // restarts the browser session after 2 hours//// all this page's extra moodle settings are compared against a white list of allowed settings// (the basic and behat_* ones) to avoid problems with production environments. this setting can be// used to expand the default white list with an array of extra settings.// example:// $cfg->behat_extraallowedsettings = array('somecoresetting', ...);//// you should explicitly allow the usage of the deprecated behat steps, otherwise an exception will// be thrown when using them. the setting is disabled by default.// example:// $cfg->behat_usedeprecated = true;//// including feature files from directories outside the dirroot is possible if required. the setting// requires that the running user has executable permissions on all parent directories in the paths.// example:// $cfg->behat_additionalfeatures = array('/home/developer/code/wipfeatures');//// you can make behat save several dumps when a scenario fails. the dumps currently saved are:// * a dump of the dom in it's state at the time of failure; and// * a screenshot (javascript is required for the screenshot functionality, so not all browsers support this option)// example:// $cfg->behat_faildump_path = '/my/path/to/save/failure/dumps';//// you can specify db, selenium wd_host etc. for behat parallel run by setting following variable.// example:// $cfg->behat_parallel_run = array (// array (// 'dbtype' => 'mysqli',// 'dblibrary' => 'native',// 'dbhost' => 'localhost',// 'dbname' => 'moodletest',// 'dbuser' => 'moodle',// 'dbpass' => 'moodle',// 'behat_prefix' => 'mdl_',// 'wd_host' => 'http://127.0.0.1:4444/wd/hub',// 'behat_wwwroot' => 'http://127.0.0.1/moodle',// 'behat_dataroot' => '/home/example/bht_moodledata'// ),// );//// to change name of behat parallel run site, define behat_parallel_site_name and parallel run sites will be suffixed// with this value// example:// define('behat_parallel_site_name', 'behatparallelsite');//// command line output for parallel behat install is limited to 80 chars, if you are installing more then 4 sites and// want to expand output to more then 80 chars, then define behat_max_cmd_line_output// example:// define('behat_max_cmd_line_output', 120);//// behat feature files will be distributed randomly between the processes by default. if you have timing file or want// to create timing file then define behat_feature_timing_file with path to timing file. it will be updated for each// run with latest time taken to execute feature.// example:// define('behat_feature_timing_file', '/path_to_timing_file/timing.json');//// if you don't have timing file and want some stable distribution of features, then you can use step counts to// distribute the features. you can generate step file by executing php admin/tool/behat/cli/util.php --updatesteps// this will update step file which is defined by behat_feature_step_file.// example:// define('behat_feature_step_file', '/path_to_feature_step_count_file/stepcount.json');//// feature distribution for each process is displayed as histogram. you can disable it by setting// behat_disable_histogram// example:// define('behat_disable_histogram', true);////=========================================================================// 12. developer data generator//=========================================================================//// the developer data generator tool is intended to be used only in development or testing sites and// it's usage in production environments is not recommended; if it is used to create jmeter test plans// is even less recommended as jmeter needs to log in as site course users. jmeter needs to know the// users passwords but would be dangerous to have a default password as everybody would know it, which would// be specially dangerouse if somebody uses this tool in a production site, so in order to prevent unintended// uses of the tool and undesired accesses as well, is compulsory to set a password for the users// generated by this tool, but only in case you want to generate a jmeter test. the value should be a string.// example:// $cfg->tool_generator_users_password = 'examplepassword';////=========================================================================// 13. system paths (you need to set following, depending on your system)//=========================================================================// ghostscript path.// on most linux installs, this can be left as '/usr/bin/gs'.// on windows it will be something like 'c:\gs\bin\gswin32c.exe' (make sure// there are no spaces in the path - if necessary copy the files 'gswin32c.exe'// and 'gsdll32.dll' to a new folder without a space in the path)// $cfg->pathtogs = '/usr/bin/gs';//// clam av path.// probably something like /usr/bin/clamscan or /usr/bin/clamdscan. you need// this in order for clam av to run.// $cfg->pathtoclam = '';//// path to du.// probably something like /usr/bin/du. if you enter this, pages that display// directory contents will run much faster for directories with a lot of files.// $cfg->pathtodu = '';//// path to aspell.// to use spell-checking within the editor, you must have aspell 0.50 or later// installed on your server, and you must specify the correct path to access the// aspell binary. on unix/linux systems, this path is usually /usr/bin/aspell,// but it might be something else.// $cfg->aspellpath = '';//// path to dot.// probably something like /usr/bin/dot. to be able to generate graphics from// dot files, you must have installed the dot executable and point to it here.// note that, for now, this only used by the profiling features// (development->profiling) built into moodle.// $cfg->pathtodot = '';//=========================================================================// all done! to continue installation, visit your main page with a browser//=========================================================================require_once(dirname(__file__) . '/lib/setup.php'); // do not edit// there is no php closing tag in this file,// it is intentional because it prevents trailing whitespace problems!