Search moodle.org's
Developer Documentation


Long Term Support Release

  • Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
  • Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
  • minimum PHP 5.4.4 (always use latest PHP 5.4.x , 5.5.x or 5.6.x on Windows - http://windows.php.net/download/). PHP 7.0.x is supported but has some engine limitations. PHP 7.1.x is not supported.
  • / -> config-dist.php (source)

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

    Search This Site: