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