| [ Index ] |
PHP Cross Reference of moodle-2.8 |
[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 // Prevent stats processing and hide the GUI 177 // $CFG->disablestatsprocessing = true; 178 // 179 // Setting this to true will enable admins to edit any post at any time 180 // $CFG->admineditalways = true; 181 // 182 // These variables define DEFAULT block variables for new courses 183 // If this one is set it overrides all others and is the only one used. 184 // $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity'; 185 // 186 // These variables define the specific settings for defined course formats. 187 // They override any settings defined in the formats own config file. 188 // $CFG->defaultblocks_site = 'site_main_menu,course_list:course_summary,calendar_month'; 189 // $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,course_list'; 190 // $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity'; 191 // $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity'; 192 // 193 // These blocks are used when no other default setting is found. 194 // $CFG->defaultblocks = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity'; 195 // 196 // You can specify a different class to be created for the $PAGE global, and to 197 // compute which blocks appear on each page. However, I cannot think of any good 198 // reason why you would need to change that. It just felt wrong to hard-code the 199 // the class name. You are strongly advised not to use these to settings unless 200 // you are absolutely sure you know what you are doing. 201 // $CFG->moodlepageclass = 'moodle_page'; 202 // $CFG->moodlepageclassfile = "$CFG->dirroot/local/myplugin/mypageclass.php"; 203 // $CFG->blockmanagerclass = 'block_manager'; 204 // $CFG->blockmanagerclassfile = "$CFG->dirroot/local/myplugin/myblockamanagerclass.php"; 205 // 206 // Seconds for files to remain in caches. Decrease this if you are worried 207 // about students being served outdated versions of uploaded files. 208 // $CFG->filelifetime = 60*60*6; 209 // 210 // Some web servers can offload the file serving from PHP process, 211 // comment out one the following options to enable it in Moodle: 212 // $CFG->xsendfile = 'X-Sendfile'; // Apache {@see https://tn123.org/mod_xsendfile/} 213 // $CFG->xsendfile = 'X-LIGHTTPD-send-file'; // Lighttpd {@see http://redmine.lighttpd.net/projects/lighttpd/wiki/X-LIGHTTPD-send-file} 214 // $CFG->xsendfile = 'X-Accel-Redirect'; // Nginx {@see http://wiki.nginx.org/XSendfile} 215 // If your X-Sendfile implementation (usually Nginx) uses directory aliases specify them 216 // in the following array setting: 217 // $CFG->xsendfilealiases = array( 218 // '/dataroot/' => $CFG->dataroot, 219 // '/cachedir/' => '/var/www/moodle/cache', // for custom $CFG->cachedir locations 220 // '/localcachedir/' => '/var/local/cache', // for custom $CFG->localcachedir locations 221 // '/tempdir/' => '/var/www/moodle/temp', // for custom $CFG->tempdir locations 222 // '/filedir' => '/var/www/moodle/filedir', // for custom $CFG->filedir locations 223 // ); 224 // 225 // YUI caching may be sometimes improved by slasharguments: 226 // $CFG->yuislasharguments = 1; 227 // Some servers may need a special rewrite rule to work around internal path length limitations: 228 // RewriteRule (^.*/theme/yui_combo\.php)(/.*) $1?file=$2 229 // 230 // 231 // Following settings may be used to select session driver, uncomment only one of the handlers. 232 // Database session handler (not compatible with MyISAM): 233 // $CFG->session_handler_class = '\core\session\database'; 234 // $CFG->session_database_acquire_lock_timeout = 120; 235 // 236 // File session handler (file system locking required): 237 // $CFG->session_handler_class = '\core\session\file'; 238 // $CFG->session_file_save_path = $CFG->dataroot.'/sessions'; 239 // 240 // Memcached session handler (requires memcached server and extension): 241 // $CFG->session_handler_class = '\core\session\memcached'; 242 // $CFG->session_memcached_save_path = '127.0.0.1:11211'; 243 // $CFG->session_memcached_prefix = 'memc.sess.key.'; 244 // $CFG->session_memcached_acquire_lock_timeout = 120; 245 // $CFG->session_memcached_lock_expire = 7200; // Ignored if memcached extension <= 2.1.0 246 // 247 // Memcache session handler (requires memcached server and memcache extension): 248 // $CFG->session_handler_class = '\core\session\memcache'; 249 // $CFG->session_memcache_save_path = '127.0.0.1:11211'; 250 // $CFG->session_memcache_acquire_lock_timeout = 120; 251 // ** NOTE: Memcache extension has less features than memcached and may be 252 // less reliable. Use memcached where possible or if you encounter 253 // session problems. ** 254 // 255 // Please be aware that when selecting either Memcached or Memcache for sessions that it is advised to use a dedicated 256 // memcache server. The memcache and memcached extensions do not provide isolated environments for individual uses. 257 // Using the same server for other purposes (MUC for example) can lead to sessions being prematurely removed should 258 // the other uses of the server purge the cache. 259 // 260 // Following setting allows you to alter how frequently is timemodified updated in sessions table. 261 // $CFG->session_update_timemodified_frequency = 20; // In seconds. 262 // 263 // If this setting is set to true, then Moodle will track the IP of the 264 // current user to make sure it hasn't changed during a session. This 265 // will prevent the possibility of sessions being hijacked via XSS, but it 266 // may break things for users coming using proxies that change all the time, 267 // like AOL. 268 // $CFG->tracksessionip = true; 269 // 270 // The following lines are for handling email bounces. 271 // $CFG->handlebounces = true; 272 // $CFG->minbounces = 10; 273 // $CFG->bounceratio = .20; 274 // The next lines are needed both for bounce handling and any other email to module processing. 275 // mailprefix must be EXACTLY four characters. 276 // Uncomment and customise this block for Postfix 277 // $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix. 278 // $CFG->mailprefix = 'mdl-'; // - is the separator for qmail 279 // $CFG->maildomain = 'youremaildomain.com'; 280 // 281 // Enable when setting up advanced reverse proxy load balancing configurations, 282 // it may be also necessary to enable this when using port forwarding. 283 // $CFG->reverseproxy = true; 284 // 285 // Enable when using external SSL appliance for performance reasons. 286 // Please note that site may be accessible via http: or https:, but not both! 287 // $CFG->sslproxy = true; 288 // 289 // This setting will cause the userdate() function not to fix %d in 290 // date strings, and just let them show with a zero prefix. 291 // $CFG->nofixday = true; 292 // 293 // This setting will make some graphs (eg user logs) use lines instead of bars 294 // $CFG->preferlinegraphs = true; 295 // 296 // Enabling this will allow custom scripts to replace existing moodle scripts. 297 // For example: if $CFG->customscripts/course/view.php exists then 298 // it will be used instead of $CFG->wwwroot/course/view.php 299 // At present this will only work for files that include config.php and are called 300 // as part of the url (index.php is implied). 301 // Some examples are: 302 // http://my.moodle.site/course/view.php 303 // http://my.moodle.site/index.php 304 // http://my.moodle.site/admin (index.php implied) 305 // Custom scripts should not include config.php 306 // Warning: Replacing standard moodle scripts may pose security risks and/or may not 307 // be compatible with upgrades. Use this option only if you are aware of the risks 308 // involved. 309 // Specify the full directory path to the custom scripts 310 // $CFG->customscripts = '/home/example/customscripts'; 311 // 312 // Performance profiling 313 // 314 // If you set Debug to "Yes" in the Configuration->Variables page some 315 // performance profiling data will show up on your footer (in default theme). 316 // With these settings you get more granular control over the capture 317 // and printout of the data 318 // 319 // Capture performance profiling data 320 // define('MDL_PERF' , true); 321 // 322 // Capture additional data from DB 323 // define('MDL_PERFDB' , true); 324 // 325 // Print to log (for passive profiling of production servers) 326 // define('MDL_PERFTOLOG' , true); 327 // 328 // Print to footer (works with the default theme) 329 // define('MDL_PERFTOFOOT', true); 330 // 331 // Enable earlier profiling that causes more code to be covered 332 // on every request (db connections, config load, other inits...). 333 // Requires extra configuration to be defined in config.php like: 334 // profilingincluded, profilingexcluded, profilingautofrec, 335 // profilingallowme, profilingallowall, profilinglifetime 336 // $CFG->earlyprofilingenabled = true; 337 // 338 // Force displayed usernames 339 // A little hack to anonymise user names for all students. If you set these 340 // then all non-teachers will always see these for every person. 341 // $CFG->forcefirstname = 'Bruce'; 342 // $CFG->forcelastname = 'Simpson'; 343 // 344 // The following setting will turn SQL Error logging on. This will output an 345 // entry in apache error log indicating the position of the error and the statement 346 // called. This option will action disregarding error_reporting setting. 347 // $CFG->dblogerror = true; 348 // 349 // The following setting will log every database query to a table called adodb_logsql. 350 // Use this setting on a development server only, the table grows quickly! 351 // $CFG->logsql = true; 352 // 353 // The following setting will turn on username logging into Apache log. For full details regarding setting 354 // up of this function please refer to the install section of the document. 355 // $CFG->apacheloguser = 0; // Turn this feature off. Default value. 356 // $CFG->apacheloguser = 1; // Log user id. 357 // $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader. 358 // $CFG->apacheloguser = 3; // Log username. 359 // To get the values logged in Apache's log, add to your httpd.conf 360 // the following statements. In the General part put: 361 // LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat 362 // And in the part specific to your Moodle install / virtualhost: 363 // CustomLog "/your/path/to/log" moodleformat 364 // CAUTION: Use of this option will expose usernames in the Apache log, 365 // If you are going to publish your log, or the output of your web stats analyzer 366 // this will weaken the security of your website. 367 // 368 // Email database connection errors to someone. If Moodle cannot connect to the 369 // database, then email this address with a notice. 370 // 371 // $CFG->emailconnectionerrorsto = '[email protected]'; 372 // 373 // Set the priority of themes from highest to lowest. This is useful (for 374 // example) in sites where the user theme should override all other theme 375 // settings for accessibility reasons. You can also disable types of themes 376 // (other than site) by removing them from the array. The default setting is: 377 // $CFG->themeorder = array('course', 'category', 'session', 'user', 'site'); 378 // NOTE: course, category, session, user themes still require the 379 // respective settings to be enabled 380 // 381 // It is possible to add extra themes directory stored outside of $CFG->dirroot. 382 // This local directory does not have to be accessible from internet. 383 // 384 // $CFG->themedir = '/location/of/extra/themes'; 385 // 386 // It is possible to specify different cache and temp directories, use local fast filesystem 387 // for normal web servers. Server clusters MUST use shared filesystem for cachedir! 388 // Localcachedir is intended for server clusters, it does not have to be shared by cluster nodes. 389 // The directories must not be accessible via web. 390 // 391 // $CFG->tempdir = '/var/www/moodle/temp'; // Files used during one HTTP request only. 392 // $CFG->cachedir = '/var/www/moodle/cache'; // Directory MUST BE SHARED by all cluster nodes, locking required. 393 // $CFG->localcachedir = '/var/local/cache'; // Intended for local node caching. 394 // 395 // Some filesystems such as NFS may not support file locking operations. 396 // Locking resolves race conditions and is strongly recommended for production servers. 397 // $CFG->preventfilelocking = false; 398 // 399 // Site default language can be set via standard administration interface. If you 400 // want to have initial error messages for eventual database connection problems 401 // localized too, you have to set your language code here. 402 // 403 // $CFG->lang = 'yourlangcode'; // for example 'cs' 404 // 405 // When Moodle is about to perform an intensive operation it raises PHP's memory 406 // limit. The following setting should be used on large sites to set the raised 407 // memory limit to something higher. 408 // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G 409 // 410 // $CFG->extramemorylimit = '1024M'; 411 // 412 // Moodle 2.4 introduced a new cache API. 413 // The cache API stores a configuration file within the Moodle data directory and 414 // uses that rather than the database in order to function in a stand-alone manner. 415 // Using altcacheconfigpath you can change the location where this config file is 416 // looked for. 417 // It can either be a directory in which to store the file, or the full path to the 418 // file if you want to take full control. Either way it must be writable by the 419 // webserver. 420 // 421 // $CFG->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php 422 // 423 // The CSS files the Moodle produces can be extremely large and complex, especially 424 // if you are using a custom theme that builds upon several other themes. 425 // In Moodle 2.3 a CSS optimiser was added as an experimental feature for advanced 426 // users. The CSS optimiser organises the CSS in order to reduce the overall number 427 // of rules and styles being sent to the client. It does this by collating the 428 // CSS before it is cached removing excess styles and rules and stripping out any 429 // extraneous content such as comments and empty rules. 430 // The following settings are used to enable and control the optimisation. 431 // 432 // Enable the CSS optimiser. This will only optimise the CSS if themedesignermode 433 // is not enabled. This can be set through the UI however it is noted here as well 434 // because the other CSS optimiser settings can not be set through the UI. 435 // 436 // $CFG->enablecssoptimiser = true; 437 // 438 // If set the CSS optimiser will add stats about the optimisation to the top of 439 // the optimised CSS file. You can then inspect the CSS to see the affect the CSS 440 // optimiser is having. 441 // 442 // $CFG->cssoptimiserstats = true; 443 // 444 // If set the CSS that is optimised will still retain a minimalistic formatting 445 // so that anyone wanting to can still clearly read it. 446 // 447 // $CFG->cssoptimiserpretty = true; 448 // 449 // Use the following flag to completely disable the Available update notifications 450 // feature and hide it from the server administration UI. 451 // 452 // $CFG->disableupdatenotifications = true; 453 // 454 // Use the following flag to completely disable the Automatic updates deployment 455 // feature and hide it from the server administration UI. 456 // 457 // $CFG->disableupdateautodeploy = true; 458 // 459 // Use the following flag to completely disable the On-click add-on installation 460 // feature and hide it from the server administration UI. 461 // 462 // $CFG->disableonclickaddoninstall = true; 463 // 464 // Use the following flag to disable modifications to scheduled tasks 465 // whilst still showing the state of tasks. 466 // 467 // $CFG->preventscheduledtaskchanges = true; 468 // 469 // As of version 2.4 Moodle serves icons as SVG images if the users browser appears 470 // to support SVG. 471 // For those wanting to control the serving of SVG images the following setting can 472 // be defined in your config.php. 473 // If it is not defined then the default (browser detection) will occur. 474 // 475 // To ensure they are always used when available: 476 // $CFG->svgicons = true; 477 // 478 // To ensure they are never used even when available: 479 // $CFG->svgicons = false; 480 // 481 // Some administration options allow setting the path to executable files. This can 482 // potentially cause a security risk. Set this option to true to disable editing 483 // those config settings via the web. They will need to be set explicitly in the 484 // config.php file 485 // $CFG->preventexecpath = true; 486 // 487 // Use the following flag to set userid for noreply user. If not set then moodle will 488 // create dummy user and use -ve value as user id. 489 // $CFG->noreplyuserid = -10; 490 // 491 // As of version 2.6 Moodle supports admin to set support user. If not set, all mails 492 // will be sent to supportemail. 493 // $CFG->supportuserid = -20; 494 // 495 // Moodle 2.7 introduces a locking api for critical tasks (e.g. cron). 496 // The default locking system to use is DB locking for MySQL and Postgres, and File 497 // locking for Oracle and SQLServer. If $CFG->preventfilelocking is set, then the default 498 // will always be DB locking. It can be manually set to one of the lock 499 // factory classes listed below, or one of your own custom classes implementing the 500 // \core\lock\lock_factory interface. 501 // 502 // $CFG->lock_factory = "auto"; 503 // 504 // The list of available lock factories is: 505 // 506 // "\\core\\lock\\file_lock_factory" - File locking 507 // Uses lock files stored by default in the dataroot. Whether this 508 // works on clusters depends on the file system used for the dataroot. 509 // 510 // "\\core\\lock\\db_row_lock_factory" - DB locking based on table rows. 511 // 512 // "\\core\\lock\\postgres_lock_factory" - DB locking based on postgres advisory locks. 513 // 514 // Settings used by the lock factories 515 // 516 // Location for lock files used by the File locking factory. This must exist 517 // on a shared file system that supports locking. 518 // $CFG->lock_file_root = $CFG->dataroot . '/lock'; 519 // 520 //========================================================================= 521 // 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!! 522 //========================================================================= 523 // 524 // Force a debugging mode regardless the settings in the site administration 525 // @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS! 526 // @ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS! 527 // $CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS! 528 // $CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS! 529 // 530 // You can specify a comma separated list of user ids that that always see 531 // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay 532 // for these users only. 533 // $CFG->debugusers = '2'; 534 // 535 // Prevent theme caching 536 // $CFG->themedesignermode = true; // NOT FOR PRODUCTION SERVERS! 537 // 538 // Prevent JS caching 539 // $CFG->cachejs = false; // NOT FOR PRODUCTION SERVERS! 540 // 541 // Restrict which YUI logging statements are shown in the browser console. 542 // For details see the upstream documentation: 543 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logInclude 544 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logExclude 545 // $CFG->yuiloginclude = array( 546 // 'moodle-core-dock-loader' => true, 547 // 'moodle-course-categoryexpander' => true, 548 // ); 549 // $CFG->yuilogexclude = array( 550 // 'moodle-core-dock' => true, 551 // 'moodle-core-notification' => true, 552 // ); 553 // 554 // Set the minimum log level for YUI logging statements. 555 // For details see the upstream documentation: 556 // http://yuilibrary.com/yui/docs/api/classes/config.html#property_logLevel 557 // $CFG->yuiloglevel = 'debug'; 558 // 559 // Prevent core_string_manager application caching 560 // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS! 561 // 562 // When working with production data on test servers, no emails or other messages 563 // should ever be send to real users 564 // $CFG->noemailever = true; // NOT FOR PRODUCTION SERVERS! 565 // 566 // Divert all outgoing emails to this address to test and debug emailing features 567 // $CFG->divertallemailsto = '[email protected]'; // NOT FOR PRODUCTION SERVERS! 568 // 569 // Uncomment if you want to allow empty comments when modifying install.xml files. 570 // $CFG->xmldbdisablecommentchecking = true; // NOT FOR PRODUCTION SERVERS! 571 // 572 // Since 2.0 sql queries are not shown during upgrade by default. 573 // Please note that this setting may produce very long upgrade page on large sites. 574 // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS! 575 // 576 // Add SQL queries to the output of cron, just before their execution 577 // $CFG->showcronsql = true; 578 // 579 // Force developer level debug and add debug info to the output of cron 580 // $CFG->showcrondebugging = true; 581 // 582 //========================================================================= 583 // 8. FORCED SETTINGS 584 //========================================================================= 585 // It is possible to specify normal admin settings here, the point is that 586 // they can not be changed through the standard admin settings pages any more. 587 // 588 // Core settings are specified directly via assignment to $CFG variable. 589 // Example: 590 // $CFG->somecoresetting = 'value'; 591 // 592 // Plugin settings have to be put into a special array. 593 // Example: 594 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'secondsetting' => 'othervalue'), 595 // 'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue')); 596 // Module default settings with advanced/locked checkboxes can be set too. To do this, add 597 // an extra config with '_adv' or '_locked' as a suffix and set the value to true or false. 598 // Example: 599 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'settingname_locked' => true, 'settingname_adv' => true)); 600 // 601 //========================================================================= 602 // 9. PHPUNIT SUPPORT 603 //========================================================================= 604 // $CFG->phpunit_prefix = 'phpu_'; 605 // $CFG->phpunit_dataroot = '/home/example/phpu_moodledata'; 606 // $CFG->phpunit_directorypermissions = 02777; // optional 607 // 608 // 609 //========================================================================= 610 // 10. SECRET PASSWORD SALT 611 //========================================================================= 612 // A site-wide password salt is no longer used in new installations. 613 // If upgrading from 2.6 or older, keep all existing salts in config.php file. 614 // 615 // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1'; 616 // 617 // You may also have some alternative salts to allow migration from previously 618 // used salts. 619 // 620 // $CFG->passwordsaltalt1 = ''; 621 // $CFG->passwordsaltalt2 = ''; 622 // $CFG->passwordsaltalt3 = ''; 623 // .... 624 // $CFG->passwordsaltalt19 = ''; 625 // $CFG->passwordsaltalt20 = ''; 626 // 627 // 628 //========================================================================= 629 // 11. BEHAT SUPPORT 630 //========================================================================= 631 // Behat test site needs a unique www root, data directory and database prefix: 632 // 633 // $CFG->behat_wwwroot = 'http://127.0.0.1/moodle'; 634 // $CFG->behat_prefix = 'bht_'; 635 // $CFG->behat_dataroot = '/home/example/bht_moodledata'; 636 // 637 // You can override default Moodle configuration for Behat and add your own 638 // params; here you can add more profiles, use different Mink drivers than Selenium... 639 // These params would be merged with the default Moodle behat.yml, giving priority 640 // to the ones specified here. The array format is YAML, following the Behat 641 // params hierarchy. More info: http://docs.behat.org/guides/7.config.html 642 // Example: 643 // $CFG->behat_config = array( 644 // 'default' => array( 645 // 'formatter' => array( 646 // 'name' => 'pretty', 647 // 'parameters' => array( 648 // 'decorated' => true, 649 // 'verbose' => false 650 // ) 651 // ) 652 // ), 653 // 'Mac-Firefox' => array( 654 // 'extensions' => array( 655 // 'Behat\MinkExtension\Extension' => array( 656 // 'selenium2' => array( 657 // 'browser' => 'firefox', 658 // 'capabilities' => array( 659 // 'platform' => 'OS X 10.6', 660 // 'version' => 20 661 // ) 662 // ) 663 // ) 664 // ) 665 // ), 666 // 'Mac-Safari' => array( 667 // 'extensions' => array( 668 // 'Behat\MinkExtension\Extension' => array( 669 // 'selenium2' => array( 670 // 'browser' => 'safari', 671 // 'capabilities' => array( 672 // 'platform' => 'OS X 10.8', 673 // 'version' => 6 674 // ) 675 // ) 676 // ) 677 // ) 678 // ) 679 // ); 680 // 681 // You can force the browser session (not user's sessions) to restart after N seconds. This could 682 // be useful if you are using a cloud-based service with time restrictions in the browser side. 683 // Setting this value the browser session that Behat is using will be restarted. Set the time in 684 // seconds. Is not recommended to use this setting if you don't explicitly need it. 685 // Example: 686 // $CFG->behat_restart_browser_after = 7200; // Restarts the browser session after 2 hours 687 // 688 // All this page's extra Moodle settings are compared against a white list of allowed settings 689 // (the basic and behat_* ones) to avoid problems with production environments. This setting can be 690 // used to expand the default white list with an array of extra settings. 691 // Example: 692 // $CFG->behat_extraallowedsettings = array('logsql', 'dblogerror'); 693 // 694 // You should explicitly allow the usage of the deprecated behat steps, otherwise an exception will 695 // be thrown when using them. The setting is disabled by default. 696 // Example: 697 // $CFG->behat_usedeprecated = true; 698 // 699 // Including feature files from directories outside the dirroot is possible if required. The setting 700 // requires that the running user has executable permissions on all parent directories in the paths. 701 // Example: 702 // $CFG->behat_additionalfeatures = array('/home/developer/code/wipfeatures'); 703 // 704 // You can make behat save several dumps when a scenario fails. The dumps currently saved are: 705 // * a dump of the DOM in it's state at the time of failure; and 706 // * a screenshot (JavaScript is required for the screenshot functionality, so not all browsers support this option) 707 // Example: 708 // $CFG->behat_faildump_path = '/my/path/to/save/failure/dumps'; 709 // 710 //========================================================================= 711 // 12. DEVELOPER DATA GENERATOR 712 //========================================================================= 713 // 714 // The developer data generator tool is intended to be used only in development or testing sites and 715 // it's usage in production environments is not recommended; if it is used to create JMeter test plans 716 // is even less recommended as JMeter needs to log in as site course users. JMeter needs to know the 717 // users passwords but would be dangerous to have a default password as everybody would know it, which would 718 // be specially dangerouse if somebody uses this tool in a production site, so in order to prevent unintended 719 // uses of the tool and undesired accesses as well, is compulsory to set a password for the users 720 // generated by this tool, but only in case you want to generate a JMeter test. The value should be a string. 721 // Example: 722 // $CFG->tool_generator_users_password = 'examplepassword'; 723 // 724 //========================================================================= 725 // 13. SYSTEM PATHS (You need to set following, depending on your system) 726 //========================================================================= 727 // Ghostscript path. 728 // On most Linux installs, this can be left as '/usr/bin/gs'. 729 // On Windows it will be something like 'c:\gs\bin\gswin32c.exe' (make sure 730 // there are no spaces in the path - if necessary copy the files 'gswin32c.exe' 731 // and 'gsdll32.dll' to a new folder without a space in the path) 732 // $CFG->pathtogs = '/usr/bin/gs'; 733 // 734 // Clam AV path. 735 // Probably something like /usr/bin/clamscan or /usr/bin/clamdscan. You need 736 // this in order for clam AV to run. 737 // $CFG->pathtoclam = ''; 738 // 739 // Path to du. 740 // Probably something like /usr/bin/du. If you enter this, pages that display 741 // directory contents will run much faster for directories with a lot of files. 742 // $CFG->pathtodu = ''; 743 // 744 // Path to aspell. 745 // To use spell-checking within the editor, you MUST have aspell 0.50 or later 746 // installed on your server, and you must specify the correct path to access the 747 // aspell binary. On Unix/Linux systems, this path is usually /usr/bin/aspell, 748 // but it might be something else. 749 // $CFG->aspellpath = ''; 750 // 751 // Path to dot. 752 // Probably something like /usr/bin/dot. To be able to generate graphics from 753 // DOT files, you must have installed the dot executable and point to it here. 754 // Note that, for now, this only used by the profiling features 755 // (Development->Profiling) built into Moodle. 756 // $CFG->pathtodot = ''; 757 758 //========================================================================= 759 // ALL DONE! To continue installation, visit your main page with a browser 760 //========================================================================= 761 762 require_once(dirname(__FILE__) . '/lib/setup.php'); // Do not edit 763 764 // There is no php closing tag in this file, 765 // it is intentional because it prevents trailing whitespace problems!
title
Description
Body
title
Description
Body
title
Description
Body
title
Body
| Generated: Fri Nov 28 20:29:05 2014 | Cross-referenced by PHPXref 0.7.1 |