Search moodle.org's
Developer Documentation


  • Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
  • Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
  • minimum PHP 5.4.4 (always use latest PHP 5.4.x or 5.5.x on Windows - http://windows.php.net/download/). For PHP 7.0.x support, upgrade to Moodle 3.0.1 or later. PHP 7.1.x is not supported by Moodle 3.0.
  • / -> config-dist.php (source)

    Differences Between: [Versions 29 and 30] [Versions 30 and 31] [Versions 30 and 32] [Versions 30 and 33] [Versions 30 and 34] [Versions 30 and 35] [Versions 30 and 36] [Versions 30 and 37] [Versions 30 and 38]

       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  //   Redis session handler (requires redis server and redis extension):
     253  //      $CFG->session_handler_class = '\core\session\redis';
     254  //      $CFG->session_redis_host = '127.0.0.1';
     255  //      $CFG->session_redis_port = 6379;  // Optional.
     256  //      $CFG->session_redis_database = 0;  // Optional, default is db 0.
     257  //      $CFG->session_redis_prefix = ''; // Optional, default is don't set one.
     258  //      $CFG->session_redis_acquire_lock_timeout = 120;
     259  //      $CFG->session_redis_lock_expire = 7200;
     260  //
     261  //   Memcache session handler (requires memcached server and memcache extension):
     262  //      $CFG->session_handler_class = '\core\session\memcache';
     263  //      $CFG->session_memcache_save_path = '127.0.0.1:11211';
     264  //      $CFG->session_memcache_acquire_lock_timeout = 120;
     265  //      ** NOTE: Memcache extension has less features than memcached and may be
     266  //         less reliable. Use memcached where possible or if you encounter
     267  //         session problems. **
     268  //
     269  // Please be aware that when selecting either Memcached or Memcache for sessions that it is advised to use a dedicated
     270  // memcache server. The memcache and memcached extensions do not provide isolated environments for individual uses.
     271  // Using the same server for other purposes (MUC for example) can lead to sessions being prematurely removed should
     272  // the other uses of the server purge the cache.
     273  //
     274  // Following setting allows you to alter how frequently is timemodified updated in sessions table.
     275  //      $CFG->session_update_timemodified_frequency = 20; // In seconds.
     276  //
     277  // If this setting is set to true, then Moodle will track the IP of the
     278  // current user to make sure it hasn't changed during a session.  This
     279  // will prevent the possibility of sessions being hijacked via XSS, but it
     280  // may break things for users coming using proxies that change all the time,
     281  // like AOL.
     282  //      $CFG->tracksessionip = true;
     283  //
     284  // The following lines are for handling email bounces.
     285  //      $CFG->handlebounces = true;
     286  //      $CFG->minbounces = 10;
     287  //      $CFG->bounceratio = .20;
     288  // The next lines are needed both for bounce handling and any other email to module processing.
     289  // mailprefix must be EXACTLY four characters.
     290  // Uncomment and customise this block for Postfix
     291  //      $CFG->mailprefix = 'mdl+'; // + is the separator for Exim and Postfix.
     292  //      $CFG->mailprefix = 'mdl-'; // - is the separator for qmail
     293  //      $CFG->maildomain = 'youremaildomain.com';
     294  //
     295  // Enable when setting up advanced reverse proxy load balancing configurations,
     296  // it may be also necessary to enable this when using port forwarding.
     297  //      $CFG->reverseproxy = true;
     298  //
     299  // Enable when using external SSL appliance for performance reasons.
     300  // Please note that site may be accessible via http: or https:, but not both!
     301  //      $CFG->sslproxy = true;
     302  //
     303  // This setting will cause the userdate() function not to fix %d in
     304  // date strings, and just let them show with a zero prefix.
     305  //      $CFG->nofixday = true;
     306  //
     307  // This setting will make some graphs (eg user logs) use lines instead of bars
     308  //      $CFG->preferlinegraphs = true;
     309  //
     310  // Enabling this will allow custom scripts to replace existing moodle scripts.
     311  // For example: if $CFG->customscripts/course/view.php exists then
     312  // it will be used instead of $CFG->wwwroot/course/view.php
     313  // At present this will only work for files that include config.php and are called
     314  // as part of the url (index.php is implied).
     315  // Some examples are:
     316  //      http://my.moodle.site/course/view.php
     317  //      http://my.moodle.site/index.php
     318  //      http://my.moodle.site/admin            (index.php implied)
     319  // Custom scripts should not include config.php
     320  // Warning: Replacing standard moodle scripts may pose security risks and/or may not
     321  // be compatible with upgrades. Use this option only if you are aware of the risks
     322  // involved.
     323  // Specify the full directory path to the custom scripts
     324  //      $CFG->customscripts = '/home/example/customscripts';
     325  //
     326  // Performance profiling
     327  //
     328  //   If you set Debug to "Yes" in the Configuration->Variables page some
     329  //   performance profiling data will show up on your footer (in default theme).
     330  //   With these settings you get more granular control over the capture
     331  //   and printout of the data
     332  //
     333  //   Capture performance profiling data
     334  //   define('MDL_PERF'  , true);
     335  //
     336  //   Capture additional data from DB
     337  //   define('MDL_PERFDB'  , true);
     338  //
     339  //   Print to log (for passive profiling of production servers)
     340  //   define('MDL_PERFTOLOG'  , true);
     341  //
     342  //   Print to footer (works with the default theme)
     343  //   define('MDL_PERFTOFOOT', true);
     344  //
     345  //   Enable earlier profiling that causes more code to be covered
     346  //   on every request (db connections, config load, other inits...).
     347  //   Requires extra configuration to be defined in config.php like:
     348  //   profilingincluded, profilingexcluded, profilingautofrec,
     349  //   profilingallowme, profilingallowall, profilinglifetime
     350  //       $CFG->earlyprofilingenabled = true;
     351  //
     352  // Force displayed usernames
     353  //   A little hack to anonymise user names for all students.  If you set these
     354  //   then all non-teachers will always see these for every person.
     355  //       $CFG->forcefirstname = 'Bruce';
     356  //       $CFG->forcelastname  = 'Simpson';
     357  //
     358  // The following setting will turn on username logging into Apache log. For full details regarding setting
     359  // up of this function please refer to the install section of the document.
     360  //     $CFG->apacheloguser = 0; // Turn this feature off. Default value.
     361  //     $CFG->apacheloguser = 1; // Log user id.
     362  //     $CFG->apacheloguser = 2; // Log full name in cleaned format. ie, Darth Vader will be displayed as darth_vader.
     363  //     $CFG->apacheloguser = 3; // Log username.
     364  // To get the values logged in Apache's log, add to your httpd.conf
     365  // the following statements. In the General part put:
     366  //     LogFormat "%h %l %{MOODLEUSER}n %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" moodleformat
     367  // And in the part specific to your Moodle install / virtualhost:
     368  //     CustomLog "/your/path/to/log" moodleformat
     369  // CAUTION: Use of this option will expose usernames in the Apache log,
     370  // If you are going to publish your log, or the output of your web stats analyzer
     371  // this will weaken the security of your website.
     372  //
     373  // Email database connection errors to someone.  If Moodle cannot connect to the
     374  // database, then email this address with a notice.
     375  //
     376  //     $CFG->emailconnectionerrorsto = 'your@emailaddress.com';
     377  //
     378  // Set the priority of themes from highest to lowest. This is useful (for
     379  // example) in sites where the user theme should override all other theme
     380  // settings for accessibility reasons. You can also disable types of themes
     381  // (other than site)  by removing them from the array. The default setting is:
     382  //      $CFG->themeorder = array('course', 'category', 'session', 'user', 'site');
     383  // NOTE: course, category, session, user themes still require the
     384  // respective settings to be enabled
     385  //
     386  // It is possible to add extra themes directory stored outside of $CFG->dirroot.
     387  // This local directory does not have to be accessible from internet.
     388  //
     389  //     $CFG->themedir = '/location/of/extra/themes';
     390  //
     391  // It is possible to specify different cache and temp directories, use local fast filesystem
     392  // for normal web servers. Server clusters MUST use shared filesystem for cachedir!
     393  // Localcachedir is intended for server clusters, it does not have to be shared by cluster nodes.
     394  // The directories must not be accessible via web.
     395  //
     396  //     $CFG->tempdir = '/var/www/moodle/temp';        // Directory MUST BE SHARED by all clsuter nodes.
     397  //     $CFG->cachedir = '/var/www/moodle/cache';      // Directory MUST BE SHARED by all cluster nodes, locking required.
     398  //     $CFG->localcachedir = '/var/local/cache';      // Intended for local node caching.
     399  //
     400  // Some filesystems such as NFS may not support file locking operations.
     401  // Locking resolves race conditions and is strongly recommended for production servers.
     402  //     $CFG->preventfilelocking = false;
     403  //
     404  // Site default language can be set via standard administration interface. If you
     405  // want to have initial error messages for eventual database connection problems
     406  // localized too, you have to set your language code here.
     407  //
     408  //     $CFG->lang = 'yourlangcode'; // for example 'cs'
     409  //
     410  // When Moodle is about to perform an intensive operation it raises PHP's memory
     411  // limit. The following setting should be used on large sites to set the raised
     412  // memory limit to something higher.
     413  // The value for the settings should be a valid PHP memory value. e.g. 512M, 1G
     414  //
     415  //     $CFG->extramemorylimit = '1024M';
     416  //
     417  // Moodle 2.4 introduced a new cache API.
     418  // The cache API stores a configuration file within the Moodle data directory and
     419  // uses that rather than the database in order to function in a stand-alone manner.
     420  // Using altcacheconfigpath you can change the location where this config file is
     421  // looked for.
     422  // It can either be a directory in which to store the file, or the full path to the
     423  // file if you want to take full control. Either way it must be writable by the
     424  // webserver.
     425  //
     426  //     $CFG->altcacheconfigpath = '/var/www/shared/moodle.cache.config.php
     427  //
     428  // The CSS files the Moodle produces can be extremely large and complex, especially
     429  // if you are using a custom theme that builds upon several other themes.
     430  // In Moodle 2.3 a CSS optimiser was added as an experimental feature for advanced
     431  // users. The CSS optimiser organises the CSS in order to reduce the overall number
     432  // of rules and styles being sent to the client. It does this by collating the
     433  // CSS before it is cached removing excess styles and rules and stripping out any
     434  // extraneous content such as comments and empty rules.
     435  // The following settings are used to enable and control the optimisation.
     436  //
     437  // Enable the CSS optimiser. This will only optimise the CSS if themedesignermode
     438  // is not enabled. This can be set through the UI however it is noted here as well
     439  // because the other CSS optimiser settings can not be set through the UI.
     440  //
     441  //      $CFG->enablecssoptimiser = true;
     442  //
     443  // If set the CSS optimiser will add stats about the optimisation to the top of
     444  // the optimised CSS file. You can then inspect the CSS to see the affect the CSS
     445  // optimiser is having.
     446  //
     447  //      $CFG->cssoptimiserstats = true;
     448  //
     449  // If set the CSS that is optimised will still retain a minimalistic formatting
     450  // so that anyone wanting to can still clearly read it.
     451  //
     452  //      $CFG->cssoptimiserpretty = true;
     453  //
     454  // Use the following flag to completely disable the Available update notifications
     455  // feature and hide it from the server administration UI.
     456  //
     457  //      $CFG->disableupdatenotifications = true;
     458  //
     459  // Use the following flag to completely disable the installation of plugins
     460  // (new plugins, available updates and missing dependencies) and related
     461  // features (such as cancelling the plugin installation or upgrade) via the
     462  // server administration web interface.
     463  //
     464  //      $CFG->disableupdateautodeploy = true;
     465  //
     466  // Use the following flag to disable modifications to scheduled tasks
     467  // whilst still showing the state of tasks.
     468  //
     469  //      $CFG->preventscheduledtaskchanges = true;
     470  //
     471  // As of version 2.4 Moodle serves icons as SVG images if the users browser appears
     472  // to support SVG.
     473  // For those wanting to control the serving of SVG images the following setting can
     474  // be defined in your config.php.
     475  // If it is not defined then the default (browser detection) will occur.
     476  //
     477  // To ensure they are always used when available:
     478  //      $CFG->svgicons = true;
     479  //
     480  // To ensure they are never used even when available:
     481  //      $CFG->svgicons = false;
     482  //
     483  // Some administration options allow setting the path to executable files. This can
     484  // potentially cause a security risk. Set this option to true to disable editing
     485  // those config settings via the web. They will need to be set explicitly in the
     486  // config.php file
     487  //      $CFG->preventexecpath = true;
     488  //
     489  // Use the following flag to set userid for noreply user. If not set then moodle will
     490  // create dummy user and use -ve value as user id.
     491  //      $CFG->noreplyuserid = -10;
     492  //
     493  // As of version 2.6 Moodle supports admin to set support user. If not set, all mails
     494  // will be sent to supportemail.
     495  //      $CFG->supportuserid = -20;
     496  //
     497  // Moodle 2.7 introduces a locking api for critical tasks (e.g. cron).
     498  // The default locking system to use is DB locking for Postgres, and file locking for
     499  // MySQL, Oracle and SQLServer. If $CFG->preventfilelocking is set, then the default
     500  // will always be DB locking. It can be manually set to one of the lock
     501  // factory classes listed below, or one of your own custom classes implementing the
     502  // \core\lock\lock_factory interface.
     503  //
     504  //      $CFG->lock_factory = "auto";
     505  //
     506  // The list of available lock factories is:
     507  //
     508  // "\\core\\lock\\file_lock_factory" - File locking
     509  //      Uses lock files stored by default in the dataroot. Whether this
     510  //      works on clusters depends on the file system used for the dataroot.
     511  //
     512  // "\\core\\lock\\db_record_lock_factory" - DB locking based on table rows.
     513  //
     514  // "\\core\\lock\\postgres_lock_factory" - DB locking based on postgres advisory locks.
     515  //
     516  // Settings used by the lock factories
     517  //
     518  // Location for lock files used by the File locking factory. This must exist
     519  // on a shared file system that supports locking.
     520  //      $CFG->lock_file_root = $CFG->dataroot . '/lock';
     521  //
     522  // Moodle 2.9 allows administrators to customise the list of supported file types.
     523  // To add a new filetype or override the definition of an existing one, set the
     524  // customfiletypes variable like this:
     525  //
     526  // $CFG->customfiletypes = array(
     527  //     (object)array(
     528  //         'extension' => 'frog',
     529  //         'icon' => 'archive',
     530  //         'type' => 'application/frog',
     531  //         'customdescription' => 'Amphibian-related file archive'
     532  //     )
     533  // );
     534  //
     535  // The extension, icon, and type fields are required. The icon field can refer to
     536  // any icon inside the pix/f folder. You can also set the customdescription field
     537  // (shown above) and (for advanced use) the groups, string, and defaulticon fields.
     538  //
     539  // Upgrade key
     540  //
     541  // If the upgrade key is defined here, then the value must be provided every time
     542  // the site is being upgraded though the web interface, regardless of whether the
     543  // administrator is logged in or not. This prevents anonymous access to the upgrade
     544  // screens where the real authentication and authorization mechanisms can not be
     545  // relied on.
     546  //
     547  // It is strongly recommended to use a value different from your real account
     548  // password.
     549  //
     550  //      $CFG->upgradekey = 'put_some_password-like_value_here';
     551  //
     552  //=========================================================================
     553  // 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
     554  //=========================================================================
     555  //
     556  // Force a debugging mode regardless the settings in the site administration
     557  // @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
     558  // @ini_set('display_errors', '1');    // NOT FOR PRODUCTION SERVERS!
     559  // $CFG->debug = (E_ALL | E_STRICT);   // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
     560  // $CFG->debugdisplay = 1;             // NOT FOR PRODUCTION SERVERS!
     561  //
     562  // You can specify a comma separated list of user ids that that always see
     563  // debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
     564  // for these users only.
     565  // $CFG->debugusers = '2';
     566  //
     567  // Prevent theme caching
     568  // $CFG->themedesignermode = true; // NOT FOR PRODUCTION SERVERS!
     569  //
     570  // Prevent JS caching
     571  // $CFG->cachejs = false; // NOT FOR PRODUCTION SERVERS!
     572  //
     573  // Restrict which YUI logging statements are shown in the browser console.
     574  // For details see the upstream documentation:
     575  //   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logInclude
     576  //   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logExclude
     577  // $CFG->yuiloginclude = array(
     578  //     'moodle-core-dock-loader' => true,
     579  //     'moodle-course-categoryexpander' => true,
     580  // );
     581  // $CFG->yuilogexclude = array(
     582  //     'moodle-core-dock' => true,
     583  //     'moodle-core-notification' => true,
     584  // );
     585  //
     586  // Set the minimum log level for YUI logging statements.
     587  // For details see the upstream documentation:
     588  //   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logLevel
     589  // $CFG->yuiloglevel = 'debug';
     590  //
     591  // Prevent core_string_manager application caching
     592  // $CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!
     593  //
     594  // When working with production data on test servers, no emails or other messages
     595  // should ever be send to real users
     596  // $CFG->noemailever = true;    // NOT FOR PRODUCTION SERVERS!
     597  //
     598  // Divert all outgoing emails to this address to test and debug emailing features
     599  // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
     600  //
     601  // Uncomment if you want to allow empty comments when modifying install.xml files.
     602  // $CFG->xmldbdisablecommentchecking = true;    // NOT FOR PRODUCTION SERVERS!
     603  //
     604  // Since 2.0 sql queries are not shown during upgrade by default.
     605  // Please note that this setting may produce very long upgrade page on large sites.
     606  // $CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!
     607  //
     608  // Add SQL queries to the output of cron, just before their execution
     609  // $CFG->showcronsql = true;
     610  //
     611  // Force developer level debug and add debug info to the output of cron
     612  // $CFG->showcrondebugging = true;
     613  //
     614  //=========================================================================
     615  // 8. FORCED SETTINGS
     616  //=========================================================================
     617  // It is possible to specify normal admin settings here, the point is that
     618  // they can not be changed through the standard admin settings pages any more.
     619  //
     620  // Core settings are specified directly via assignment to $CFG variable.
     621  // Example:
     622  //   $CFG->somecoresetting = 'value';
     623  //
     624  // Plugin settings have to be put into a special array.
     625  // Example:
     626  //   $CFG->forced_plugin_settings = array('pluginname'  => array('settingname' => 'value', 'secondsetting' => 'othervalue'),
     627  //                                        'otherplugin' => array('mysetting' => 'myvalue', 'thesetting' => 'thevalue'));
     628  // Module default settings with advanced/locked checkboxes can be set too. To do this, add
     629  // an extra config with '_adv' or '_locked' as a suffix and set the value to true or false.
     630  // Example:
     631  //   $CFG->forced_plugin_settings = array('pluginname'  => array('settingname' => 'value', 'settingname_locked' => true, 'settingname_adv' => true));
     632  //
     633  //=========================================================================
     634  // 9. PHPUNIT SUPPORT
     635  //=========================================================================
     636  // $CFG->phpunit_prefix = 'phpu_';
     637  // $CFG->phpunit_dataroot = '/home/example/phpu_moodledata';
     638  // $CFG->phpunit_directorypermissions = 02777; // optional
     639  //
     640  //
     641  //=========================================================================
     642  // 10. SECRET PASSWORD SALT
     643  //=========================================================================
     644  // A site-wide password salt is no longer used in new installations.
     645  // If upgrading from 2.6 or older, keep all existing salts in config.php file.
     646  //
     647  // $CFG->passwordsaltmain = 'a_very_long_random_string_of_characters#@6&*1';
     648  //
     649  // You may also have some alternative salts to allow migration from previously
     650  // used salts.
     651  //
     652  // $CFG->passwordsaltalt1 = '';
     653  // $CFG->passwordsaltalt2 = '';
     654  // $CFG->passwordsaltalt3 = '';
     655  // ....
     656  // $CFG->passwordsaltalt19 = '';
     657  // $CFG->passwordsaltalt20 = '';
     658  //
     659  //
     660  //=========================================================================
     661  // 11. BEHAT SUPPORT
     662  //=========================================================================
     663  // Behat test site needs a unique www root, data directory and database prefix:
     664  //
     665  // $CFG->behat_wwwroot = 'http://127.0.0.1/moodle';
     666  // $CFG->behat_prefix = 'bht_';
     667  // $CFG->behat_dataroot = '/home/example/bht_moodledata';
     668  //
     669  // You can override default Moodle configuration for Behat and add your own
     670  // params; here you can add more profiles, use different Mink drivers than Selenium...
     671  // These params would be merged with the default Moodle behat.yml, giving priority
     672  // to the ones specified here. The array format is YAML, following the Behat
     673  // params hierarchy. More info: http://docs.behat.org/guides/7.config.html
     674  // Example:
     675  //   $CFG->behat_config = array(
     676  //       'default' => array(
     677  //           'formatter' => array(
     678  //               'name' => 'pretty',
     679  //               'parameters' => array(
     680  //                   'decorated' => true,
     681  //                   'verbose' => false
     682  //               )
     683  //           )
     684  //       ),
     685  //       'Mac-Firefox' => array(
     686  //           'extensions' => array(
     687  //               'Behat\MinkExtension\Extension' => array(
     688  //                   'selenium2' => array(
     689  //                       'browser' => 'firefox',
     690  //                       'capabilities' => array(
     691  //                           'platform' => 'OS X 10.6',
     692  //                           'version' => 20
     693  //                       )
     694  //                   )
     695  //               )
     696  //           )
     697  //       ),
     698  //       'Mac-Safari' => array(
     699  //           'extensions' => array(
     700  //               'Behat\MinkExtension\Extension' => array(
     701  //                   'selenium2' => array(
     702  //                       'browser' => 'safari',
     703  //                       'capabilities' => array(
     704  //                           'platform' => 'OS X 10.8',
     705  //                           'version' => 6
     706  //                       )
     707  //                   )
     708  //               )
     709  //           )
     710  //       )
     711  //   );
     712  // You can also use the following config to override default Moodle configuration for Behat.
     713  // This config is limited to default suite and will be supported in later versions.
     714  // It will have precedence over $CFG->behat_config.
     715  // $CFG->behat_profiles = array(
     716  //     'phantomjs' => array(
     717  //         'browser' => 'phantomjs',
     718  //         'tags' => '~@_file_upload&&~@_alert&&~@_bug_phantomjs',
     719  //         'wd_host' => 'http://127.0.0.1:4443/wd/hub',
     720  //         'capabilities' => array(
     721  //             'platform' => 'Linux',
     722  //             'version' => 2.1
     723  //         )
     724  //     ),
     725  // );
     726  //
     727  // You can force the browser session (not user's sessions) to restart after N seconds. This could
     728  // be useful if you are using a cloud-based service with time restrictions in the browser side.
     729  // Setting this value the browser session that Behat is using will be restarted. Set the time in
     730  // seconds. Is not recommended to use this setting if you don't explicitly need it.
     731  // Example:
     732  //   $CFG->behat_restart_browser_after = 7200;     // Restarts the browser session after 2 hours
     733  //
     734  // All this page's extra Moodle settings are compared against a white list of allowed settings
     735  // (the basic and behat_* ones) to avoid problems with production environments. This setting can be
     736  // used to expand the default white list with an array of extra settings.
     737  // Example:
     738  //   $CFG->behat_extraallowedsettings = array('somecoresetting', ...);
     739  //
     740  // You should explicitly allow the usage of the deprecated behat steps, otherwise an exception will
     741  // be thrown when using them. The setting is disabled by default.
     742  // Example:
     743  //   $CFG->behat_usedeprecated = true;
     744  //
     745  // Including feature files from directories outside the dirroot is possible if required. The setting
     746  // requires that the running user has executable permissions on all parent directories in the paths.
     747  // Example:
     748  //   $CFG->behat_additionalfeatures = array('/home/developer/code/wipfeatures');
     749  //
     750  // You can make behat save several dumps when a scenario fails. The dumps currently saved are:
     751  // * a dump of the DOM in it's state at the time of failure; and
     752  // * a screenshot (JavaScript is required for the screenshot functionality, so not all browsers support this option)
     753  // Example:
     754  //   $CFG->behat_faildump_path = '/my/path/to/save/failure/dumps';
     755  //
     756  // You can specify db, selenium wd_host etc. for behat parallel run by setting following variable.
     757  // Example:
     758  //   $CFG->behat_parallel_run = array (
     759  //       array (
     760  //           'dbtype' => 'mysqli',
     761  //           'dblibrary' => 'native',
     762  //           'dbhost' => 'localhost',
     763  //           'dbname' => 'moodletest',
     764  //           'dbuser' => 'moodle',
     765  //           'dbpass' => 'moodle',
     766  //           'behat_prefix' => 'mdl_',
     767  //           'wd_host' => 'http://127.0.0.1:4444/wd/hub',
     768  //           'behat_wwwroot' => 'http://127.0.0.1/moodle',
     769  //           'behat_dataroot' => '/home/example/bht_moodledata'
     770  //       ),
     771  //   );
     772  //
     773  // To change name of behat parallel run site, define BEHAT_PARALLEL_SITE_NAME and parallel run sites will be suffixed
     774  // with this value
     775  // Example:
     776  //   define('BEHAT_PARALLEL_SITE_NAME', 'behatparallelsite');
     777  //
     778  // Command line output for parallel behat install is limited to 80 chars, if you are installing more then 4 sites and
     779  // want to expand output to more then 80 chars, then define BEHAT_MAX_CMD_LINE_OUTPUT
     780  // Example:
     781  //   define('BEHAT_MAX_CMD_LINE_OUTPUT', 120);
     782  //
     783  // Behat feature files will be distributed randomly between the processes by default. If you have timing file or want
     784  // to create timing file then define BEHAT_FEATURE_TIMING_FILE with path to timing file. It will be updated for each
     785  // run with latest time taken to execute feature.
     786  // Example:
     787  //   define('BEHAT_FEATURE_TIMING_FILE', '/PATH_TO_TIMING_FILE/timing.json');
     788  //
     789  // If you don't have timing file and want some stable distribution of features, then you can use step counts to
     790  // distribute the features. You can generate step file by executing php admin/tool/behat/cli/util.php --updatesteps
     791  // this will update step file which is defined by BEHAT_FEATURE_STEP_FILE.
     792  // Example:
     793  //   define('BEHAT_FEATURE_STEP_FILE', '/PATH_TO_FEATURE_STEP_COUNT_FILE/stepcount.json');
     794  //
     795  // Feature distribution for each process is displayed as histogram. you can disable it by setting
     796  // BEHAT_DISABLE_HISTOGRAM
     797  // Example:
     798  //   define('BEHAT_DISABLE_HISTOGRAM', true);
     799  //
     800  //=========================================================================
     801  // 12. DEVELOPER DATA GENERATOR
     802  //=========================================================================
     803  //
     804  // The developer data generator tool is intended to be used only in development or testing sites and
     805  // it's usage in production environments is not recommended; if it is used to create JMeter test plans
     806  // is even less recommended as JMeter needs to log in as site course users. JMeter needs to know the
     807  // users passwords but would be dangerous to have a default password as everybody would know it, which would
     808  // be specially dangerouse if somebody uses this tool in a production site, so in order to prevent unintended
     809  // uses of the tool and undesired accesses as well, is compulsory to set a password for the users
     810  // generated by this tool, but only in case you want to generate a JMeter test. The value should be a string.
     811  // Example:
     812  //   $CFG->tool_generator_users_password = 'examplepassword';
     813  //
     814  //=========================================================================
     815  // 13. SYSTEM PATHS (You need to set following, depending on your system)
     816  //=========================================================================
     817  // Ghostscript path.
     818  // On most Linux installs, this can be left as '/usr/bin/gs'.
     819  // On Windows it will be something like 'c:\gs\bin\gswin32c.exe' (make sure
     820  // there are no spaces in the path - if necessary copy the files 'gswin32c.exe'
     821  // and 'gsdll32.dll' to a new folder without a space in the path)
     822  //      $CFG->pathtogs = '/usr/bin/gs';
     823  //
     824  // Clam AV path.
     825  // Probably something like /usr/bin/clamscan or /usr/bin/clamdscan. You need
     826  // this in order for clam AV to run.
     827  //      $CFG->pathtoclam = '';
     828  //
     829  // Path to du.
     830  // Probably something like /usr/bin/du. If you enter this, pages that display
     831  // directory contents will run much faster for directories with a lot of files.
     832  //      $CFG->pathtodu = '';
     833  //
     834  // Path to aspell.
     835  // To use spell-checking within the editor, you MUST have aspell 0.50 or later
     836  // installed on your server, and you must specify the correct path to access the
     837  // aspell binary. On Unix/Linux systems, this path is usually /usr/bin/aspell,
     838  // but it might be something else.
     839  //      $CFG->aspellpath = '';
     840  //
     841  // Path to dot.
     842  // Probably something like /usr/bin/dot. To be able to generate graphics from
     843  // DOT files, you must have installed the dot executable and point to it here.
     844  // Note that, for now, this only used by the profiling features
     845  // (Development->Profiling) built into Moodle.
     846  //      $CFG->pathtodot = '';
     847  
     848  //=========================================================================
     849  // ALL DONE!  To continue installation, visit your main page with a browser
     850  //=========================================================================
     851  
     852  require_once(dirname(__FILE__) . '/lib/setup.php'); // Do not edit
     853  
     854  // There is no php closing tag in this file,
     855  // it is intentional because it prevents trailing whitespace problems!
    

    Search This Site: