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