MDL-35510 theme_mymobile: RTL fixes for course and category names in style/jmobile11_...
[moodle.git] / config-dist.php
blob2e38635377f7971701d803836299957d1d34f609
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', '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
65 //=========================================================================
66 // 2. SECRET PASSWORD SALT
67 //=========================================================================
68 // User password salt is very important security feature, it is created
69 // automatically in installer, you have to uncomment and modify value
70 // on the next line if you are creating config.php manually.
72 // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1';
74 // After changing the main salt you have to copy old value into one
75 // of the following settings - this allows migration to the new salt
76 // during the next login of each user.
78 // $CFG->passwordsaltalt1 = '';
79 // $CFG->passwordsaltalt2 = '';
80 // $CFG->passwordsaltalt3 = '';
81 // ....
82 // $CFG->passwordsaltalt19 = '';
83 // $CFG->passwordsaltalt20 = '';
86 //=========================================================================
87 // 3. WEB SITE LOCATION
88 //=========================================================================
89 // Now you need to tell Moodle where it is located. Specify the full
90 // web address to where moodle has been installed. If your web site
91 // is accessible via multiple URLs then choose the most natural one
92 // that your students would use. Do not include a trailing slash
94 // If you need both intranet and Internet access please read
95 // http://docs.moodle.org/en/masquerading
97 $CFG->wwwroot = 'http://example.com/moodle';
100 //=========================================================================
101 // 4. DATA FILES LOCATION
102 //=========================================================================
103 // Now you need a place where Moodle can save uploaded files. This
104 // directory should be readable AND WRITEABLE by the web server user
105 // (usually 'nobody' or 'apache'), but it should not be accessible
106 // directly via the web.
108 // - On hosting systems you might need to make sure that your "group" has
109 // no permissions at all, but that "others" have full permissions.
111 // - On Windows systems you might specify something like 'c:\moodledata'
113 $CFG->dataroot = '/home/example/moodledata';
116 //=========================================================================
117 // 5. DATA FILES PERMISSIONS
118 //=========================================================================
119 // The following parameter sets the permissions of new directories
120 // created by Moodle within the data directory. The format is in
121 // octal format (as used by the Unix utility chmod, for example).
122 // The default is usually OK, but you may want to change it to 0750
123 // if you are concerned about world-access to the files (you will need
124 // to make sure the web server process (eg Apache) can access the files.
125 // NOTE: the prefixed 0 is important, and don't use quotes.
127 $CFG->directorypermissions = 02777;
130 //=========================================================================
131 // 6. DIRECTORY LOCATION (most people can just ignore this setting)
132 //=========================================================================
133 // A very few webhosts use /admin as a special URL for you to access a
134 // control panel or something. Unfortunately this conflicts with the
135 // standard location for the Moodle admin pages. You can fix this by
136 // renaming the admin directory in your installation, and putting that
137 // new name here. eg "moodleadmin". This will fix admin links in Moodle.
139 $CFG->admin = 'admin';
142 //=========================================================================
143 // 7. OTHER MISCELLANEOUS SETTINGS (ignore these for new installations)
144 //=========================================================================
146 // These are additional tweaks for which no GUI exists in Moodle yet.
148 // Starting in PHP 5.3 administrators should specify default timezone
149 // in PHP.ini, you can also specify it here if needed.
150 // See details at: http://php.net/manual/en/function.date-default-timezone-set.php
151 // List of time zones at: http://php.net/manual/en/timezones.php
152 // date_default_timezone_set('Australia/Perth');
154 // Change the key pair lifetime for Moodle Networking
155 // The default is 28 days. You would only want to change this if the key
156 // was not getting regenerated for any reason. You would probably want
157 // make it much longer. Note that you'll need to delete and manually update
158 // any existing key.
159 // $CFG->mnetkeylifetime = 28;
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,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,course_list:course_summary,calendar_month';
204 // $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,course_list';
205 // $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,course_list:news_items,calendar_upcoming,recent_activity';
206 // $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,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,course_list:news_items,calendar_upcoming,recent_activity';
211 // You can specify a different class to be created for the $PAGE global, and to
212 // compute which blocks appear on each page. However, I cannot think of any good
213 // reason why you would need to change that. It just felt wrong to hard-code the
214 // the class name. You are strongly advised not to use these to settings unless
215 // you are absolutely sure you know what you are doing.
216 // $CFG->moodlepageclass = 'moodle_page';
217 // $CFG->moodlepageclassfile = "$CFG->dirroot/local/myplugin/mypageclass.php";
218 // $CFG->blockmanagerclass = 'block_manager';
219 // $CFG->blockmanagerclassfile = "$CFG->dirroot/local/myplugin/myblockamanagerclass.php";
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 // Some web servers can offload the file serving from PHP process,
226 // comment out one the following options to enable it in Moodle:
227 // $CFG->xsendfile = 'X-Sendfile'; // Apache {@see https://tn123.org/mod_xsendfile/}
228 // $CFG->xsendfile = 'X-LIGHTTPD-send-file'; // Lighttpd {@see http://redmine.lighttpd.net/projects/lighttpd/wiki/X-LIGHTTPD-send-file}
229 // $CFG->xsendfile = 'X-Accel-Redirect'; // Nginx {@see http://wiki.nginx.org/XSendfile}
230 // If your X-Sendfile implementation (usually Nginx) uses directory aliases specify them
231 // in the following array setting:
232 // $CFG->xsendfilealiases = array(
233 // '/dataroot/' => $CFG->dataroot,
234 // '/cachedir/' => '/var/www/moodle/cache', // for custom $CFG->cachedir locations
235 // '/tempdir/' => '/var/www/moodle/temp', // for custom $CFG->tempdir locations
236 // '/filedir' => '/var/www/moodle/filedir', // for custom $CFG->filedir locations
237 // );
239 // YUI caching may be sometimes improved by slasharguments:
240 // $CFG->yuislasharguments = 1;
241 // Some servers may need a special rewrite rule to work around internal path length limitations:
242 // RewriteRule (^.*/theme/yui_combo\.php)(/.*) $1?file=$2
245 // This setting will prevent the 'My Courses' page being displayed when a student
246 // logs in. The site front page will always show the same (logged-out) view.
247 // $CFG->disablemycourses = true;
249 // If this setting is set to true, then Moodle will track the IP of the
250 // current user to make sure it hasn't changed during a session. This
251 // will prevent the possibility of sessions being hijacked via XSS, but it
252 // may break things for users coming using proxies that change all the time,
253 // like AOL.
254 // $CFG->tracksessionip = true;
256 // The following lines are for handling email bounces.
257 // $CFG->handlebounces = true;
258 // $CFG->minbounces = 10;
259 // $CFG->bounceratio = .20;
260 // The next lines are needed both for bounce handling and any other email to module processing.
261 // mailprefix must be EXACTLY four characters.
262 // Uncomment and customise this block for Postfix
263 // $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix.
264 // $CFG->mailprefix = 'mdl-'; // - is the separator for qmail
265 // $CFG->maildomain = 'youremaildomain.com';
267 // Enable when setting up advanced reverse proxy load balancing configurations,
268 // it may be also necessary to enable this when using port forwarding.
269 // $CFG->reverseproxy = true;
271 // Enable when using external SSL appliance for performance reasons.
272 // Please note that site may be accessible via https: or https:, but not both!
273 // $CFG->sslproxy = true;
275 // This setting will cause the userdate() function not to fix %d in
276 // date strings, and just let them show with a zero prefix.
277 // $CFG->nofixday = true;
279 // This setting will make some graphs (eg user logs) use lines instead of bars
280 // $CFG->preferlinegraphs = true;
282 // Enabling this will allow custom scripts to replace existing moodle scripts.
283 // For example: if $CFG->customscripts/course/view.php exists then
284 // it will be used instead of $CFG->wwwroot/course/view.php
285 // At present this will only work for files that include config.php and are called
286 // as part of the url (index.php is implied).
287 // Some examples are:
288 // http://my.moodle.site/course/view.php
289 // http://my.moodle.site/index.php
290 // http://my.moodle.site/admin (index.php implied)
291 // Custom scripts should not include config.php
292 // Warning: Replacing standard moodle scripts may pose security risks and/or may not
293 // be compatible with upgrades. Use this option only if you are aware of the risks
294 // involved.
295 // Specify the full directory path to the custom scripts
296 // $CFG->customscripts = '/home/example/customscripts';
298 // Performance profiling
300 // If you set Debug to "Yes" in the Configuration->Variables page some
301 // performance profiling data will show up on your footer (in default theme).
302 // With these settings you get more granular control over the capture
303 // and printout of the data
305 // Capture performance profiling data
306 // define('MDL_PERF' , true);
308 // Capture additional data from DB
309 // define('MDL_PERFDB' , true);
311 // Print to log (for passive profiling of production servers)
312 // define('MDL_PERFTOLOG' , true);
314 // Print to footer (works with the default theme)
315 // define('MDL_PERFTOFOOT', true);
317 // Enable earlier profiling that causes more code to be covered
318 // on every request (db connections, config load, other inits...).
319 // Requires extra configuration to be defined in config.php like:
320 // profilingincluded, profilingexcluded, profilingautofrec,
321 // profilingallowme, profilingallowall, profilinglifetime
322 // $CFG->earlyprofilingenabled = true;
324 // Force displayed usernames
325 // A little hack to anonymise user names for all students. If you set these
326 // then all non-teachers will always see these for every person.
327 // $CFG->forcefirstname = 'Bruce';
328 // $CFG->forcelastname = 'Simpson';
330 // The following setting will turn SQL Error logging on. This will output an
331 // entry in apache error log indicating the position of the error and the statement
332 // called. This option will action disregarding error_reporting setting.
333 // $CFG->dblogerror = true;
335 // The following setting will log every database query to a table called adodb_logsql.
336 // Use this setting on a development server only, the table grows quickly!
337 // $CFG->logsql = true;
339 // The following setting will turn on username logging into Apache log. For full details regarding setting
340 // up of this function please refer to the install section of the document.
341 // $CFG->apacheloguser = 0; // Turn this feature off. Default value.
342 // $CFG->apacheloguser = 1; // Log user id.
343 // $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
344 // $CFG->apacheloguser = 3; // Log username.
345 // To get the values logged in Apache's log, add to your httpd.conf
346 // the following statements. In the General part put:
347 // LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat
348 // And in the part specific to your Moodle install / virtualhost:
349 // CustomLog "/your/path/to/log" moodleformat
350 // CAUTION: Use of this option will expose usernames in the Apache log,
351 // If you are going to publish your log, or the output of your web stats analyzer
352 // this will weaken the security of your website.
354 // Email database connection errors to someone. If Moodle cannot connect to the
355 // database, then email this address with a notice.
357 // $CFG->emailconnectionerrorsto = 'your@emailaddress.com';
359 // Set the priority of themes from highest to lowest. This is useful (for
360 // example) in sites where the user theme should override all other theme
361 // settings for accessibility reasons. You can also disable types of themes
362 // (other than site) by removing them from the array. The default setting is:
363 // $CFG->themeorder = array('course', 'category', 'session', 'user', 'site');
364 // NOTE: course, category, session, user themes still require the
365 // respective settings to be enabled
367 // It is possible to add extra themes directory stored outside of $CFG->dirroot.
368 // This local directory does not have to be accessible from internet.
370 // $CFG->themedir = '/location/of/extra/themes';
372 // It is possible to specify different cache and temp directories, use local fast filesystem.
373 // The directories must not be accessible via web.
375 // $CFG->tempdir = '/var/www/moodle/temp';
376 // $CFG->cachedir = '/var/www/moodle/cache';
378 // Some filesystems such as NFS may not support file locking operations.
379 // Locking resolves race conditions and is strongly recommended for production servers.
380 // $CFG->preventfilelocking = false;
382 // If $CFG->langstringcache is enabled (which should always be in production
383 // environment), Moodle keeps aggregated strings in its own internal format
384 // optimised for performance. By default, this on-disk cache is created in
385 // $CFG->cachedir/lang. In cluster environment, you may wish to specify
386 // an alternative location of this cache so that each web server in the cluster
387 // uses its own local cache and does not need to access the shared dataroot.
388 // Make sure that the web server process has write permission to this location
389 // and that it has permission to remove the folder, too (so that the cache can
390 // be pruned).
392 // $CFG->langcacheroot = '/var/www/moodle/htdocs/altcache/lang';
394 // If $CFG->langcache is enabled (which should always be in production
395 // environment), Moodle stores the list of available languages in a cache file.
396 // By default, the file $CFG->dataroot/languages is used. You may wish to
397 // specify an alternative location of this cache file.
399 // $CFG->langmenucachefile = '/var/www/moodle/htdocs/altcache/languages';
401 // Site default language can be set via standard administration interface. If you
402 // want to have initial error messages for eventual database connection problems
403 // localized too, you have to set your language code here.
405 // $CFG->lang = 'yourlangcode'; // for example 'cs'
407 // When Moodle is about to perform an intensive operation it raises PHP's memory
408 // limit. The following setting should be used on large sites to set the raised
409 // memory limit to something higher.
410 // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G
412 // $CFG->extramemorylimit = '1G';
414 // Moodle 2.4 introduced a new cache API.
415 // The cache API stores a configuration file within the Moodle data directory and
416 // uses that rather than the database in order to function in a stand-alone manner.
417 // Using altcacheconfigpath you can change the location where this config file is
418 // looked for.
419 // It can either be a directory in which to store the file, or the full path to the
420 // file if you want to take full control. Either way it must be writable by the
421 // webserver.
423 // $CFG->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php
425 // The CSS files the Moodle produces can be extremely large and complex, especially
426 // if you are using a custom theme that builds upon several other themes.
427 // In Moodle 2.3 a CSS optimiser was added as an experimental feature for advanced
428 // users. The CSS optimiser organises the CSS in order to reduce the overall number
429 // of rules and styles being sent to the client. It does this by collating the
430 // CSS before it is cached removing excess styles and rules and stripping out any
431 // extraneous content such as comments and empty rules.
432 // The following settings are used to enable and control the optimisation.
434 // Enable the CSS optimiser. This will only optimise the CSS if themedesignermode
435 // is not enabled. This can be set through the UI however it is noted here as well
436 // because the other CSS optimiser settings can not be set through the UI.
438 // $CFG->enablecssoptimiser = true;
440 // If set the CSS optimiser will add stats about the optimisation to the top of
441 // the optimised CSS file. You can then inspect the CSS to see the affect the CSS
442 // optimiser is having.
444 // $CFG->cssoptimiserstats = true;
446 // If set the CSS that is optimised will still retain a minimalistic formatting
447 // so that anyone wanting to can still clearly read it.
449 // $CFG->cssoptimiserpretty = true;
451 // Use the following flag to completely disable the Available update notifications
452 // feature and hide it from the server administration UI.
454 // $CFG->disableupdatenotifications = true;
456 // As of version 2.4 Moodle serves icons as SVG images if the users browser appears
457 // to support SVG.
458 // For those wanting to control the serving of SVG images the following setting can
459 // be defined in your config.php.
460 // If it is not defined then the default (browser detection) will occur.
462 // To ensure they are always used when available:
463 // $CFG->svgicons = true;
465 // To ensure they are never used even when available:
466 // $CFG->svgicons = false;
468 //=========================================================================
469 // 8. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
470 //=========================================================================
472 // Force a debugging mode regardless the settings in the site administration
473 // @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
474 // @ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
475 // $CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
476 // $CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS!
478 // You can specify a comma separated list of user ids that that always see
479 // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
480 // for these users only.
481 // $CFG->debugusers = '2';
483 // Prevent theme caching
484 // $CFG->themerev = -1; // NOT FOR PRODUCTION SERVERS!
486 // Prevent core_string_manager on-disk cache
487 // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!
489 // When working with production data on test servers, no emails or other messages
490 // should ever be send to real users
491 // $CFG->noemailever = true; // NOT FOR PRODUCTION SERVERS!
493 // Divert all outgoing emails to this address to test and debug emailing features
494 // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
496 // special magic evil developer only wanting to edit the xmldb files manually
497 // AND don't use the XMLDBEditor nor the prev/next stuff at all (Mahara and others)
498 // Uncomment these if you're lazy like Penny
499 // $CFG->xmldbdisablecommentchecking = true; // NOT FOR PRODUCTION SERVERS!
500 // $CFG->xmldbdisablenextprevchecking = true; // NOT FOR PRODUCTION SERVERS!
502 // Special magic - evil developer only wanting to edit xmldb files manually
503 // AND allowing the XMLDBEditor to reconstruct the prev/next elements every
504 // time one file is loaded and saved (Moodle).
505 // Uncomment this if you're lazy like Petr
506 // $CFG->xmldbreconstructprevnext = true; // NOT FOR PRODUCTION SERVERS!
508 // Since 2.0 sql queries are not shown during upgrade by default.
509 // Please note that this setting may produce very long upgrade page on large sites.
510 // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!
512 // Add SQL queries to the output of cron, just before their execution
513 // $CFG->showcronsql = true;
515 // Force developer level debug and add debug info to the output of cron
516 // $CFG->showcrondebugging = true;
518 //=========================================================================
519 // 9. FORCED SETTINGS
520 //=========================================================================
521 // It is possible to specify normal admin settings here, the point is that
522 // they can not be changed through the standard admin settings pages any more.
524 // Core settings are specified directly via assignment to $CFG variable.
525 // Example:
526 // $CFG->somecoresetting = 'value';
528 // Plugin settings have to be put into a special array.
529 // Example:
530 // $CFG->forced_plugin_settings = array('pluginname' => array('settingname' => 'value', 'secondsetting' => 'othervalue'),
531 // 'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));
533 //=========================================================================
534 // 9. PHPUNIT SUPPORT
535 //=========================================================================
536 // $CFG->phpunit_prefix = 'phpu_';
537 // $CFG->phpunit_dataroot = '/home/example/phpu_moodledata';
538 // $CFG->phpunit_directorypermissions = 02777; // optional
540 //=========================================================================
541 // ALL DONE! To continue installation, visit your main page with a browser
542 //=========================================================================
544 require_once(dirname(__FILE__) . '/lib/setup.php'); // Do not edit
546 // There is no php closing tag in this file,
547 // it is intentional because it prevents trailing whitespace problems!