Search moodle.org's
Developer Documentation


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

Search This Site: