MDL-21250 capital letters removal
[moodle.git] / config-dist.php
bloba5409db941aa5a21cdf44e52fa15f15d3ea4da09
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();
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. //
41 $CFG->dbtype = 'pgsql'; // 'pgsql', 'mysqli', 'mssql' 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
54 // used? if you set it to 'true' here,
55 // set dbhost to 'localhost'
56 'dbport' => '', // the TCP port number to use when connecting
57 // to the server. keep empty string for the
58 // default port
62 //=========================================================================
63 // 2. SECRET PASSWORD SALT
64 //=========================================================================
65 // User password salt is very important security feature, it is created
66 // automatically in installer, you have to uncomment and modify value
67 // on the next line if you are creating config.php manually.
69 // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1';
71 // After changing the main salt you have to copy old value into one
72 // of the following settings - this allows migration to the new salt
73 // during the next login of each user.
75 // $CFG->passwordsaltalt1 = '';
76 // $CFG->passwordsaltalt2 = '';
77 // $CFG->passwordsaltalt3 = '';
78 // ....
79 // $CFG->passwordsaltalt19 = '';
80 // $CFG->passwordsaltalt20 = '';
83 //=========================================================================
84 // 3. WEB SITE LOCATION
85 //=========================================================================
86 // Now you need to tell Moodle where it is located. Specify the full
87 // web address to where moodle has been installed. If your web site
88 // is accessible via multiple URLs then choose the most natural one
89 // that your students would use. Do not include a trailing slash
91 // If you need both intranet and Internet access please read
92 // http://docs.moodle.org/en/masquerading
94 $CFG->wwwroot = 'http://example.com/moodle';
97 //=========================================================================
98 // 4. DATA FILES LOCATION
99 //=========================================================================
100 // Now you need a place where Moodle can save uploaded files. This
101 // directory should be readable AND WRITEABLE by the web server user
102 // (usually 'nobody' or 'apache'), but it should not be accessible
103 // directly via the web.
105 // - On hosting systems you might need to make sure that your "group" has
106 // no permissions at all, but that "others" have full permissions.
108 // - On Windows systems you might specify something like 'c:\moodledata'
110 $CFG->dataroot = '/home/example/moodledata';
113 //=========================================================================
114 // 5. DATA FILES PERMISSIONS
115 //=========================================================================
116 // The following parameter sets the permissions of new directories
117 // created by Moodle within the data directory. The format is in
118 // octal format (as used by the Unix utility chmod, for example).
119 // The default is usually OK, but you may want to change it to 0750
120 // if you are concerned about world-access to the files (you will need
121 // to make sure the web server process (eg Apache) can access the files.
122 // NOTE: the prefixed 0 is important, and don't use quotes.
124 $CFG->directorypermissions = 02777;
127 //=========================================================================
128 // 6. DIRECTORY LOCATION (most people can just ignore this setting)
129 //=========================================================================
130 // A very few webhosts use /admin as a special URL for you to access a
131 // control panel or something. Unfortunately this conflicts with the
132 // standard location for the Moodle admin pages. You can fix this by
133 // renaming the admin directory in your installation, and putting that
134 // new name here. eg "moodleadmin". This will fix admin links in Moodle.
136 $CFG->admin = 'admin';
139 //=========================================================================
140 // 7. OTHER MISCELLANEOUS SETTINGS (ignore these for new installations)
141 //=========================================================================
143 // These are additional tweaks for which no GUI exists in Moodle yet.
145 // Starting in PHP 5.3 administrators should specify default timezone
146 // in PHP.ini, you can also specify it here if needed.
147 // See details at: http://php.net/manual/en/function.date-default-timezone-set.php
148 // List of time zones at: http://php.net/manual/en/timezones.php
149 // date_default_timezone_set('Australia/Perth');
151 // Change the key pair lifetime for Moodle Networking
152 // The default is 28 days. You would only want to change this if the key
153 // was not getting regenerated for any reason. You would probably want
154 // make it much longer. Note that you'll need to delete and manually update
155 // any existing key.
156 // $CFG->mnetkeylifetime = 28;
158 // Allow user passwords to be included in backup files. Very dangerous
159 // setting as far as it publishes password hashes that can be unencrypted
160 // if the backup file is publicy available. Use it only if you can guarantee
161 // that all your backup files remain only privacy available and are never
162 // shared out from your site/institution!
163 // $CFG->includeuserpasswordsinbackup = true;
165 // Completely disable user creation when restoring a course, bypassing any
166 // permissions granted via roles and capabilities. Enabling this setting
167 // results in the restore process stopping when a user attempts to restore a
168 // course requiring users to be created.
169 // $CFG->disableusercreationonrestore = true;
171 // Keep the temporary directories used by backup and restore without being
172 // deleted at the end of the process. Use it if you want to debug / view
173 // all the information stored there after the process has ended. Note that
174 // those directories may be deleted (after some ttl) both by cron and / or
175 // by new backup / restore invocations.
176 // $CFG->keeptempdirectoriesonbackup = true;
178 // Modify the restore process in order to force the "user checks" to assume
179 // that the backup originated from a different site, so detection of matching
180 // users is performed with different (more "relaxed") rules. Note that this is
181 // only useful if the backup file has been created using Moodle < 1.9.4 and the
182 // site has been rebuilt from scratch using backup files (not the best way btw).
183 // If you obtain user conflicts on restore, rather than enabling this setting
184 // permanently, try restoring the backup on a different site, back it up again
185 // and then restore on the target server.
186 // $CFG->forcedifferentsitecheckingusersonrestore = true;
188 // Prevent stats processing and hide the GUI
189 // $CFG->disablestatsprocessing = true;
191 // Setting this to true will enable admins to edit any post at any time
192 // $CFG->admineditalways = true;
194 // These variables define DEFAULT block variables for new courses
195 // If this one is set it overrides all others and is the only one used.
196 // $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
198 // These variables define the specific settings for defined course formats.
199 // They override any settings defined in the formats own config file.
200 // $CFG->defaultblocks_site = 'site_main_menu,admin,course_list:course_summary,calendar_month';
201 // $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,admin,course_list';
202 // $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
203 // $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
205 // These blocks are used when no other default setting is found.
206 // $CFG->defaultblocks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
208 // The blocks in this list will be protected from deletion, and this is primarily
209 // used to protect the navigation and settings blocks which can be very hard to
210 // get back if accidentally delete.
211 // $CFG->undeletableblocktypes = 'navigation,settings';
213 // You can specify a different class to be created for the $PAGE global, and to
214 // compute which blocks appear on each page. However, I cannot think of any good
215 // reason why you would need to change that. It just felt wrong to hard-code the
216 // the class name. You are stronly advised not to use these to settings unless
217 // you are absolutely sure you know what you are doing.
218 // $CFG->moodlepageclass = 'moodle_page';
219 // $CFG->blockmanagerclass = 'block_manager';
221 // Seconds for files to remain in caches. Decrease this if you are worried
222 // about students being served outdated versions of uploaded files.
223 // $CFG->filelifetime = 86400;
225 // This setting will prevent the 'My Courses' page being displayed when a student
226 // logs in. The site front page will always show the same (logged-out) view.
227 // $CFG->disablemycourses = true;
229 // If this setting is set to true, then Moodle will track the IP of the
230 // current user to make sure it hasn't changed during a session. This
231 // will prevent the possibility of sessions being hijacked via XSS, but it
232 // may break things for users coming using proxies that change all the time,
233 // like AOL.
234 // $CFG->tracksessionip = true;
237 // The following lines are for handling email bounces.
238 // $CFG->handlebounces = true;
239 // $CFG->minbounces = 10;
240 // $CFG->bounceratio = .20;
241 // The next lines are needed both for bounce handling and any other email to module processing.
242 // mailprefix must be EXACTLY four characters.
243 // Uncomment and customise this block for Postfix
244 // $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix.
245 // $CFG->mailprefix = 'mdl-'; // - is the separator for qmail
246 // $CFG->maildomain = 'youremaildomain.com';
248 // Enable when setting up advanced reverse proxy load balancing configurations,
249 // it may be also necessary to enable this when using port forwarding.
250 // $CFG->reverseproxy = true;
252 // Enable when using external SSL appliance for performance reasons.
253 // Please note that site may be accessible via https: or https:, but not both!
254 // $CFG->sslproxy = true;
256 // This setting will cause the userdate() function not to fix %d in
257 // date strings, and just let them show with a zero prefix.
258 // $CFG->nofixday = true;
260 // This setting will make some graphs (eg user logs) use lines instead of bars
261 // $CFG->preferlinegraphs = true;
263 // Enabling this will allow custom scripts to replace existing moodle scripts.
264 // For example: if $CFG->customscripts/course/view.php exists then
265 // it will be used instead of $CFG->wwwroot/course/view.php
266 // At present this will only work for files that include config.php and are called
267 // as part of the url (index.php is implied).
268 // Some examples are:
269 // http://my.moodle.site/course/view.php
270 // http://my.moodle.site/index.php
271 // http://my.moodle.site/admin (index.php implied)
272 // Custom scripts should not include config.php
273 // Warning: Replacing standard moodle scripts may pose security risks and/or may not
274 // be compatible with upgrades. Use this option only if you are aware of the risks
275 // involved.
276 // Specify the full directory path to the custom scripts
277 // $CFG->customscripts = '/home/example/customscripts';
279 // Performance profiling
281 // If you set Debug to "Yes" in the Configuration->Variables page some
282 // performance profiling data will show up on your footer (in default theme).
283 // With these settings you get more granular control over the capture
284 // and printout of the data
286 // Capture performance profiling data
287 // define('MDL_PERF' , true);
289 // Capture additional data from DB
290 // define('MDL_PERFDB' , true);
292 // Print to log (for passive profiling of production servers)
293 // define('MDL_PERFTOLOG' , true);
295 // Print to footer (works with the default theme)
296 // define('MDL_PERFTOFOOT', true);
298 // Force displayed usernames
299 // A little hack to anonymise user names for all students. If you set these
300 // then all non-teachers will always see these for every person.
301 // $CFG->forcefirstname = 'Bruce';
302 // $CFG->forcelastname = 'Simpson';
304 // The following setting will turn SQL Error logging on. This will output an
305 // entry in apache error log indicating the position of the error and the statement
306 // called. This option will action disregarding error_reporting setting.
307 // $CFG->dblogerror = true;
309 // The following setting will log every database query to a table called adodb_logsql.
310 // Use this setting on a development server only, the table grows quickly!
311 // $CFG->logsql = true;
313 // The following setting will turn on username logging into Apache log. For full details regarding setting
314 // up of this function please refer to the install section of the document.
315 // $CFG->apacheloguser = 0; // Turn this feature off. Default value.
316 // $CFG->apacheloguser = 1; // Log user id.
317 // $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
318 // $CFG->apacheloguser = 3; // Log username.
319 // To get the values logged in Apache's log, add to your httpd.conf
320 // the following statements. In the General part put:
321 // LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat
322 // And in the part specific to your Moodle install / virtualhost:
323 // CustomLog "/your/path/to/log" moodleformat
324 // CAUTION: Use of this option will expose usernames in the Apache log,
325 // If you are going to publish your log, or the output of your web stats analyzer
326 // this will weaken the security of your website.
328 // Email database connection errors to someone. If Moodle cannot connect to the
329 // database, then email this address with a notice.
331 // $CFG->emailconnectionerrorsto = 'your@emailaddress.com';
333 // Set the priority of themes from highest to lowest. This is useful (for
334 // example) in sites where the user theme should override all other theme
335 // settings for accessibility reasons. You can also disable types of themes
336 // (other than site) by removing them from the array. The default setting is:
337 // $CFG->themeorder = array('course', 'category', 'session', 'user', 'site');
338 // NOTE: course, category, session, user themes still require the
339 // respective settings to be enabled
341 // It is possible to add extra themes directory stored outside of $CFG->dirroot.
342 // This local directory does not have to be accessible from internet.
344 // $CFG->themedir = '/location/of/extra/themes';
346 // Site default language can be set via standard administration interface. If you
347 // want to have initial error messages for eventual database connection problems
348 // localized too, you have to set your language code here.
350 // $CFG->lang = 'yourlangcode'; // for example 'cs'
352 // When Moodle is about to perform an intensive operation it raises PHP's memory
353 // limit. The following setting should be used on large sites to set the raised
354 // memory limit to something higher.
355 // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G
357 // $CFG->extramemorylimit = 1G;
360 //=========================================================================
361 // 8. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
362 //=========================================================================
364 // Force a debugging mode regardless the settings in the site administration
365 // @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!
366 // @ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
367 // $CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!
368 // $CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!
370 // You can specify a comma separated list of user ids that that always see
371 // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
372 // for these users only.
373 // $CFG->debugusers = '2';
375 // Prevent theme caching
376 // $CFG->themerev = -1; // NOT FOR PRODUCTION SERVERS!
378 // Prevent core_string_manager on-disk cache
379 // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!
381 // When working with production data on test servers, no emails should ever be send to real users
382 // $CFG->noemailever = true; // NOT FOR PRODUCTION SERVERS!
384 // Divert all outgoing emails to this address to test and debug emailing features
385 // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
387 // Specify prefix for fake unit test tables. If not specified only tests
388 // that do not need fake tables will be executed.
389 // $CFG->unittestprefix = 'tst_'; // NOT FOR PRODUCTION SERVERS!
391 // special magic evil developer only wanting to edit the xmldb files manually
392 // AND don't use the XMLDBEditor nor the prev/next stuff at all (Mahara and others)
393 // Uncomment these if you're lazy like Penny
394 // $CFG->xmldbdisablecommentchecking = true; // NOT FOR PRODUCTION SERVERS!
395 // $CFG->xmldbdisablenextprevchecking = true; // NOT FOR PRODUCTION SERVERS!
397 // Special magic - evil developer only wanting to edit xmldb files manually
398 // AND allowing the XMLDBEditor to reconstruct the prev/next elements every
399 // time one file is loaded and saved (Moodle).
400 // Uncomment this if you're lazy like Petr
401 // $CFG->xmldbreconstructprevnext = true; // NOT FOR PRODUCTION SERVERS!
403 // Since 2.0 sql queries are not shown during upgrade by default.
404 // Please note that this setting may produce very long upgrade page on large sites.
405 // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!
407 // Add SQL queries to the output of cron, just before their execution
408 // $CFG->showcronsql = true;
410 // Force developer level debug and add debug info to the output of cron
411 // $CFG->showcrondebugging = true;
413 //=========================================================================
414 // 9. FORCED SETTINGS
415 //=========================================================================
416 // It is possible to specify normal admin settings here, the point is that
417 // they can not be changed through the standard admin settings pages any more.
419 // Core settings are specified directly via assignment to $CFG variable.
420 // Example:
421 // $CFG->somecoresetting = 'value';
423 // Plugin settings have to be put into a special array.
424 // Example:
425 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'secondsetting' => 'othervalue'),
426 // 'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));
429 //=========================================================================
430 // ALL DONE! To continue installation, visit your main page with a browser
431 //=========================================================================
433 require_once(dirname(__FILE__) . '/lib/setup.php'); // Do not edit
435 // There is no php closing tag in this file,
436 // it is intentional because it prevents trailing whitespace problems!