Search moodle.org's
Developer Documentation


  • Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
  • Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
  • minimum PHP 5.6.5. Note: minimum PHP version has increased since Moodle 3.1. PHP 7.0.x and 7.1.x are supported but have some engine limitations
  • / -> config-dist.php (source)

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

    Search This Site: