MoodleDocs - User contributions [en]

Installation FAQ

2012-01-26T10:51:40Z

Howardsmiller: /* System information needed for Installation problems forum */

{{Installing Moodle}}
== System information needed for Installation problems forum ==
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:
* '''Moodle version''' (e.g. 2.1)
* Server Operating System name (version also if possible):
* PHP version (e.g. PHP 5.3.2)
* Database server type and version (e.g. MySQL 5.5.18)
* Browser and version (e.g. Internet Explorer 8):
* Moodle install type? (New/Upgrade):
* Moodle config.php attached (please remove passwords):
* Phpinfo attached?:

Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!

[[#top|Top]]

==PHP - is it installed and what version do I have?==

Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:

<code php>
<?PHP phpinfo() ?>
</code>

If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.

[[#top|Top]]

==What & where are Moodle's configuration settings stored?==
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs.
[[#top|Top]]

==Downloading previous releases of Moodle==
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below).

{| style="width:75%; height:75px" border="0"
|-
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions]
|-
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions]
|-
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] ||
|}

You can download previous releases by using wget, lynx or curl with this URL:
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>.
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki>
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac pacakges], use either of these URLs (depending on whether you need the Intel or PPC package):
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki>
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki>
* '''Using CVS''': You can also use CVS to download older releases and incremental releases of the Moodle generic packages, e.g. Moodle 1.5.4 - see the [[CVS_for_Administrators | CVS documentation]].

[[#top|Top]]

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[PHP error logs]].

==Email copies are not being sent from my forums==

You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on. Please refer to the [[Cron|cron instructions]].

Tips:
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.
* Check your firewall or ask your network administrator. Many mail servers are heavily locked down and you may need permission to send mail through them.

[[#top|Top]]

==I can't log in - I just stay stuck on the login screen==

This may also apply if you are seeing “Your session has timed out. Please login again” and cannot log in.

The following are possible causes and actions you can take (in no particular order):

* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
* Sessions may not be configured properly on the server. You can test this by calling the script <nowiki>http://yourserver/moodle/lib/session-test.php</nowiki>.
* If your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)
* Try deleting cookies on your computer and/or try another browser or another client computer
* In Site Administration > Server > Session handling, try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser.
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This feature was optional since Moodle 1.6 but has been applied by default since 1.9.7. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
* You are using the correct username and password, yes?

If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it see [[Administration FAQ]]

[[#top|Top]]

==I log in but the login link doesn't change. I am logged in and can navigate freely.==

Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.

[[#top|Top]]
==Uploaded files give "File not found"==

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.

Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory (see [[Installing Moodle]] for more details):

'''AcceptPathInfo''' on

Note, this will ONLY work for Apache versions 2.x.

For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx.

IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.

Once you've got URL rewriting working the recommended rewriting rule is:

'''RewriteRule''' ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]

In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.

If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.

To use this alternative method, you should change the ''slasharguments'' variable. For moodle versions < 1.7, this is located in the Operating System section of ''Administration > Configuration > [[admin/config|Variables]]''. In later versions, this option is located in ''Site Administration > Server > HTTP''. You should now be able to access your uploaded files.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=145422 Troubleshooting Guide - 404 Errors] forum discussion.

[[#top|Top]]

==Why are all my pages blank?==

Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)

<code php>
$CFG->dirroot = "/var/www/moodle";
</code>

Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].

To determine if database support is your problem, insert this as the second line in your ''config.php'' file

<code php>
phpinfo();
</code>

then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.

[[#top|Top]]

== Why is a particular page blank or incomplete? ==

*'''Check your web server log files!!'''
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.

*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".

*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.

*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion

==Installation hangs when setting-up database tables==
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.

See [[Unexpected installation halts]] for more about solutions that involve:
*Checking for MySQL limits
*Checking the .htaccess files
*Code customizations issues
*Checking memory limit
*Upgrade incrementally
*Fix fopen function

[[#top|Top]]

==Why can't I upload a new image into my profile?==

If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
*The permissions associated with the role you are using are preventing you from changing your profile picture.
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > [[PHP info]]'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.

If Moodle thinks GD is not installed, then you will need to '''install the GD library'''.
*On Unix you may need to re-compile PHP with arguments something like this:

./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars
--enable-versioning --with-zlib

* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
extension=php_gd2.dll

:Windows users should see the [[Installing AMP|installation instructions]] for further help.

3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.

'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.

== Why doesn't my Moodle site display the time and date correctly? ==

Each language requires a specific language code (called a '''locale''' code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.

You can find the correct locale codes for Windows on these two pages: [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_language_strings.asp Language codes] and [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_country_strings.asp Country/region] codes (e.g. "esp_esp" for spanish)

These new locale codes can be entered on the Administration >> Configuration >> [[admin/config|Variables]] page, where they override the ones in the currently chosen language pack.
[[#top|Top]]
== How do I uninstall Moodle?==

'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
<pre>sql>DROP DATABASE moodle;</pre>
:In the above example replace 'moodle' with the name of the moodle database you created when installing.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:
*Open cmd.exe and navigate to this directory within your installation directory:
<pre>server/mysql/bin</pre>
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre>
*Enter your database password at the prompt (the default is "" [blank]).
*Enter "y" to confirm the database drop.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

==Migrating Moodle to a new site or server==
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.

[[#top|Top]]
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].

[[#top|Top]]
==Maximum upload file size - how to change it?==
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].

If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server.

For more help see:
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]
*[[Installing_Moodle#Recheck_PHP_settings]]
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]
*[[Site_policies#Maximum_uploaded_file_size]]
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650

[[#top|Top]]

==Moodle claims PHP float handling is not compatible==

The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".

[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.

You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.

Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
ini_set('precision', 14);
to your config.php file, and report your success in MDL-18253.

==When upgrading Moodle claims my database is not UTF8 when I'm sure it is==

The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade.

The database may not have it's character encoding set quite correctly. You can safely try this command on the database (mySQL):

ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it.

Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use [[phpMyAdmin]] to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199).

If your Moodle site is version 1.5 or older then it's telling the truth.

[[#top|Top]]

== How do I run multiple instances of Moodle without duplicating base code? ==

See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].

== What is FreeTDS and how can I use it in my installation? ==
[[FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.

== How do I install a plugin? ==

Please see [[Installing contributed modules or plugins]].

== See also ==

* [[Installing Moodle]]
* [[Upgrading FAQ]]
* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]

[[Category:FAQ]]

[[es:FAQ Instalación]]
[[fr:FAQ d'installation]]
[[nl:Installatie FAQ]]
[[ja:インストールFAQ]]
[[ru:FAQ по установке]]
[[pl:Instalacja FAQ]]
[[de:Installation FAQ]]

Installing Moodle

2012-01-26T10:46:18Z

Howardsmiller: /* Download and copy files into place */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have three basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack...
* '''OR''' Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].
* '''OR''' Pull the code from one of the CVS repositories. See [[CVS for Administrators]].

Any of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

== Platform specific instructions ==

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Installing Moodle

2012-01-26T10:45:35Z

Howardsmiller: /* Download and copy files into place */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have three basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack...
* '''OR''' Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].
* '''OR''' Pull the code from one of the CVS repository. See [[CVS for Administrators]].

Any of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

== Platform specific instructions ==

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Groupings

2012-01-18T14:54:56Z

Howardsmiller:

{{Grouping users}}
A grouping is a set of groups. Groupings enable students to be arranged into different sets of groups for each activity.

NOTE: if you want to show resources just to one group and not another (i.e. enable Groupings for resources), see [[Available for group members only]].

==Adding groups to a grouping==
To add groups to a grouping:
*In your course, click ''Settings > Course administration > Users > Groups''.
*Click the groupings tab:

[[File:Groupingstabs.png]]
*If necessary, create a new grouping by clicking the create grouping button on the groupings page.
*Click the "Show groups in grouping" people icon in the edit column:

[[File:Showgroupsingroupings2.png]]

*On the add/remove groups page, select the group(s) you want to add to the grouping from the "Potential members" list.
*Click the arrow button that points towards the "Existing members" list.

[[File:Addremovegroupings.png]]
*Click the "Back to groupings" button. The group(s) you added to the grouping will now be listed in the table on the groupings page.

Existing groupings can be edited and/or deleted using the appropriate icons in the edit column of the table on the groupings page.

==Setting the default grouping==

Once some groupings have been created, a default grouping for course activities and resources may be set.

#Follow the settings link in the course administration block.
#In the groups section in the course settings, select the default grouping.

The default grouping is used on the Participants page.

==Selecting grouping in activity==
To use a particular grouping in an activity:
*In the "edit settings" link of the Settings block for the activity, click the "Show advanced" button in the common module settings section.
*Ensure that the group mode is set to separate or visible groups.
*Select the grouping from the grouping dropdown menu.

[[File:Setyourgrouping.png]]

*Click the "Save changes" button at the bottom of the page.

Students will only see the activities they have been assigned to. Teachers will see the name of the grouping in brackets after the activity name on the course page. A count of activities assigned to each grouping is kept on the groupings page.

Please note that the grouping option appears by default only in activities that support group modes, if you enable ''Available for group members only'' you will be able to assign resources to specific groups also.

==Examples of groupings==
*In a class, you've divided your students into 4 groups, each with their own author to research. Groups A and B, while they have different authors, are both assigned to write in a forum; groups C and D, though writing on different authors, are supposed to make a wiki. You might create a Forum Group''ing'', containing groups A and B, and a Wiki Group''ing'', containing groups C and D. Then, you can make the Wiki activity available to only the Wiki grouping, but you still have your two Wiki sub-groups, as well - C and D - for an added layer of distinction between the work going on about two different authors.
*Olympic metaphor: at the Olympics, there are different sports (gymnastics, swimming, track) and many countries. There are two ways to think of an Olympian athlete: by the sport they compete in, and by their nationality. To be part of the United States Olympic Team, you must first be a swimmer, a gymnast, or a runner. You cannot be in the US Team without first being an athlete in a specific sport. The sport is your group. Your country is your grouping. You must belong to a group before joining a grouping.

==See also==

*[[Available for group members only]]
*[[Groupings FAQ]]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=131905 Moodle Groups vs. Groupings] forum discussion including youtube video showing how to set up groupings

[[fr:Groupements]]
[[ja:グルーピング]]
[[de:Gruppierungen]]
[[ca:Agrupaments]]

Talk:Available for group members only

2012-01-18T14:08:47Z

Howardsmiller: Created page with "It might be more use to explain what it does rather than just say it's experimental --~~~~"

It might be more use to explain what it does rather than just say it's experimental --[[User:Howard Miller|Howard Miller]] 22:08, 18 January 2012 (WST)

Installing Moodle

2012-01-09T10:39:53Z

Howardsmiller: /* Download and copy files into place */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have three basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack... OR
* '''OR''' Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].
* '''OR''' Pull the code from one of the CVS repository. See [[CVS for Administrators]].

Any of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

== Platform specific instructions ==

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Installing Moodle

2012-01-09T10:21:58Z

Howardsmiller: /* Download and copy files into place */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have three basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack... OR
* '''OR''' Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].
* '''OR''' Pull the code from one of the CVS repository. See [[CVS for Administrators]].

Either of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

== Platform specific instructions ==

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Mac Installation

2012-01-02T19:21:01Z

Howardsmiller:

{{Template:Installing Moodle}}

The following pages give installation information for the Mac OSX platform. This information is provided by the Moodle community and may not have been fully checked and may be out of date (sometimes very). It is provided in the hope that it is useful.

* [[Step by Step Installation on a Mac OS X Server]]
* [[Complete Install Packages for Mac OS X]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]

Mac Installation

2012-01-02T19:19:23Z

Howardsmiller: Created page with "{{Template:Installing Moodle}} The following pages give installation information for the Mac OSX platform. This information is provided by the Moodle community and may not have ..."

{{Template:Installing Moodle}}

The following pages give installation information for the Mac OSX platform. This information is provided by the Moodle community and may not have been fully checked and may be out of date (sometimes very). It is provided in the hope that it is useful.

* [[Step by Step Installation on a Mac OS X Server]]
* [[Complete Install Packages for Mac OS X Clients 10.4/10.5/10.6]]
* [[Step by Step Installation on a Mac OS X 10.4 Client using the internal web server]]

Installing Moodle

2012-01-02T19:17:39Z

Howardsmiller: /* Platform specific instructions */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have two basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack... OR
* Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].

Either of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

== Platform specific instructions ==

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Unix or Linux Installation

2012-01-02T19:08:02Z

Howardsmiller:

{{Template:Installing Moodle}}

The following pages give installation information for specific Unix or Linux platforms. This information is provided by the Moodle community and may not have been fully checked and may be out of date (sometimes very). It is provided in the hope that it is useful.

* [[Installation on Ubuntu using Git]]
* [[Installation on Ubuntu 8.04]] (older Ubuntu discussion with some details on Postgres)
* [[RedHat Linux installation]]
* [[Installation on Solaris 10 with Oracle 10]]

Step-by-step Install Guide for Solaris 10 with Oracle 10

2012-01-02T19:07:25Z

Howardsmiller: moved Step-by-step Install Guide for Solaris 10 with Oracle 10 to Installation on Solaris 10 with Oracle 10

#REDIRECT [[Installation on Solaris 10 with Oracle 10]]

Installation on Solaris 10 with Oracle 10

2012-01-02T19:07:25Z

Howardsmiller: moved Step-by-step Install Guide for Solaris 10 with Oracle 10 to Installation on Solaris 10 with Oracle 10

<center>'''Installation Documentation'''</center>

<center>''for''</center>

<center>''Moodle at VDAB''</center>

'''Table of Contents'''1 Purpose of this document1

2 Setting up the Oracle Database2

3 Configuring Apache2

3.1 Install Apache2

3.2 Install OCI 8 and Oracle Instant Client3

3.3 Install PHP4

3.4 Change PHP settings6

3.5 Add GNU Coreutils7

4 Install Moodle7

4.1 Prepare the Moodle installation files7

4.2 Choose installation language8

4.3 Check PHP settings8

4.4 Set installation and data directories10

4.5 Set Database connection11

4.6 Server checks for installed components12

4.7 Install language packs19

4.8 Confirmation for written configuration file.21

4.9 Licence agreement21

4.10 Release information21

4.11 Automatic database setup22

4.12 Setting up the administrator account23

4.13 Set up Frontpage24

4.14 Start with empty Moodle25

4.15 Add template Purpose of this document
This document provides an in-depth installation manual for Moodle on Solaris 10 with Oracle 10.2.0.2.

We provide an overview of the different steps involved:

* Preparing Oracle 10g for a large Moodle installation
* Configuring Apache 2.2 for a secure and high-performance webserver
* Preparing all necessary PHP packages for Apache and Oracle
* Preparing PHP settings for Moodle
* An overview of the steps in the Moodle installation wizard.

= Setting up the Oracle Database =
We set up '''2 parallel Moodle installations '''on one and a '''database on a separate server'''. Both installations share the same Oracle database, but use a different tablespace.

The Oracle 10.2.0.2 database runs on a Solaris 10 and is set up using Oracle's '''DBCA '''tool.

* This is testzone1 on the test server testitis00
* Database name = testitis02.vdab.be
* We used the ''General purpose'' template for the database set-up;
* And set UTF8 character encoding to NLS_LANG=AMERICAN_AMERICA.AL32UTF8

For each Moodle installation we create a '''separate Tablespace''':

* First Moodle installation on testzone2:
** MOODLE_DATA with initial size of 300MB
** User: MOODLEUSER, password: moodle
** The user only has rights within the specified tablespace
* Second Moodle installation on testzone3:
** MOODLE_DATA2 with initial size of 300MB
** User: MOODLEUSER2, password: moodle
** The user only has rights within the specified tablespace

= Configuring Apache =
== Install Apache ==
First '''download the latest Apache '''e.g. httpd-2.2.8.tar.gz from [http://httpd.apache.org/download.cgi http://httpd.apache.org/download.cgi] to the folder /usr/local/apache2

Log in as root, '''uncompress the Apache files '''and go to the installation folder.

<nowiki># gzip -d httpd-2.2.8.tar.gz</nowiki>

<nowiki># tar -xvf httpd-2.2.8.tar</nowiki>

<nowiki># cd httpd-2.2.8</nowiki>

Adapt the '''Environment Variables '''to make sure the correct gcc and make are used.

<nowiki># export PATH=$PATH:/usr/sfw/bin:/usr/ccs/bin:.</nowiki>

'''Configure and make Apache''':

<nowiki># make clean --> only if necessary</nowiki>

<nowiki># ./configure \</nowiki>

--prefix=/usr/local/apache2 \

--with-included-apr

<nowiki># make</nowiki>

<nowiki># make install</nowiki>

In order to increase performance '''edit''' the following in the httpd.conf file:

<nowiki># vi /usr/local/moodle_1.9+/moodle/httpd.conf -- > opens text editor</nowiki>

'''DirectoryIndex '''index.php

'''Listen''' 8002 -- > for VDAB

'''DocumentRoot''' “/usr/local/moodle_1.9+/moodle”

'''AcceptPathInfo '''on

If you're running Moodle on Oracle with Apache on Linux, you might have issues with PHP being able to see the system environment variables. To resolve this, you can edit /etc/sysconfig/apache2 and add the following lines to the bottom: 
 
LD_LIBRARY_PATH=/opt/oracle/instantclient_11_2# Set LANG Variables for UTF-8 
NLS_LANG=AMERICAN_AMERICA.AL32UTF8 
LANG=en_US.UTF-8 
LC_ALL=en_US.UTF-8 
LC_COLLATE=en_US.UTF-8 
LC_CTYPE=en_US.UTF-8 
LC_MESSAGES=en_US.UTF-8 
LC_MONETARY=en_US.UTF-8 
LC_NUMERIC=en_US.UTF-8 
LC_TIME=en_US.UTF-8 
export LANG LC_ALL LC_COLLATE LC_CTYPE LC_MESSAGES LC_MONETARY LC_NUMERIC LC_TIM NLS_LANG LD_LIBRARY_PATH 
 
Also need to add those two lines to ~/.bashrc so that the PHP command-line client can see it too. 
 

== Install OCI 8 and Oracle Instant Client ==
'''Download the 32bit Solaris Basic en SDK''': instantclient-basic-solaris6432-10.2.0.3-20070101.zip and

instantclient-sdk-solaris6432-10.2.0.3-20070101.zip from

[http://www.oracle.com/technology/tech/oci/instantclient/index.html http://www.oracle.com/technology/tech/oci/instantclient/index.html] to a folder e.g. /oracle/product.

Log in as the user oracle and '''uncompress the installation files''':

$ cd /oracle/product

$ unzip instantclient-basic-solaris6432-10.2.0.3-20070101.zip --> creates the directory instantclient_10_2

$ unzip instantclient-sdk-solaris6432-10.2.0.3-20070101.zip --> is put into the directory instantclient_10_2

'''Adapt the tnsnames '''to set an alias or Oracle net service name. Each net service name entry contains connect descriptors that define listener and service information.

$ cd $TNS_ADMIN --> for VDAB this is /var/opt/oracle)

$ vi tns_admin _--> Below an example adaptation:_

moodle =

(DESCRIPTION =

(ADDRESS =

(COMMUNITY = TCPDEV.world)

(PROTOCOL = TCP)

(HOST = testzone1)

(PORT = 1521)

)

(CONNECT_DATA =

(SID = testitis02)

)

)

If necessary, create and adapt a sqlnet.ora file. For VDAB this was not necessary.

Create two '''Symbolic Links'''.

$ ln -s /oracle/product/instantclient_10_2/libclntsh.so.10.1

/oracle/product/instantclient_10_2/libclntsh.so

$ ln -s /oracle/product/instantclient_10_2/libocci.so.10.1

/oracle/product/instantclient_10_2/libocci.so

== Install PHP ==
To '''install PHP '''on the Apache server, download php-5.2.5.tar.gz from [http://www.php.net/downloads http://www.php.net/downloads] to the folder /usr/local/apache2

Log in as root, '''uncompress the PHP files '''and go to the installation folder.

<nowiki># gzip -d php-5.2.5.tar.gz</nowiki>

<nowiki># tar -xvf php-5.2.5.tar</nowiki>

<nowiki># cd php-5.2.5</nowiki>

Adapt the '''Environment Variables '''to make sure the correct gcc and make are used.

<nowiki># export PATH=$PATH:/usr/sfw/bin:/usr/ccs/bin</nowiki>

<nowiki># export LD_LIBRARY_PATH=/oracle/product/instantclient_10_2</nowiki>

The following table provides a brief overview of the PHP extensions and what they are used for. All of these are required to do a fully functional Moodle installation.

{| class="prettytable"
! <center>PHP Extensions</center>
! <center>Description</center>

|-
| GD

Freetype 2
| GD is commonly used to generate charts, graphics, thumbnails, etc. on the fly.

Freetype provides an API to manipulate fonts.

Moodle uses these modules to generate dynamic graphs from the logs.

|-
| OCI8
| Required connector for Oracle

|-
| zlib (alternatively use zip or unzip)
| Zlib is required for zip/unzip funcitonality based on the deflate compression method.

Moodle itself can also handle this functionality, but this impacts the use of server resources.

|-
| curl
| curl is a client to get files from servers. It is used for handling files using a wide variety of protocols.

This is a requirement for Moodle 1.8 and later

|-
| openssl
| Library to enable secured connections to a server. This is mainly used for connections between Moodle installations e.g. to share courses.

|-
| php5-LDAP
| Enables the use of LDAP functions in PHP

|-
| aspell-xx
| The optional aspell modules provide a free spelling checker functionality embedded in Moodle. This module support a very large number of languages. XX represents the 2-letter code for the language.

|}
For a default Solaris most of these modules are available by default. We only need to install curl and enable these modules in the Apache-Php configuration.

We first install curl. Download the package curl-7.18.1.tar.gz from [http://curl.haxx.se/ http://curl.haxx.se] to /usr/local/apache2.

Log in as root, '''uncompress the curl files '''and go to the installation folder to '''make''' and '''install'''.

<nowiki># gunzip curl-7.18.1.tar.gz</nowiki>

<nowiki># tar -xvf curl-7.18.1.tar</nowiki>

<nowiki># cd curl-7.18.1</nowiki>

<nowiki># ./configure</nowiki>

<nowiki># make</nowiki>

<nowiki># make install</nowiki>

In order to '''test''' the curl installation do

/usr/local/bin/curl -V

If necessary, extend PATH to /usr/local/bin. This was not necessary for VDAB.

Next, we will configure, and '''install the PHP for Apache make links to the PHP extensions'''.

<nowiki># cd /usr/local/apache2/php-5.2.5</nowiki>

<nowiki># ./configure \</nowiki>

--with-apxs2=/usr/local/apache2/bin/apxs \

--with-config-file-path=/usr/local/apache2/conf \

--with-oci8=instantclient,/oracle/product/instantclient_10_2 \

--enable-sigchild \

--enable-mbstring \

--with-gd \

--with-openssl \

--with-curl=/usr/local/apache2/curl-7.18.1

--with-ldap=/usr/local

<nowiki># make</nowiki>

<nowiki># make install</nowiki>

== Change PHP settings ==
By default there is no php.ini file. However, there is a php.ini-recommended which we will use to make the required adaptations listed in the table below. Afterwards we will make a copy of this file and make it the active Php configuration file.

<nowiki># vi /usr/local/apache2/conf/php.ini-recommended --> Open text editor and make adaptations</nowiki>

<nowiki># cp /usr/local/apache2/php-5.2.5/php.ini-recommended /usr/local/apache2/conf/php.ini</nowiki>

'''In the file edit the following settings:'''

{| class="prettytable"
! <center>Setting</center>
! <center>Value we used in php.ini</center>

|-
| Safe mode must be off
| <nowiki>; Safe mode</nowiki>

safe_mode = Off

|-
| memory_limit is at least 128MB
| <nowiki>; Resource Limits</nowiki>

memory_limit = 128M <nowiki>; Maximum amount of memory a script may consume</nowiki>

|-
| session.save_handler needs to be set to FILES.
| <nowiki>[Session]</nowiki>

<nowiki>; Handler used to store/retrieve data.</nowiki>

session.save_handler = files

|-
| magic_quotes_gpc needs to be ON

magic_quotes_runtime needs to be OFF
| <nowiki>; Magic quotes for incoming GET/POST/Cookie data.</nowiki>

magic_quotes_gpc = On

<nowiki>; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.</nowiki>

magic_quotes_runtime = Off

|-
| file_uploads needs to be ON
| <nowiki>; Whether to allow HTTP file uploads.</nowiki>

file_uploads = On

|-
| session.auto_start needs to be OFF
| <nowiki>; Initialize session on request startup.</nowiki>

session.auto_start = 0

|-
| session.bug_compat_warn needs to be OFF
| session.bug_compat_warn = 0

|-
| post_max_size is too small by default and needs to be increased e.g. when you run into problems while creating online content
| <nowiki>; Maximum size of POST data that PHP will accept.</nowiki>

post_max_size = 300M

|-
| upload_max_filesize needs to be increased e.g. to allow uploading larger course packages
| <nowiki>; Maximum allowed size for uploaded files.</nowiki>

upload_max_filesize = 300M

|-
| magic_quotes_sybase should be on for Oracle installations.
| magic_quotes_sybase = On

|}
== Add GNU Coreutils ==
Also install the GNU Coreutils for Solaris in order to avoid Apache error described in case MDL-6850 . The Coreutils will include the du command which is required by Moodle to collect and calculate data on file sizes.

'''Download '''coreutils-6.4-sol10-sparc-local.gz from [http://www.sunfreeware.com/solaris_2.5_list.html#coreutils http://www.sunfreeware.com/solaris_2.5_list.html#coreutils] to your global zone as root .

gunzip coreutils-6.4-sol10-sparc-local.gz

pkgadd -d coreutils-6.4-sol10-sparc-local.gz

Go to Administration > Configuration > Variables > Operating System and enter the path to entry pathtodu to the GNU du in /usr/local/bin/du (was /usr/bin/du) .

Set the correct path in the Moodle administration interface. Go to Administration > Server > System Paths and fill out the correct path in the Path to du entry.

= Install Moodle =
== Prepare the Moodle installation files ==
Now that we have completed the set-up for Apache, PHP, Oracle and the connection between PHP and Oracle we prepare for the Moodle installation.

Log in as root and '''create a moodle user''' assigned to a group and set a password.

<nowiki># mkdir /export/home/moodle</nowiki>

<nowiki># useradd -u 1005 -g 101 -d /export/home/moodle -s /bin/bash -c "Moodle" -m moodle</nowiki>

<nowiki># chown moodle:users /export/home/moodle</nowiki>

<nowiki># passwd moodle</nowiki>

Log in as root to '''create a directory for the Moodle installation''':

<nowiki># mkdir /usr/local/moodle_1.9+</nowiki>

<nowiki># chown moodle:users /usr/local/moodle_1.9+</nowiki>

'''Download '''moodle-weekly-19.tgz from [http://download.moodle.org/ http://download.moodle.org/]. Log in as the user moodle and copy the file to /usr/local/moodle_1.9+ and uncompress the file:

$ gunzip moodle-weekly-19.tgz

$ tar -vxf moodle-weekly-19.tar --> creates subdirectory 'moodle'

Now log onto the system where you will install Moodle e.g. testzone3 on server testitis03 as the user moodle.

Set the '''environment variables''', preferable in the .profile of the de user moodle:

$ export ORACLE_HOME=/oracle/product/instantclient_10_2

$ export LD_LIBRARY_PATH=$ORACLE_HOME

$ export TNS_ADMIN=/var/opt/oracle

$ export PATH=$PATH:/usr/local/bin:/local/bin:.

'''Start Apache '''with the configuration file adapted to moodle:

$ /usr/local/apache2/bin/apachectl -k start -f /usr/local/moodle_1.9+/moodle/httpd.conf

If desired you can install other languages during the installation wizard by downloading the appropriate language files e.g. Dutch ([http://download.moodle.org/lang16/nl_utf8.zip http://download.moodle.org/lang16/nl_utf8.zip]) to /usr/local/moodle_1.9+/moodledata/lang and uncompress the file.

<nowiki># unzip nl_utf8.zip </nowiki>

A list of additional languages is available from the administration interface. Moodle then automatically downloads and installs the selected languages.

== Choose installation language ==
Choose the installation language from the drop-down list. This choice only applies to the installation wizard.

Click the next button to continue.

[[Image:Image001.jpg]]

== Check PHP settings ==
If you followed the above mentioned instructions for php, you should get the following screen.

In case of a Fail, recheck the PHP settings in php.ini.

[[Image:Image002.jpg]]

== Set installation and data directories ==
In this step you define the basic locations of all Moodle-related files. Unless you chose a different location for the moodledata folder you do not need to change anything.

It is adviseable to keep the Moodle software and the data (courses, uploaded assignments etc.) separately;

In case of VDAB the web address is e.g. testzone2 or testzone3 and the data directory is /usr/local/moodle_1.9+/moodle

[[Image:Image003.jpg]]

== Set Database connection ==
In this step we will set up the connection to the database:

* Select Oracle from the drop-down list
* For an Oracle installation, leave the Host entry empty
* Provide the name of the Oracle database you created e.g. moodle
* The database admin username and password
* Add a table prefix e.g. m_

[[Image:Image004.jpg]]

== Server checks for installed components ==
The installation wizard will now perform an '''availability check '''on the required System Components.

If you checked all the required PHP settings and modules during the pre-installation phase, you should get the following screen.

[[Image:Image005.jpg]]

== Install language packs ==
Since we chose a '''Dutch installation''', we now get an option to download the '''Dutch language files '''for the user interface. Provided you have direct write access to the Moodle server, the set-up of the language pack is '''automatic'''.

[[Image:Image006.jpg]]If the '''download is unsuccessful''', you will get the error message below. To resolve this problem, you can either:

* Select other languages by using the ''Administrator interface ''when the installation is complete (Administration > Language > Language packs).
* ''Unzip the language file on the server ''in the lang files directory e.g. <nowiki><path to Moodle directory>/moodledata/lang</nowiki>

[[Image:Image007.jpg]]

== Confirmation for written configuration file. ==
All the settings we made in prior steps are now collected and written to the '''Moodle configuration file '''(config.php).

[[Image:Image008.jpg]]In this step, the basic Moodle configuration is complete. In the next steps, the setup will add the database tables and prepare Moodle for use.

== Licence agreement ==
Carefully read and '''accept the licence agreement '''before proceeding to the final installation steps.

[[Image:Image009.jpg]]

== Release information ==
This page provides the release information and the possibility to perform the following steps automatically (unattended). We will simply click next in order to capture potential setup errors.

[[Image:Image010.jpg]]

Following steps can be performed automatically (unattended) or with manual confirmation.

== Automatic database setup ==
What follows is a series of screens for the '''setup of the database tables for all of the standard Moodle components'''. Apart from clicking next, no user interaction is required.

[[Image:Image011.jpg]]After each sequence a '''confirmation of success '''appears.

[[Image:Image012.jpg]]This is the final step in the database set-up sequence.

[[Image:Image013.jpg]]

== Setting up the administrator account ==
Now that the system is ready, we only need to provide details for an initial administrator account.

These data can be changed and/or complemented later. This is the account that will initially be used after installation to allow further configuration of the system.

[[Image:Image014.jpg]]

== Set up Frontpage ==
During this final step of the installation wizard, we will put:

* The '''Full site name '''e.g. the name of the institution. This will be visible in the title bar in all of the standard templates.
* As '''Short name for the site'''.
* A '''Front page description''' of the site. This will be displayed as a welcome message on the start page.

[[Image:Image015.jpg]]

== Start with empty Moodle ==
We are then automatically redirected to the '''Moodle start page'''. Our Moodle is up and running and we can now continue with the configuration of the system.

[[Image:Image016.jpg]]

When we click '''Turn editing on''' we can start the configuration. We will need to verify the system location of some additional components. The installation procedure does not check for the availability of a zip program. Moodle especially needs zip and unzip when handling SCORM packages. Using the built-in unzip feature may impact server performance.

[[Image:Image017.jpg]]

== Add template ==
To add a theme to a Moodle installation:

* Extract a theme to /usr/local/moodle_1.9+/moodledata/theme
* Log into Moodle as admin, go to Site Administration >Appearance >Themes > Theme Selector
* Select the theme from the list.

==See also==

[[Category:Installation]]

Unix or Linux Installation

2012-01-02T19:04:09Z

Howardsmiller:

Manual installation on Ubuntu

2012-01-02T19:03:05Z

Howardsmiller: moved Manual installation on Ubuntu to Installation on Ubuntu 8.04

#REDIRECT [[Installation on Ubuntu 8.04]]

Installation on Ubuntu 8.04

2012-01-02T19:03:05Z

Howardsmiller: moved Manual installation on Ubuntu to Installation on Ubuntu 8.04

The instructions herein refer to the installation of Moodle without using the Debian/Ubuntu package(s). This method, while acceptable on many Linux platforms, is neither consistent with (nor compatible with) Debian/Ubuntu packaged versions of Moodle. Use at your own risk and do not mix with Debian/Ubuntu packages. (These instructions are very old and may be well-outdated.)

== Hardy Heron 8.04 ==

*[http://www.ubuntu.com/products/GetUbuntu/download#lts Ubuntu 8.04 LTS server CD]

=== Install Ubuntu ===
Start computer and boot from CD.

Select '''Install to hard drive'''.

Select your '''language''', '''country''', and '''keyboard layout''' (i.e. English, United States, American English)

Select '''[http://help.ubuntu.com/8.04/ubuntu/serverguide/C/network-configuration.html manually configure]''' and set an IP address (or autoconfig if you don't know).

Enter your servername (i.e. moodletest)

Select to '''manually edit the partition table'''. I’m doing my testing on a standard 40GB harddrive and will modify these sizes for production.

:<table>
:<tr><td width=%10>/boot</td><td width=%10>ext3</td><td align=right width=%10>200MB</td><td align=center width=%10>bootable</td>
<td>([http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/s1-grub-whatis.html may need to be under cylinder 1024 on your harddrive to be bootable])</td></tr>
:<tr><td>/</td><td>ext3</td><td align=right>10GB</td><td></td><td>(files are relatively static)</td></tr>
:<tr><td>swap</td><td></td><td align=right>4GB</td><td></td>
<td>(4xRAM if you don't have much memory, down to 1xRAM if you have gobs of memory)</td></tr>
:<tr><td>/var</td><td>ext3</td><td align=right>26GB</td><td></td><td>(variable content – uses rest of the drive)</td></tr>
:</table>

Select your '''timezone'''. (i.e. Central)

Set clock to '''Universal Time'''.

Enter Administrators '''full name'''. (i.e. Joe Smith)

Enter '''account name'''. (i.e. joesmith)

Enter a secure password. (‘abcde’ is not a good one!)

Let the computer restart.

Log in your account.

Edit the ''/etc/apt/sources.list'' file. Remove the ''#'' mark on lines 22 and 38 to enable access to the universe package source and universe security updates. You will need to re-enter your account password when ''sudo'' asks for it.
<pre>
sudo nano /etc/apt/sources.list
</pre>
Now to get all the security updates.
<pre>
sudo apt-get update

sudo apt-get dselect-upgrade
</pre>
Normally you would just use ''[http://help.ubuntu.com/6.06/ubuntu/serverguide/C/apt-get.html sudo apt-get upgrade]''.

And reboot to run on the new kernel!
<pre>
sudo reboot
</pre>

=== Install MySQL (skip Postgresql) ===
At this point we'll need to log in again to the server and type:

<pre>
sudo apt-get install mysql-server php5-mysql
</pre>
Press ''Y'' to continue the install.

Replace the following string ''NewRootDatabasePassword'' with a secure password of your own choosing.

There is no space between the ''-p'' and the password on the second command.
<pre>
mysqladmin -u root password NewRootDatabasePassword

mysqladmin -u root -h localhost password NewRootDatabasePassword -pNewRootDatabasePassword
</pre>

We now need to create the Moodle database and Moodle user in MySQL.

The mysql command will prompt for your ''NewRootDatabasePassword'' (from above).
Replace ''NewMoodleDatabasePassword'' with a secure password of your own choosing.
<pre>
mysql -u root -p
> CREATE DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
> GRANT ALL PRIVILEGES ON moodle.* TO moodleuser@localhost IDENTIFIED BY 'NewMoodleDatabasePassword';
> GRANT SELECT,LOCK TABLES on moodle.* TO moodlebackup@localhost IDENTIFIED BY 'MoodleBackupPassword';
> FLUSH PRIVILEGES;
> QUIT
</pre>
The above also creates a backup user moodlebackup so that you can use ''mysqldump'' to make database backups without accident.

=== Install Postgresql (skip MySQL) ===

At this point we'll need to log in again to the server and type:
<pre>
sudo apt-get install postgresql-8.1 php5-pgsql
</pre>
Press Y to continue the install.

We now need to create the database user 'moodleuser'.
<pre>
sudo -u postgres createuser -D -A -P moodleuser
</pre>
Enter in a ''NewMoodleDatabasePassword here'', then answer 'N' to the question.

We now need to create the database 'moodle' for the user 'moodleuser'. You'll need to enter the password that you just created.
<pre>
sudo -u postgres createdb -E utf8 -O moodleuser moodle
</pre>
Let's now secure the postgresql database with an admin password.
<pre>
sudo -u postgres psql template1
# ALTER USER postgres WITH PASSWORD 'NewAdminDatabasePassword';
# \q
</pre>
Edit the file '/etc/postgresql/8.1/main/pg_hba.conf' and on line 79 change the words ''ident sameuser'' to ''md5''.
<pre>
sudo nano /etc/postgresql/8.1/main/pg_hba.conf
</pre>
Restart the database so everything is fine.
<pre>
sudo /etc/init.d/postgresql-8.1 restart
</pre>

=== Install Apache ===

The following mod-security, ldap, and odbc libraries are optional.
<pre>
sudo apt-get install apache2 libapache2-mod-php5 php5-gd

sudo apt-get install libapache2-mod-security php5-ldap php5-odbc
</pre>

Restart Apache
<pre>
sudo /etc/init.d/apache2 restart
</pre>

'''Note:''' To install Moodle 2.0 for the current ubuntu, you need to [http://moodle.org/mod/forum/discuss.php?d=116604 install PHP from an external repository] --[[User:Olli Savolainen|Olli Savolainen]] 19:28, 10 April 2009 (UTC)

=== Install other software ===
On the command line, type:
<pre>
sudo apt-get install openssh-server unattended-upgrades

sudo apt-get install unzip zip aspell-en aspell-fr aspell-de aspell-es

sudo apt-get install curl php5-curl php5-xmlrpc

sudo apt-get install clamav-base clamav-freshclam clamav
</pre>
Press ''Y'' to continue the install after each of these apt-get commands.

The clamav package will support virus checking on file uploads into Moodle. May have to run it again to configure properly.

Additional languages are available for aspell.

=== Install Moodle ===
On the command line, type:
<pre>
cd /var/www

sudo wget http://download.moodle.org/stable19/moodle-latest-19.tgz

sudo tar -zxf moodle-latest-19.tgz

----
in ubuntu 8.04 it should be:
sudo tar zxf moodle-latest-19.tgz
----

sudo mkdir /var/moodledata

sudo chown -R www-data:www-data /var/moodledata
where www-data is whatever user/group was created automatically when apache was installed.
</pre>

We now need to edit the location of the default web site. On lines five and ten, replace ''/var/www/'' with ''/var/www/moodle/''. Restart Apache. (See page comments for more details on this instruction.)
<pre>
sudo nano /etc/apache2/sites-available/default

sudo /etc/init.d/apache2 restart
</pre>

=== Configure Moodle website ===
ifconfig (look for your server’s ip address on the 2nd line).

On another computer open a web browser and put in your server address. Make sure your web browser is set to accept cookies.

Complete the Moodle install using a secure username and password.

Go to a bar for a few hours.

Come back and tell your boss that you FINALLY got the test server running.

== Other Resources ==
* [http://ubuntuguide.org/wiki/Moodle_tips Ubuntuguide -- Moodle tips]
* [http://kubuntuguide.org/Moodle_tips Kubuntuguide -- Moodle tips]
* Ubuntu - [http://help.ubuntu.com/community/Security 1] [http://www.computerworld.com/action/article.do?command=printArticleBasic&articleId=9002691 2] security
* Debian - [http://www.debian.org/security/ 1] [http://www.us.debian.org/doc/user-manuals#securing 2] security
* Setting up a secure LAMP Webserver on Debian Etch (May 22nd, 2008) [http://news.metaparadigma.de/?p=248]
* Linux - [http://www.linux-sec.net/ 1] [http://www.puschitz.com/SecuringLinux.shtml 2] [http://www.linuxsecurity.com/docs/LDP/Security-HOWTO/ 3] security
* MySQL - [http://dev.mysql.com/doc/refman/5.0/en/security.html 1] [http://www.securityfocus.com/infocus/1667 2] security
* Apache - [http://httpd.apache.org/docs/2.0/misc/security_tips.html 1] [http://www.cisecurity.org/bench_apache.html 2] security
* [http://www.modsecurity.org/documentation/index.html Modsecurity apache2 module]
* Another (old) [http://help.ubuntu.com/community/MySQLMoodle Ubuntu and Moodle install] document
* Moodle [[Security]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=125912 HowTo: Installing aspell in Ubuntu (with dictionary)] forum discussion

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Unix or Linux Installation

2012-01-02T18:59:39Z

Howardsmiller:

Installation on Ubuntu using Git

2012-01-02T18:50:53Z

Howardsmiller: /* See also */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories) on Desktop or log into the terminal on Server.
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* (on Desktop) open a web browser and go to http://localhost/ and make sure you see 'It works!'.
* (on Server) open a web browser on a remote machine and go to http://name.or.ip.of.server/ and make sure you see 'It works!'.

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The checkout switches to the latest (weekly) of the 2.1 branch. The chmod (temporarily) allows the installation script to write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
cd moodle
git checkout -t origin/MOODLE_21_STABLE
chmod 0777 /var/www/moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

The standard configuration of Apache on Ubuntu should work fine and will give you a Moodle URL of http://name.or.ip.of.server/moodle (or http://localhost/moodle).

If you need other configurations or a different form of URL, now is the time to configure this. However, this is not covered here. There is lots of information online, although do note that the Ubuntu Apache configuration is rather different to the standard layout.

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

Don't skip this step. This secures the Moodle code, preventing it being overwritten by hackers.

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

==See also==

* [https://help.ubuntu.com/community/Installation Installing Ubuntu]
* [https://help.ubuntu.com/community/ApacheMySQLPHP Ubuntu LAMP/Apache documentation]

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T18:47:47Z

Howardsmiller: /* Troubleshooting */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories) on Desktop or log into the terminal on Server.
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* (on Desktop) open a web browser and go to http://localhost/ and make sure you see 'It works!'.
* (on Server) open a web browser on a remote machine and go to http://name.or.ip.of.server/ and make sure you see 'It works!'.

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The checkout switches to the latest (weekly) of the 2.1 branch. The chmod (temporarily) allows the installation script to write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
cd moodle
git checkout -t origin/MOODLE_21_STABLE
chmod 0777 /var/www/moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

The standard configuration of Apache on Ubuntu should work fine and will give you a Moodle URL of http://name.or.ip.of.server/moodle (or http://localhost/moodle).

If you need other configurations or a different form of URL, now is the time to configure this. However, this is not covered here. There is lots of information online, although do note that the Ubuntu Apache configuration is rather different to the standard layout.

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

Don't skip this step. This secures the Moodle code, preventing it being overwritten by hackers.

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

==See also==

* [https://help.ubuntu.com/community/ApacheMySQLPHP Ubuntu LAMP/Apache documentation]

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T18:44:32Z

Howardsmiller: /* and finally */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories) on Desktop or log into the terminal on Server.
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* (on Desktop) open a web browser and go to http://localhost/ and make sure you see 'It works!'.
* (on Server) open a web browser on a remote machine and go to http://name.or.ip.of.server/ and make sure you see 'It works!'.

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The checkout switches to the latest (weekly) of the 2.1 branch. The chmod (temporarily) allows the installation script to write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
cd moodle
git checkout -t origin/MOODLE_21_STABLE
chmod 0777 /var/www/moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

The standard configuration of Apache on Ubuntu should work fine and will give you a Moodle URL of http://name.or.ip.of.server/moodle (or http://localhost/moodle).

If you need other configurations or a different form of URL, now is the time to configure this. However, this is not covered here. There is lots of information online, although do note that the Ubuntu Apache configuration is rather different to the standard layout.

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

Don't skip this step. This secures the Moodle code, preventing it being overwritten by hackers.

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T15:50:15Z

Howardsmiller: /* Install Moodle code */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories) on Desktop or log into the terminal on Server.
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* (on Desktop) open a web browser and go to http://localhost/ and make sure you see 'It works!'.
* (on Server) open a web browser on a remote machine and go to http://name.or.ip.of.server/ and make sure you see 'It works!'.

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The checkout switches to the latest (weekly) of the 2.1 branch. The chmod (temporarily) allows the installation script to write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
cd moodle
git checkout -t origin/MOODLE_21_STABLE
chmod 0777 /var/www/moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

The standard configuration of Apache on Ubuntu should work fine and will give you a Moodle URL of http://name.or.ip.of.server/moodle (or http://localhost/moodle).

If you need other configurations or a different form of URL, now is the time to configure this. However, this is not covered here. There is lots of information online, although do note that the Ubuntu Apache configuration is rather different to the standard layout.

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T15:48:55Z

Howardsmiller: /* Configure apache */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories) on Desktop or log into the terminal on Server.
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* (on Desktop) open a web browser and go to http://localhost/ and make sure you see 'It works!'.
* (on Server) open a web browser on a remote machine and go to http://name.or.ip.of.server/ and make sure you see 'It works!'.

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The checkout switches to the latest (weekly) of the 2.1 branch.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
cd moodle
git checkout -t origin/MOODLE_21_STABLE
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

The standard configuration of Apache on Ubuntu should work fine and will give you a Moodle URL of http://name.or.ip.of.server/moodle (or http://localhost/moodle).

If you need other configurations or a different form of URL, now is the time to configure this. However, this is not covered here. There is lots of information online, although do note that the Ubuntu Apache configuration is rather different to the standard layout.

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T15:44:10Z

Howardsmiller: /* Install Moodle code */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories) on Desktop or log into the terminal on Server.
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* (on Desktop) open a web browser and go to http://localhost/ and make sure you see 'It works!'.
* (on Server) open a web browser on a remote machine and go to http://name.or.ip.of.server/ and make sure you see 'It works!'.

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The checkout switches to the latest (weekly) of the 2.1 branch.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
cd moodle
git checkout -t origin/MOODLE_21_STABLE
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

'''NOTE TO UBUNTU USERS''': If you are following these instructions for vanilla Ubuntu then you can ignore this step. The default Apache configuration will 'just work'.

Apache is configured for mythweb so needs a small tweak to work:

<pre>
cd /etc/apache2/sites-enabled
</pre>

Use your favourite editor to edit the file default-mythbuntu. After the closing </Directory> on (or about) line 15 add:

<pre>
<Directory /var/www/moodle/>
DirectoryIndex index.php
order allow,deny
allow from all
</Directory>
</pre>

make sure you do not add any spaces in 'allow,deny'. Save and exit.

Restart Apache:

<pre>
/etc/init.d/apache2 restart
</pre>

(A force-reload will not be enough).

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T15:41:53Z

Howardsmiller: /* Basic Setup */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories) on Desktop or log into the terminal on Server.
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* (on Desktop) open a web browser and go to http://localhost/ and make sure you see 'It works!'.
* (on Server) open a web browser on a remote machine and go to http://name.or.ip.of.server/ and make sure you see 'It works!'.

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The chmod is so the installer can write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
chmod 0777 moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

'''NOTE TO UBUNTU USERS''': If you are following these instructions for vanilla Ubuntu then you can ignore this step. The default Apache configuration will 'just work'.

Apache is configured for mythweb so needs a small tweak to work:

<pre>
cd /etc/apache2/sites-enabled
</pre>

Use your favourite editor to edit the file default-mythbuntu. After the closing </Directory> on (or about) line 15 add:

<pre>
<Directory /var/www/moodle/>
DirectoryIndex index.php
order allow,deny
allow from all
</Directory>
</pre>

make sure you do not add any spaces in 'allow,deny'. Save and exit.

Restart Apache:

<pre>
/etc/init.d/apache2 restart
</pre>

(A force-reload will not be enough).

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T15:39:21Z

Howardsmiller: /* Install Ubuntu */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] or [http://www.ubuntu.com/download/server/download Ubuntu Server] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories)
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
</pre>

if ordinary ubuntu add the following to the above list
<pre>
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* On Ubuntu (only), go to http://localhost/ and make sure you see 'It works!'

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The chmod is so the installer can write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
chmod 0777 moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

'''NOTE TO UBUNTU USERS''': If you are following these instructions for vanilla Ubuntu then you can ignore this step. The default Apache configuration will 'just work'.

Apache is configured for mythweb so needs a small tweak to work:

<pre>
cd /etc/apache2/sites-enabled
</pre>

Use your favourite editor to edit the file default-mythbuntu. After the closing </Directory> on (or about) line 15 add:

<pre>
<Directory /var/www/moodle/>
DirectoryIndex index.php
order allow,deny
allow from all
</Directory>
</pre>

make sure you do not add any spaces in 'allow,deny'. Save and exit.

Restart Apache:

<pre>
/etc/init.d/apache2 restart
</pre>

(A force-reload will not be enough).

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T15:37:37Z

Howardsmiller: /* Install Mythbuntu */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Ubuntu==

* Install [http://ubuntu.org/ Ubuntu Desktop] using (if in doubt) default settings

==Basic Setup==

* Open a terminal window (from Applications>Accessories)
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
</pre>

if ordinary ubuntu add the following to the above list
<pre>
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* On Ubuntu (only), go to http://localhost/ and make sure you see 'It works!'

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The chmod is so the installer can write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
chmod 0777 moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

'''NOTE TO UBUNTU USERS''': If you are following these instructions for vanilla Ubuntu then you can ignore this step. The default Apache configuration will 'just work'.

Apache is configured for mythweb so needs a small tweak to work:

<pre>
cd /etc/apache2/sites-enabled
</pre>

Use your favourite editor to edit the file default-mythbuntu. After the closing </Directory> on (or about) line 15 add:

<pre>
<Directory /var/www/moodle/>
DirectoryIndex index.php
order allow,deny
allow from all
</Directory>
</pre>

make sure you do not add any spaces in 'allow,deny'. Save and exit.

Restart Apache:

<pre>
/etc/init.d/apache2 restart
</pre>

(A force-reload will not be enough).

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installation on Ubuntu using Git

2012-01-02T15:36:32Z

Howardsmiller: /* Introduction */

==Introduction==

This page gives the basic steps to install Moodle on Ubuntu using Moodle code from Git. This is generally a better idea than using the Ubuntu '.deb' package.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should work on either Ubuntu Desktop or Server edition.

==Install Mythbuntu==

* Install [http://www.mythbuntu.org/ Mythbuntu] or ordinary [http://ubuntu.org/ Ubuntu Desktop] using (if in doubt) default settings
* Log in and exit MythTV application (using Escape Key) (not on Ubuntu)
* '''Mythbuntu''': Run Firefox and ensure that 'mythweb' is running at localhost (proving the web server is running)

==Basic Setup==

* Open a terminal window (from Applications>Accessories)
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
</pre>

if ordinary ubuntu add the following to the above list
<pre>
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* On Ubuntu (only), go to http://localhost/ and make sure you see 'It works!'

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The chmod is so the installer can write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
chmod 0777 moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

'''NOTE TO UBUNTU USERS''': If you are following these instructions for vanilla Ubuntu then you can ignore this step. The default Apache configuration will 'just work'.

Apache is configured for mythweb so needs a small tweak to work:

<pre>
cd /etc/apache2/sites-enabled
</pre>

Use your favourite editor to edit the file default-mythbuntu. After the closing </Directory> on (or about) line 15 add:

<pre>
<Directory /var/www/moodle/>
DirectoryIndex index.php
order allow,deny
allow from all
</Directory>
</pre>

make sure you do not add any spaces in 'allow,deny'. Save and exit.

Restart Apache:

<pre>
/etc/init.d/apache2 restart
</pre>

(A force-reload will not be enough).

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Unix or Linux Installation

2012-01-02T15:32:55Z

Howardsmiller:

{{Template:Installing Moodle}}

The following pages provide installation information for specific Unix or Linux platforms. This information is provided by the Moodle community and may not have been fully checked and may be out of date (sometimes very). It is provided in the hope that it is useful.

* [[Installation on Ubuntu using Git]]

Unix or Linux Installation

2012-01-02T15:31:52Z

Howardsmiller: Created page with "The following pages provide installation information for specific Unix or Linux platforms. This information is provided by the Moodle community and may not have been fully checke..."

The following pages provide installation information for specific Unix or Linux platforms. This information is provided by the Moodle community and may not have been fully checked and may be out of date (sometimes very). It is provided in the hope that it is useful.

* [[Installation on Ubuntu using Git]]

Manual installation of Moodle 2.0 on Mythbuntu using Git

2012-01-02T15:31:25Z

Howardsmiller: moved Manual installation of Moodle 2.0 on Mythbuntu using Git to Installation on Ubuntu using Git

#REDIRECT [[Installation on Ubuntu using Git]]

Installation on Ubuntu using Git

2012-01-02T15:31:25Z

Howardsmiller: moved Manual installation of Moodle 2.0 on Mythbuntu using Git to Installation on Ubuntu using Git

==Introduction==

This is probably an unrealistic scenario but it stemmed from a question asked in the forums and the results might be useful to others. This was done on Mythbuntu 10.10. Mythbuntu is one of the Ubuntu derivatives, in this case providing a Linux based TV package. It comes with PHP, Apache and MySQL installed having its own web-based controller.

There was no intention to provide a fully secured production server. This just gets basic Moodle working on 'localhost'.

This should also work fine for ordinary Ubuntu with the noted changes.

==Install Mythbuntu==

* Install [http://www.mythbuntu.org/ Mythbuntu] or ordinary [http://ubuntu.org/ Ubuntu Desktop] using (if in doubt) default settings
* Log in and exit MythTV application (using Escape Key) (not on Ubuntu)
* '''Mythbuntu''': Run Firefox and ensure that 'mythweb' is running at localhost (proving the web server is running)

==Basic Setup==

* Open a terminal window (from Applications>Accessories)
* become root (and stay there right through this), install some additional software (git and php extras Moodle needs):
<pre>
sudo su (you will need to enter your password)
apt-get update
apt-get install git git-core git-doc
apt-get install php5-gd php5-curl php5-intl php5-xmlrpc
</pre>

if ordinary ubuntu add the following to the above list
<pre>
apt-get install php5 mysql-server mysql-client apache2 php5-mysql
</pre>

* On Ubuntu (only), go to http://localhost/ and make sure you see 'It works!'

==Install Moodle code==

We're going to use Git to pull the latest code. You could just download it, but this is more fun! The chmod is so the installer can write the config file.

<pre>
cd /var/www
git clone git://git.moodle.org/moodle.git
chmod 0777 moodle
</pre>

* The moodle code location (for installation) is /var/www/moodle

==Create the data area==

You can create this where you like (more or less) but I will do...

<pre>
mkdir /var/moodledata
chmod 0777 /var/moodledata
</pre>

* The moodle data location (for installation) is /var/moodledata

==Create the database==

You will need the root database password. Unless you have changed it, this is same as your login password (or whatever you set up when you installed MySQL above).

<pre>
mysql -u root -p
(asks for password here)
mysql> create database moodle default character set utf8;
mysql> grant all on moodle.* to moodleuser@localhost identified by 'mypassword';
mysql> exit
</pre>

'''Notes:'''
* don't type 'mysql>', that's just the prompt from the mysql client.
* The ''grant'' command creates the MySQL account 'moodleuser' with the supplied password and gives it rights to the moodle database all in one command.
* Set 'mypassword' to something you make up. This is the password for your moodle database
* When you install moodle the database is called 'moodle', the database user 'moodleuser' and the password as above

==Configure apache==

'''NOTE TO UBUNTU USERS''': If you are following these instructions for vanilla Ubuntu then you can ignore this step. The default Apache configuration will 'just work'.

Apache is configured for mythweb so needs a small tweak to work:

<pre>
cd /etc/apache2/sites-enabled
</pre>

Use your favourite editor to edit the file default-mythbuntu. After the closing </Directory> on (or about) line 15 add:

<pre>
<Directory /var/www/moodle/>
DirectoryIndex index.php
order allow,deny
allow from all
</Directory>
</pre>

make sure you do not add any spaces in 'allow,deny'. Save and exit.

Restart Apache:

<pre>
/etc/init.d/apache2 restart
</pre>

(A force-reload will not be enough).

==Install Moodle==

Open Firefox and go to address http://localhost/moodle
You should be able to install Moodle using the information indicated above

==and finally==

<pre>
chmod 0755 /var/www/moodle
exit
</pre>

==a quick note on updating==

Because we installed using Git, updating Moodle becomes surprisingly simple. Using the repository we did gives you the latest weekly at any time. If it matters, do a backup first then:

<pre>
sudo su
chmod /var/www/moodle
git pull
exit
</pre>

Then go to the Site administration > Notifications page in Moodle to complete the upgrade.

==Troubleshooting==

* Most errors will turn up in the web server logs. Always check there first - /var/log/apache2/errors.log
* If you need to change things like file upload sizes you need to edit /etc/php5/apache2/php.ini and then restart the web server with 'sudo /etc/init.d/apache2 restart'

[[Category:Administrator]]
[[Category:Installation|Ubuntu]]

Installing Moodle

2012-01-02T15:19:03Z

Howardsmiller: /* Platform specific instructions */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have two basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack... OR
* Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].

Either of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

== Platform specific instructions ==

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]
* [[Unix or Linux Installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Installing Moodle

2012-01-02T15:17:15Z

Howardsmiller: /* Platform specific instructions */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have two basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack... OR
* Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].

Either of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

== Platform specific instructions ==

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Installing Moodle

2012-01-02T15:14:04Z

Howardsmiller: /* If something goes wrong... */

{{Template:Installing Moodle}}

This and other installation pages are being updated. Please bear with us while this work is being completed

'''Don't panic!''' [[Image:F1 35px.png]]

This page explains how to install Moodle. Moodle runs on a large number of different configurations which are (mostly) explained in linked pages. Please take the time to find and read the parts that are relevant to you.

*If you are an expert and/or in a hurry try [[Installation Quickstart]].
*If you are upgrading from a previous version go to [[Upgrading to Moodle 2.1]]
*If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers.

== Planning ==
A Moodle installation will require planning. This may vary from almost nothing to a serious project. Here are a few things you might want to consider:

* Do you really want to install Moodle yourself at all? See [[Finding and Selecting A Web Host]].
* What skills do you have available to you or are prepared to learn? Administering a secure, stable public web server is a serious undertaking before Moodle even enters the discussion. This documentation assumes that you have (at least) a basic understanding of the platform on which you will be installing Moodle (or are prepared for a learning curve).
* What are your hardware/hosting requirements? Moodle scales easily but, depending on your requirements, you could be looking at anywhere along the spectrum - shared hosting, dedicated virtual host, your own server, your own multiple server setup.
* What software platforms will you use? This may depend on your skills or local policies. You may have a free choice.
* What are your support requirements? Will the free support in the moodle.org forums be sufficient or do you need professional support.
* How will you organise backups?

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:

The basic requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
* Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
* Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.

=== Software ===
* An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
* Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.
* [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.
* A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (but may never have been tested for optional plugins) but documentation and support is limited. SQLite support is experimental. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.
** [[MySQL]] - minimum version 5.0.25
** [[PostgreSQL]] - minimum version 8.3
** [[MSSQL]] - minimum version 9.0
** [[Oracle]] - minimum version 10.2
** [[SQLite]] - minimum version 2.0

==== Client ====
* Your clients/users access Moodle from a web browser on their PC/tablet/notepad. Any modern browser should work (but Internet Explorer version 6 and earlier are NOT supported). The operating system is not important but you may need software to read files that you upload (e.g. if you upload Microsoft Word files then all your users need software to read Word files)

=== Also read.... ===

Especially if you are planning a large or complex installation, read [[Performance]] and (in particular) the [[Performance FAQ]] to understand some common terms and concerns.

== Set up your server ==

...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]

== Download and copy files into place ==

'''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''

You have two basic options:
* Download your required version from http://moodle.org/downloads and unzip/unpack... OR
* Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
<pre>
$ git clone -b MOODLE_21_STABLE git://git.moodle.org/moodle.git
</pre>
...this fetches a complete copy of the Moodle repository and then switches to the 2.1 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]].

Either of the above should result in a directory called '''moodle''', containing a number of files and folders.

You can either place the whole folder in your web server documents directory, in which case the site will be located at '''<nowiki>http://yourwebserver.com/moodle</nowiki>''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''<nowiki>http://yourwebserver.com</nowiki>'''. See the documentation for your system and/or web server if you are unsure.

:''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.

* '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):
<pre>
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

== Create an empty database ==

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
* '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server
* '''dbname''' - the database name. Whatever you called it, e.g. ''moodle''
* '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
* '''dbpass''' - the password for the above user

If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:
* [[MySQL]]
* [[PostgreSQL]]
* [[MSSQL]]
* [[Oracle]]

== Create the (''moodledata'') data directory ==

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory.

'''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.

Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

==== Securing moodledata in a web directory ====

If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
<pre>
order deny,allow
deny from all
</pre>

== Start Moodle install ==
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.

=== Command line installer ===

It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')

* Example of using the command-line installer (as root - substitute 'www-data' for your web user):
<pre>
# chown www-data /path/to/moodle
# cd /path/to/moodle/admin/cli
# sudo -u www-data /usr/bin/php install.php
# chown -R root /path/to/moodle
</pre>
The chowns allow the script to write a new config.php file. More information about the options can be found using
<pre>
# php install.php --help
</pre>

You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]

=== Web based installer ===
To run the web installer script, just go to your Moodle's main URL using a web browser.

The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new Course.

It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.

==Final configuration==

=== Settings within Moodle ===
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
* ''Settings > Site administration > Server > Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
* ''Settings > Site administration > Server > Systen paths'': Set the paths to du, dot and aspell binaries.
* ''Settings > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Settings > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date.

=== Remaining tasks ===

* '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].
* '''Set up backups''': See [[Site backup]] and [[Automated course backup]].
* '''Check mail works''': Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details).
* '''Secure your Moodle site''': Read the information on [[Security]].

=== Installation is complete :) ===

* Create a new course: You can now [[Adding/editing a course|create a new course]] and have a play ;-)

=== If something goes wrong... ===

Here are some things you should try...

* Check the [[Installation FAQ]]
* Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
* Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
* If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
* Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
* Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
* Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
* Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!

=== Platform specific instructions ===

'''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.

* [[Windows installation]]

== See also ==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[RedHat Linux installation]]
* [[CentOS Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
[[ru:Установка Moodle]]
[[zh:安装Moodle]]
{{Review}}

Upgrading

2012-01-02T10:19:34Z

Howardsmiller: /* Install the new Moodle software */

{{Installing Moodle}}
'''Before you do anything else, read [[Upgrading to Moodle 2.1]]'''

Moodle is designed to upgrade itself from one version to the next. The procedure is
# [[Site backup|Back up everything]].
# Replace the old version of the code with the new one.
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.
These steps are explained in more detail below.

Sometimes there are specific considerations when upgrading to a particular version. See the [[dev:Releases|Releases page]] for more information on this. You also have to be more careful if you have installed additional plug-ins or customised the code.

See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.

__TOC__

When upgrading a Moodle installation you should follow these steps:

==Before you upgrade your site for real==

You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work. If you decide not to do this, make sure you have good backups. If the upgrade fails you will need the backups to go back.

==Check the requirements==
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in ''Settings > Site administration > Server > [[Environment]]''.

==Put your Site into Maintenance Mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.

== Backup important data ==
See [[Site backup]] for more specific information.

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, the SQL or Postgres database)

Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily. Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.

:''TIP:'' One more time, "do not risk what you can not afford to lose": do regular backups, make sure it is really backed up and know how to restore a backup!

== Install the new Moodle software ==
Upgrading can be a simple process or a more complicated process. Sites that have not used contributed code and are migrating from say Moodle 2.x.1 to 2.x.3 '''should''' not have a problem. However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.

*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.

=== Standard install package ===
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.
*It is probably a good idea to use the [[Site administration block]]>Server>Maintenance mode to prevent user activity as the site upgrades.
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet).
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.

=== Using a downloaded archive ===
In some installs, the site administrator may overwrite the Moodle code with a backup copy. Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders).

*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or "cleaned" installations. The best way is to rename the current Moodle code directory (for example rename "moodle" to "moodleold"), then unpack the new Moodle archive into the old location (for example, a new directory called "moodle").

====Linux====
mv moodle moodle.backup
tar xvzf moodle-1.1.tgz

Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one ('''check that optional/custom plugins are the correct version for your new Moodle first'''):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to

sudo chown www-data moodle/config.php

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')

if necessary.

where www-data is whatever user the Apache user is on your system. This is often 'apache' or 'www'.
You can find out by doing 'ls -l' in your /var/www/moodle folder (or wherever your moodle site is)
and then looking at the owner and group.

so you may see something like

ls -l
...lots of lines...
-rw-r--r-- 1 apache system 784 Jun 28 2007 config.php
...lots more lines...

so the owner is apache and the group is system.

To replicate this on your new system you can do 'chown apache:system config.php'

or to do a whole group do

chown apache:system ./*

and recursively

chown -R apache:system ./*

=== Using CVS ===

New sites should now use Git rather than CVS (see next section). If your site already uses CVS, to update, just go into the Moodle root directory and update to the new files:
<pre>
$ cd /path/to/your/moodle/
$ cvs update -dP
</pre>
To update from an older version type in the following:
<pre>
$ cd /path/to/your/moodle/
$ cvs -Q update -dP -r MOODLE_18_STABLE
</pre>
Make sure you use the "d" parameter to create new directories if necessary, and the "P" parameter to prune empty directories.

=== Using Git ===

You can use [[Git]] for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to GIt.

See [[Git for Administrators]] for further details.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

To do this just visit the [[Site administration block]] admin page (or ''<nowiki>http://example.com/moodle/admin</nowiki>'') and the "Notifications" link.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

:''TIP:'' Use the site administration block>Server>Maintenance mode to prevent users from changing data during the upgrade.
:''TIP:'' If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing. Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.

== Verify the upgrade (optional) ==

If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

==Upgrading more than one version==

Normally you can upgrade directly form any Moodle version to any later version. So, for example you could upgrade from 2.0 to 2.1, or from 1.9.

However, every so often, this general rule gets broken, because supporting really large jumps would be impossible. So far, the break points have been:
* You must have upgraded to version 1.9.x before you can upgrade to a later 2.x version.

==See also==

*[[Upgrading to Moodle 2.1]]
*[[Environment]]
*[[Git]] Version control and upgrading
*[[How to fix just one bug without upgrading]]
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).

Using Moodle.org forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=56915 Upgrading from 1.5.2 to 1.7]
*[http://moodle.org/mod/forum/discuss.php?d=56991 Upgrade nightmares.... any help appreciated]
*[http://moodle.org/mod/forum/discuss.php?d=62463 After upgrading i get "Your site may not be secure." msg]
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[nl:Upgraden]]
[[zh:升级]]
[[pl:Aktualizacja]]
[[de:Aktualisierung von Moodle]]
[[ru:Обновление]]

Upgrading

2012-01-02T10:18:18Z

Howardsmiller: /* Before you upgrade your site for real */

{{Installing Moodle}}
'''Before you do anything else, read [[Upgrading to Moodle 2.1]]'''

Moodle is designed to upgrade itself from one version to the next. The procedure is
# [[Site backup|Back up everything]].
# Replace the old version of the code with the new one.
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.
These steps are explained in more detail below.

Sometimes there are specific considerations when upgrading to a particular version. See the [[dev:Releases|Releases page]] for more information on this. You also have to be more careful if you have installed additional plug-ins or customised the code.

See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.

__TOC__

When upgrading a Moodle installation you should follow these steps:

==Before you upgrade your site for real==

You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work. If you decide not to do this, make sure you have good backups. If the upgrade fails you will need the backups to go back.

==Check the requirements==
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in ''Settings > Site administration > Server > [[Environment]]''.

==Put your Site into Maintenance Mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.

== Backup important data ==
See [[Site backup]] for more specific information.

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, the SQL or Postgres database)

Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily. Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.

:''TIP:'' One more time, "do not risk what you can not afford to lose": do regular backups, make sure it is really backed up and know how to restore a backup!

== Install the new Moodle software ==
Upgrading can be a simple process or a more complicated process. Sites that have not used contributed code and are migrating from say Moodle 1.x.1 to 1.x.3 '''should''' not have a problem. However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.

*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.

=== Standard install package ===
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.
*It is probably a good idea to use the [[Site administration block]]>Server>Maintenance mode to prevent user activity as the site upgrades.
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet).
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.

=== Using a downloaded archive ===
In some installs, the site administrator may overwrite the Moodle code with a backup copy. Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders).

*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or "cleaned" installations. The best way is to rename the current Moodle code directory (for example rename "moodle" to "moodleold"), then unpack the new Moodle archive into the old location (for example, a new directory called "moodle").

====Linux====
mv moodle moodle.backup
tar xvzf moodle-1.1.tgz

Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one ('''check that optional/custom plugins are the correct version for your new Moodle first'''):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to

sudo chown www-data moodle/config.php

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')

if necessary.

where www-data is whatever user the Apache user is on your system. This is often 'apache' or 'www'.
You can find out by doing 'ls -l' in your /var/www/moodle folder (or wherever your moodle site is)
and then looking at the owner and group.

so you may see something like

ls -l
...lots of lines...
-rw-r--r-- 1 apache system 784 Jun 28 2007 config.php
...lots more lines...

so the owner is apache and the group is system.

To replicate this on your new system you can do 'chown apache:system config.php'

or to do a whole group do

chown apache:system ./*

and recursively

chown -R apache:system ./*

=== Using CVS ===

New sites should now use Git rather than CVS (see next section). If your site already uses CVS, to update, just go into the Moodle root directory and update to the new files:
<pre>
$ cd /path/to/your/moodle/
$ cvs update -dP
</pre>
To update from an older version type in the following:
<pre>
$ cd /path/to/your/moodle/
$ cvs -Q update -dP -r MOODLE_18_STABLE
</pre>
Make sure you use the "d" parameter to create new directories if necessary, and the "P" parameter to prune empty directories.

=== Using Git ===

You can use [[Git]] for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to GIt.

See [[Git for Administrators]] for further details.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

To do this just visit the [[Site administration block]] admin page (or ''<nowiki>http://example.com/moodle/admin</nowiki>'') and the "Notifications" link.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

:''TIP:'' Use the site administration block>Server>Maintenance mode to prevent users from changing data during the upgrade.
:''TIP:'' If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing. Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.

== Verify the upgrade (optional) ==

If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

==Upgrading more than one version==

Normally you can upgrade directly form any Moodle version to any later version. So, for example you could upgrade from 2.0 to 2.1, or from 1.9.

However, every so often, this general rule gets broken, because supporting really large jumps would be impossible. So far, the break points have been:
* You must have upgraded to version 1.9.x before you can upgrade to a later 2.x version.

==See also==

*[[Upgrading to Moodle 2.1]]
*[[Environment]]
*[[Git]] Version control and upgrading
*[[How to fix just one bug without upgrading]]
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).

Using Moodle.org forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=56915 Upgrading from 1.5.2 to 1.7]
*[http://moodle.org/mod/forum/discuss.php?d=56991 Upgrade nightmares.... any help appreciated]
*[http://moodle.org/mod/forum/discuss.php?d=62463 After upgrading i get "Your site may not be secure." msg]
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[nl:Upgraden]]
[[zh:升级]]
[[pl:Aktualizacja]]
[[de:Aktualisierung von Moodle]]
[[ru:Обновление]]

Installation FAQ

2012-01-01T19:19:23Z

Howardsmiller: /* How do I install Moodle on Windows Vista? */

{{Installing Moodle}}
== System information needed for Installation problems forum ==
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:
* Server Operating System name (version also if possible):
* PHP version (e.g. PHP 5.3.2)
* Database server type and version (e.g. MySQL 5.5.18)
* Browser and version (e.g. Internet Explorer 8):
* Moodle version (e.g. 2.1):
* Moodle install type? (New/Upgrade):
* Moodle config.php attached (please remove passwords):
* Phpinfo attached?:

Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!

[[#top|Top]]

==PHP - is it installed and what version do I have?==

Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:

<code php>
<?PHP phpinfo() ?>
</code>

If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.

[[#top|Top]]

==What & where are Moodle's configuration settings stored?==
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs.
[[#top|Top]]

==Downloading previous releases of Moodle==
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below).

{| style="width:75%; height:75px" border="0"
|-
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions]
|-
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions]
|-
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] ||
|}

You can download previous releases by using wget, lynx or curl with this URL:
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>.
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki>
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac pacakges], use either of these URLs (depending on whether you need the Intel or PPC package):
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki>
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki>
* '''Using CVS''': You can also use CVS to download older releases and incremental releases of the Moodle generic packages, e.g. Moodle 1.5.4 - see the [[CVS_for_Administrators | CVS documentation]].

[[#top|Top]]

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[PHP error logs]].

==Email copies are not being sent from my forums==

You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on. Please refer to the [[Cron|cron instructions]].

Tips:
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.
* Check your firewall or ask your network administrator. Many mail servers are heavily locked down and you may need permission to send mail through them.

[[#top|Top]]

==I can't log in - I just stay stuck on the login screen==

This may also apply if you are seeing “Your session has timed out. Please login again” and cannot log in.

The following are possible causes and actions you can take (in no particular order):

* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
* Sessions may not be configured properly on the server. You can test this by calling the script <nowiki>http://yourserver/moodle/lib/session-test.php</nowiki>.
* If your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)
* Try deleting cookies on your computer and/or try another browser or another client computer
* In Site Administration > Server > Session handling, try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser.
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This feature was optional since Moodle 1.6 but has been applied by default since 1.9.7. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
* You are using the correct username and password, yes?

If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it see [[Administration FAQ]]

[[#top|Top]]

==I log in but the login link doesn't change. I am logged in and can navigate freely.==

Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.

[[#top|Top]]
==Uploaded files give "File not found"==

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.

Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory (see [[Installing Moodle]] for more details):

'''AcceptPathInfo''' on

Note, this will ONLY work for Apache versions 2.x.

For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx.

IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.

Once you've got URL rewriting working the recommended rewriting rule is:

'''RewriteRule''' ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]

In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.

If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.

To use this alternative method, you should change the ''slasharguments'' variable. For moodle versions < 1.7, this is located in the Operating System section of ''Administration > Configuration > [[admin/config|Variables]]''. In later versions, this option is located in ''Site Administration > Server > HTTP''. You should now be able to access your uploaded files.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=145422 Troubleshooting Guide - 404 Errors] forum discussion.

[[#top|Top]]

==Why are all my pages blank?==

Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)

<code php>
$CFG->dirroot = "/var/www/moodle";
</code>

Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].

To determine if database support is your problem, insert this as the second line in your ''config.php'' file

<code php>
phpinfo();
</code>

then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.

[[#top|Top]]

== Why is a particular page blank or incomplete? ==

*'''Check your web server log files!!'''
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.

*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".

*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.

*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion

==Installation hangs when setting-up database tables==
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.

See [[Unexpected installation halts]] for more about solutions that involve:
*Checking for MySQL limits
*Checking the .htaccess files
*Code customizations issues
*Checking memory limit
*Upgrade incrementally
*Fix fopen function

[[#top|Top]]

==Why can't I upload a new image into my profile?==

If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
*The permissions associated with the role you are using are preventing you from changing your profile picture.
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > [[PHP info]]'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.

If Moodle thinks GD is not installed, then you will need to '''install the GD library'''.
*On Unix you may need to re-compile PHP with arguments something like this:

./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars
--enable-versioning --with-zlib

* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
extension=php_gd2.dll

:Windows users should see the [[Installing AMP|installation instructions]] for further help.

3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.

'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.

== Why doesn't my Moodle site display the time and date correctly? ==

Each language requires a specific language code (called a '''locale''' code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.

You can find the correct locale codes for Windows on these two pages: [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_language_strings.asp Language codes] and [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_country_strings.asp Country/region] codes (e.g. "esp_esp" for spanish)

These new locale codes can be entered on the Administration >> Configuration >> [[admin/config|Variables]] page, where they override the ones in the currently chosen language pack.
[[#top|Top]]
== How do I uninstall Moodle?==

'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
<pre>sql>DROP DATABASE moodle;</pre>
:In the above example replace 'moodle' with the name of the moodle database you created when installing.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:
*Open cmd.exe and navigate to this directory within your installation directory:
<pre>server/mysql/bin</pre>
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre>
*Enter your database password at the prompt (the default is "" [blank]).
*Enter "y" to confirm the database drop.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

==Migrating Moodle to a new site or server==
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.

[[#top|Top]]
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].

[[#top|Top]]
==Maximum upload file size - how to change it?==
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].

If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server.

For more help see:
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]
*[[Installing_Moodle#Recheck_PHP_settings]]
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]
*[[Site_policies#Maximum_uploaded_file_size]]
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650

[[#top|Top]]

==Moodle claims PHP float handling is not compatible==

The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".

[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.

You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.

Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
ini_set('precision', 14);
to your config.php file, and report your success in MDL-18253.

==When upgrading Moodle claims my database is not UTF8 when I'm sure it is==

The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade.

The database may not have it's character encoding set quite correctly. You can safely try this command on the database (mySQL):

ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it.

Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use [[phpMyAdmin]] to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199).

If your Moodle site is version 1.5 or older then it's telling the truth.

[[#top|Top]]

== How do I run multiple instances of Moodle without duplicating base code? ==

See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].

== What is FreeTDS and how can I use it in my installation? ==
[[FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.

== How do I install a plugin? ==

Please see [[Installing contributed modules or plugins]].

== See also ==

* [[Installing Moodle]]
* [[Upgrading FAQ]]
* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]

[[Category:FAQ]]

[[es:FAQ Instalación]]
[[fr:FAQ d'installation]]
[[nl:Installatie FAQ]]
[[ja:インストールFAQ]]
[[ru:FAQ по установке]]
[[pl:Instalacja FAQ]]
[[de:Installation FAQ]]

Installation FAQ

2012-01-01T19:15:55Z

Howardsmiller: /* Email copies are not being sent from my forums */

{{Installing Moodle}}
== System information needed for Installation problems forum ==
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:
* Server Operating System name (version also if possible):
* PHP version (e.g. PHP 5.3.2)
* Database server type and version (e.g. MySQL 5.5.18)
* Browser and version (e.g. Internet Explorer 8):
* Moodle version (e.g. 2.1):
* Moodle install type? (New/Upgrade):
* Moodle config.php attached (please remove passwords):
* Phpinfo attached?:

Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!

[[#top|Top]]

==PHP - is it installed and what version do I have?==

Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:

<code php>
<?PHP phpinfo() ?>
</code>

If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.

[[#top|Top]]

==What & where are Moodle's configuration settings stored?==
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs.
[[#top|Top]]

==Downloading previous releases of Moodle==
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below).

{| style="width:75%; height:75px" border="0"
|-
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions]
|-
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions]
|-
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] ||
|}

You can download previous releases by using wget, lynx or curl with this URL:
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>.
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki>
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac pacakges], use either of these URLs (depending on whether you need the Intel or PPC package):
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki>
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki>
* '''Using CVS''': You can also use CVS to download older releases and incremental releases of the Moodle generic packages, e.g. Moodle 1.5.4 - see the [[CVS_for_Administrators | CVS documentation]].

[[#top|Top]]

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[PHP error logs]].

==Email copies are not being sent from my forums==

You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on. Please refer to the [[Cron|cron instructions]].

Tips:
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.
* Check your firewall or ask your network administrator. Many mail servers are heavily locked down and you may need permission to send mail through them.

[[#top|Top]]

==I can't log in - I just stay stuck on the login screen==

This may also apply if you are seeing “Your session has timed out. Please login again” and cannot log in.

The following are possible causes and actions you can take (in no particular order):

* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
* Sessions may not be configured properly on the server. You can test this by calling the script <nowiki>http://yourserver/moodle/lib/session-test.php</nowiki>.
* If your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)
* Try deleting cookies on your computer and/or try another browser or another client computer
* In Site Administration > Server > Session handling, try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser.
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This feature was optional since Moodle 1.6 but has been applied by default since 1.9.7. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
* You are using the correct username and password, yes?

If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it see [[Administration FAQ]]

[[#top|Top]]

==I log in but the login link doesn't change. I am logged in and can navigate freely.==

Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.

[[#top|Top]]
==Uploaded files give "File not found"==

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.

Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory (see [[Installing Moodle]] for more details):

'''AcceptPathInfo''' on

Note, this will ONLY work for Apache versions 2.x.

For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx.

IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.

Once you've got URL rewriting working the recommended rewriting rule is:

'''RewriteRule''' ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]

In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.

If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.

To use this alternative method, you should change the ''slasharguments'' variable. For moodle versions < 1.7, this is located in the Operating System section of ''Administration > Configuration > [[admin/config|Variables]]''. In later versions, this option is located in ''Site Administration > Server > HTTP''. You should now be able to access your uploaded files.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=145422 Troubleshooting Guide - 404 Errors] forum discussion.

[[#top|Top]]

==Why are all my pages blank?==

Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)

<code php>
$CFG->dirroot = "/var/www/moodle";
</code>

Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].

To determine if database support is your problem, insert this as the second line in your ''config.php'' file

<code php>
phpinfo();
</code>

then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.

[[#top|Top]]

== Why is a particular page blank or incomplete? ==

*'''Check your web server log files!!'''
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.

*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".

*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.

*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion

==Installation hangs when setting-up database tables==
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.

See [[Unexpected installation halts]] for more about solutions that involve:
*Checking for MySQL limits
*Checking the .htaccess files
*Code customizations issues
*Checking memory limit
*Upgrade incrementally
*Fix fopen function

[[#top|Top]]

==Why can't I upload a new image into my profile?==

If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
*The permissions associated with the role you are using are preventing you from changing your profile picture.
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > [[PHP info]]'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.

If Moodle thinks GD is not installed, then you will need to '''install the GD library'''.
*On Unix you may need to re-compile PHP with arguments something like this:

./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars
--enable-versioning --with-zlib

* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
extension=php_gd2.dll

:Windows users should see the [[Installing AMP|installation instructions]] for further help.

3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.

'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.

== Why doesn't my Moodle site display the time and date correctly? ==

Each language requires a specific language code (called a '''locale''' code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.

You can find the correct locale codes for Windows on these two pages: [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_language_strings.asp Language codes] and [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_country_strings.asp Country/region] codes (e.g. "esp_esp" for spanish)

These new locale codes can be entered on the Administration >> Configuration >> [[admin/config|Variables]] page, where they override the ones in the currently chosen language pack.
[[#top|Top]]
== How do I uninstall Moodle?==

'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
<pre>sql>DROP DATABASE moodle;</pre>
:In the above example replace 'moodle' with the name of the moodle database you created when installing.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:
*Open cmd.exe and navigate to this directory within your installation directory:
<pre>server/mysql/bin</pre>
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre>
*Enter your database password at the prompt (the default is "" [blank]).
*Enter "y" to confirm the database drop.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

==Migrating Moodle to a new site or server==
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.

[[#top|Top]]
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].

[[#top|Top]]
==Maximum upload file size - how to change it?==
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].

If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server.

For more help see:
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]
*[[Installing_Moodle#Recheck_PHP_settings]]
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]
*[[Site_policies#Maximum_uploaded_file_size]]
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650

[[#top|Top]]

==How do I install Moodle on Windows Vista?==

See [[Installing Moodle on Windows Vista]].

==Moodle claims PHP float handling is not compatible==

The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".

[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.

You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.

Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
ini_set('precision', 14);
to your config.php file, and report your success in MDL-18253.

==When upgrading Moodle claims my database is not UTF8 when I'm sure it is==

The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade.

The database may not have it's character encoding set quite correctly. You can safely try this command on the database (mySQL):

ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it.

Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use [[phpMyAdmin]] to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199).

If your Moodle site is version 1.5 or older then it's telling the truth.

[[#top|Top]]

== How do I run multiple instances of Moodle without duplicating base code? ==

See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].

== What is FreeTDS and how can I use it in my installation? ==
[[FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.

== How do I install a plugin? ==

Please see [[Installing contributed modules or plugins]].

== See also ==

* [[Installing Moodle]]
* [[Upgrading FAQ]]
* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]

[[Category:FAQ]]

[[es:FAQ Instalación]]
[[fr:FAQ d'installation]]
[[nl:Installatie FAQ]]
[[ja:インストールFAQ]]
[[ru:FAQ по установке]]
[[pl:Instalacja FAQ]]
[[de:Installation FAQ]]

Installation FAQ

2011-12-22T09:56:23Z

Howardsmiller: /* Why are all my pages blank? */

{{Installing Moodle}}
== System information needed for Installation problems forum ==
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:
* Server Operating System name (version also if possible):
* PHP version (e.g. PHP 5.3.2)
* Database server type and version (e.g. MySQL 5.5.18)
* Browser and version (e.g. Internet Explorer 8):
* Moodle version (e.g. 2.1):
* Moodle install type? (New/Upgrade):
* Moodle config.php attached (please remove passwords):
* Phpinfo attached?:

Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!

[[#top|Top]]

==PHP - is it installed and what version do I have?==

Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:

<code php>
<?PHP phpinfo() ?>
</code>

If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.

[[#top|Top]]

==What & where are Moodle's configuration settings stored?==
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs.
[[#top|Top]]

==Downloading previous releases of Moodle==
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below).

{| style="width:75%; height:75px" border="0"
|-
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions]
|-
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions]
|-
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] ||
|}

You can download previous releases by using wget, lynx or curl with this URL:
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>.
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki>
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac pacakges], use either of these URLs (depending on whether you need the Intel or PPC package):
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki>
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki>
* '''Using CVS''': You can also use CVS to download older releases and incremental releases of the Moodle generic packages, e.g. Moodle 1.5.4 - see the [[CVS_for_Administrators | CVS documentation]].

[[#top|Top]]

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[PHP error logs]].

==Email copies are not being sent from my forums==

You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on.

Basically, you need to set up a process to regularly call the script <code><nowiki>http://yoursite/admin/cron.php</nowiki></code>. Please refer to the [[Cron|cron instructions]].

Tips:
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.

[[#top|Top]]

==I can't log in - I just stay stuck on the login screen==

This may also apply if you are seeing “Your session has timed out. Please login again” and cannot log in.

The following are possible causes and actions you can take (in no particular order):

* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
* Sessions may not be configured properly on the server. You can test this by calling the script <nowiki>http://yourserver/moodle/lib/session-test.php</nowiki>.
* If your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)
* Try deleting cookies on your computer and/or try another browser or another client computer
* In Site Administration > Server > Session handling, try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser.
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This feature was optional since Moodle 1.6 but has been applied by default since 1.9.7. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
* You are using the correct username and password, yes?

If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it see [[Administration FAQ]]

[[#top|Top]]

==I log in but the login link doesn't change. I am logged in and can navigate freely.==

Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.

[[#top|Top]]
==Uploaded files give "File not found"==

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.

Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory (see [[Installing Moodle]] for more details):

'''AcceptPathInfo''' on

Note, this will ONLY work for Apache versions 2.x.

For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx.

IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.

Once you've got URL rewriting working the recommended rewriting rule is:

'''RewriteRule''' ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]

In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.

If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.

To use this alternative method, you should change the ''slasharguments'' variable. For moodle versions < 1.7, this is located in the Operating System section of ''Administration > Configuration > [[admin/config|Variables]]''. In later versions, this option is located in ''Site Administration > Server > HTTP''. You should now be able to access your uploaded files.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=145422 Troubleshooting Guide - 404 Errors] forum discussion.

[[#top|Top]]

==Why are all my pages blank?==

Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)

<code php>
$CFG->dirroot = "/var/www/moodle";
</code>

Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].

To determine if database support is your problem, insert this as the second line in your ''config.php'' file

<code php>
phpinfo();
</code>

then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.

[[#top|Top]]

== Why is a particular page blank or incomplete? ==

*'''Check your web server log files!!'''
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.

*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".

*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.

*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion

==Installation hangs when setting-up database tables==
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.

See [[Unexpected installation halts]] for more about solutions that involve:
*Checking for MySQL limits
*Checking the .htaccess files
*Code customizations issues
*Checking memory limit
*Upgrade incrementally
*Fix fopen function

[[#top|Top]]

==Why can't I upload a new image into my profile?==

If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
*The permissions associated with the role you are using are preventing you from changing your profile picture.
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > [[PHP info]]'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.

If Moodle thinks GD is not installed, then you will need to '''install the GD library'''.
*On Unix you may need to re-compile PHP with arguments something like this:

./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars
--enable-versioning --with-zlib

* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
extension=php_gd2.dll

:Windows users should see the [[Installing AMP|installation instructions]] for further help.

3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.

'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.

== Why doesn't my Moodle site display the time and date correctly? ==

Each language requires a specific language code (called a '''locale''' code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.

You can find the correct locale codes for Windows on these two pages: [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_language_strings.asp Language codes] and [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_country_strings.asp Country/region] codes (e.g. "esp_esp" for spanish)

These new locale codes can be entered on the Administration >> Configuration >> [[admin/config|Variables]] page, where they override the ones in the currently chosen language pack.
[[#top|Top]]
== How do I uninstall Moodle?==

'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
<pre>sql>DROP DATABASE moodle;</pre>
:In the above example replace 'moodle' with the name of the moodle database you created when installing.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:
*Open cmd.exe and navigate to this directory within your installation directory:
<pre>server/mysql/bin</pre>
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre>
*Enter your database password at the prompt (the default is "" [blank]).
*Enter "y" to confirm the database drop.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

==Migrating Moodle to a new site or server==
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.

[[#top|Top]]
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].

[[#top|Top]]
==Maximum upload file size - how to change it?==
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].

If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server.

For more help see:
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]
*[[Installing_Moodle#Recheck_PHP_settings]]
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]
*[[Site_policies#Maximum_uploaded_file_size]]
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650

[[#top|Top]]

==How do I install Moodle on Windows Vista?==

See [[Installing Moodle on Windows Vista]].

==Moodle claims PHP float handling is not compatible==

The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".

[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.

You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.

Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
ini_set('precision', 14);
to your config.php file, and report your success in MDL-18253.

==When upgrading Moodle claims my database is not UTF8 when I'm sure it is==

The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade.

The database may not have it's character encoding set quite correctly. You can safely try this command on the database (mySQL):

ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it.

Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use [[phpMyAdmin]] to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199).

If your Moodle site is version 1.5 or older then it's telling the truth.

[[#top|Top]]

== How do I run multiple instances of Moodle without duplicating base code? ==

See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].

== What is FreeTDS and how can I use it in my installation? ==
[[FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.

== How do I install a plugin? ==

Please see [[Installing contributed modules or plugins]].

== See also ==

* [[Installing Moodle]]
* [[Upgrading FAQ]]
* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]

[[Category:FAQ]]

[[es:FAQ Instalación]]
[[fr:FAQ d'installation]]
[[nl:Installatie FAQ]]
[[ja:インストールFAQ]]
[[ru:FAQ по установке]]
[[pl:Instalacja FAQ]]
[[de:Installation FAQ]]

MySQL

2011-12-19T10:42:48Z

Howardsmiller: /* See also */

{{Installing Moodle}}
MySQL is one of the supported databases that underpins a Moodle installation.

== Installing MySQL ==

* If you are running Linux your preference should be to install using your distributions package manager. This ensures you will get any available updates.
* There are installers available for most popular operating systems at http://www.mysql.com/downloads/mysql/.
* It is possible and reasonably straightforward to build mysql from source but it is not recommended (the pre-built binaries are supposedly better optimised).
* Make sure you set a password for the 'root' user (see http://dev.mysql.com/doc/refman/5.0/en/default-privileges.html).
* Consider installing and configuring my.cnf (the MySQL settings file) to suit your needs. The default configuration is usually very conservative in respect of memory usage versus performance.

== Creating Moodle database ==

These are the steps to create an empty Moodle database. Substitute your own database name, user name and password as appropriate.

The instructions assume that the web server and MySQL server are on the same machine. In this case the 'dbhost' is 'localhost'. If they are on different machines substitute the name of the web server for 'localhost' in the following instructions and the 'dbhost' setting will be the name of the database server.

=== Command line ===

* To create a database using the 'mysql' command line client, first log into MySQL
<pre>
$ mysql -u root -p
Enter password:
</pre>
(Enter the password you previously set - or been given - for the MySQL 'root' user). After some pre-amble this should take you to the ''mysql>'' prompt.
* Create a new database (called 'moodle' - substitute your own name if required)
<pre>
mysql> CREATE DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
</pre>
* Add a user/password with the minimum needed permissions:
<pre>
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
</pre>
...which creates a user called 'moodleuser' with a password 'yourpassword'. Make sure you invent a strong password and resist the temptation to 'GRANT ALL'.

=== phpMyAdmin ===

[http://www.phpmyadmin.net/ phpMyAdmin] is a web based administration tool for MySQL. If this is available you can use it to create a new database. Make sure that you select 'UTF8' as the default character set.

== See also ==

* [http://www.mysql.com/ The MySQL homepage]
* [http://moodle.org/mod/forum/view.php?id=45 Using Moodle databases forum]
* [http://en.wikipedia.org/wiki/MySQL Wikipedia article about ''MySQL'']
* [http://forums.mysql.com/read.php?24,92131,92131 List of articles on MySQL performance tuning]

[[Category:SQL databases]]

[[ja:MySQL]]
[[de:MySQL]]

MySQL

2011-12-19T10:40:32Z

Howardsmiller: /* Installing MySQL */

{{Installing Moodle}}
MySQL is one of the supported databases that underpins a Moodle installation.

== Installing MySQL ==

* If you are running Linux your preference should be to install using your distributions package manager. This ensures you will get any available updates.
* There are installers available for most popular operating systems at http://www.mysql.com/downloads/mysql/.
* It is possible and reasonably straightforward to build mysql from source but it is not recommended (the pre-built binaries are supposedly better optimised).
* Make sure you set a password for the 'root' user (see http://dev.mysql.com/doc/refman/5.0/en/default-privileges.html).
* Consider installing and configuring my.cnf (the MySQL settings file) to suit your needs. The default configuration is usually very conservative in respect of memory usage versus performance.

== Creating Moodle database ==

These are the steps to create an empty Moodle database. Substitute your own database name, user name and password as appropriate.

The instructions assume that the web server and MySQL server are on the same machine. In this case the 'dbhost' is 'localhost'. If they are on different machines substitute the name of the web server for 'localhost' in the following instructions and the 'dbhost' setting will be the name of the database server.

=== Command line ===

* To create a database using the 'mysql' command line client, first log into MySQL
<pre>
$ mysql -u root -p
Enter password:
</pre>
(Enter the password you previously set - or been given - for the MySQL 'root' user). After some pre-amble this should take you to the ''mysql>'' prompt.
* Create a new database (called 'moodle' - substitute your own name if required)
<pre>
mysql> CREATE DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
</pre>
* Add a user/password with the minimum needed permissions:
<pre>
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
</pre>
...which creates a user called 'moodleuser' with a password 'yourpassword'. Make sure you invent a strong password and resist the temptation to 'GRANT ALL'.

=== phpMyAdmin ===

[http://www.phpmyadmin.net/ phpMyAdmin] is a web based administration tool for MySQL. If this is available you can use it to create a new database. Make sure that you select 'UTF8' as the default character set.

== See also ==

* [http://www.mysql.com/ The MySQL homepage]
* [http://moodle.org/mod/forum/view.php?id=45 Using Moodle databases forum]
* [http://en.wikipedia.org/wiki/MySQL Wikipedia article about ''MySQL'']

[[Category:SQL databases]]

[[ja:MySQL]]
[[de:MySQL]]

MySQL

2011-12-19T10:38:48Z

Howardsmiller: /* Installing MySQL */

{{Installing Moodle}}
MySQL is one of the supported databases that underpins a Moodle installation.

== Installing MySQL ==

* If you are running Linux your preference should be to install using your distributions package manager. This ensures you will get any available updates.
* There are installers available for most popular operating systems at http://www.mysql.com/downloads/mysql/.
* It is possible and reasonably straightforward to build mysql from source but it is not recommended (the pre-built binaries are supposedly better optimised).
* Make sure you set a password for the 'root' user (see http://dev.mysql.com/doc/refman/5.0/en/default-privileges.html).

== Creating Moodle database ==

These are the steps to create an empty Moodle database. Substitute your own database name, user name and password as appropriate.

The instructions assume that the web server and MySQL server are on the same machine. In this case the 'dbhost' is 'localhost'. If they are on different machines substitute the name of the web server for 'localhost' in the following instructions and the 'dbhost' setting will be the name of the database server.

=== Command line ===

* To create a database using the 'mysql' command line client, first log into MySQL
<pre>
$ mysql -u root -p
Enter password:
</pre>
(Enter the password you previously set - or been given - for the MySQL 'root' user). After some pre-amble this should take you to the ''mysql>'' prompt.
* Create a new database (called 'moodle' - substitute your own name if required)
<pre>
mysql> CREATE DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
</pre>
* Add a user/password with the minimum needed permissions:
<pre>
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
</pre>
...which creates a user called 'moodleuser' with a password 'yourpassword'. Make sure you invent a strong password and resist the temptation to 'GRANT ALL'.

=== phpMyAdmin ===

[http://www.phpmyadmin.net/ phpMyAdmin] is a web based administration tool for MySQL. If this is available you can use it to create a new database. Make sure that you select 'UTF8' as the default character set.

== See also ==

* [http://www.mysql.com/ The MySQL homepage]
* [http://moodle.org/mod/forum/view.php?id=45 Using Moodle databases forum]
* [http://en.wikipedia.org/wiki/MySQL Wikipedia article about ''MySQL'']

[[Category:SQL databases]]

[[ja:MySQL]]
[[de:MySQL]]

MySQL

2011-12-19T10:37:10Z

Howardsmiller:

{{Installing Moodle}}
MySQL is one of the supported databases that underpins a Moodle installation.

== Installing MySQL ==

* If you are running Linux your preference should be to install using your distributions package manager. This ensures you will get any available updates.
* There are installers available for most popular operating systems at http://www.mysql.com/downloads/mysql/.
* It is possible and reasonably straightforward to build mysql from source but it is not recommended (the pre-built binaries are supposedly better optimised).
* Make sure you set a password for the 'root' user.

== Creating Moodle database ==

These are the steps to create an empty Moodle database. Substitute your own database name, user name and password as appropriate.

The instructions assume that the web server and MySQL server are on the same machine. In this case the 'dbhost' is 'localhost'. If they are on different machines substitute the name of the web server for 'localhost' in the following instructions and the 'dbhost' setting will be the name of the database server.

=== Command line ===

* To create a database using the 'mysql' command line client, first log into MySQL
<pre>
$ mysql -u root -p
Enter password:
</pre>
(Enter the password you previously set - or been given - for the MySQL 'root' user). After some pre-amble this should take you to the ''mysql>'' prompt.
* Create a new database (called 'moodle' - substitute your own name if required)
<pre>
mysql> CREATE DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
</pre>
* Add a user/password with the minimum needed permissions:
<pre>
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
</pre>
...which creates a user called 'moodleuser' with a password 'yourpassword'. Make sure you invent a strong password and resist the temptation to 'GRANT ALL'.

=== phpMyAdmin ===

[http://www.phpmyadmin.net/ phpMyAdmin] is a web based administration tool for MySQL. If this is available you can use it to create a new database. Make sure that you select 'UTF8' as the default character set.

== See also ==

* [http://www.mysql.com/ The MySQL homepage]
* [http://moodle.org/mod/forum/view.php?id=45 Using Moodle databases forum]
* [http://en.wikipedia.org/wiki/MySQL Wikipedia article about ''MySQL'']

[[Category:SQL databases]]

[[ja:MySQL]]
[[de:MySQL]]

CVS for Administrators

2011-12-07T11:25:30Z

Howardsmiller: /* See also */

{{Installing Moodle}}
{{Note|
Note that Moodle development now takes place using the [[Git]] version control system. You may find it better to read [[Git for Administrators]] than this page if you want to use Git. However, CVS is still the easiest way to do it on many servers, and we will continue providing CVS mirrors of the Moodle code for the foreseeable future.
}}

The [http://cvs.moodle.org/ CVS archive] contains all the source code for Moodle. You can use a CVS program to extract versions ranging from the most stable release to the most cutting-edge development version. CVS can be an extremely convenient way of maintaining a Moodle server.

[[Image:Cvstree.png|CVS tree]]

Developers may have selective write access to the Moodle CVS archive (see [[CVS for Developers]] for details about how to do this). However, most people only need read-only access, so they can just connect to one of the mirrors using '''anonymous CVS''' as described below. There can however currently be a delay of up to 1 hour between the time a developer commits changes to developer CVS and the time it becomes available on anonymous CVS.

==CVS Servers==

Please choose the closest CVS mirror server to you from this list:

{| border="1" cellpadding="4" cellspacing="0"
|'''Country'''
|'''Server'''
|'''Provided by'''
|-
|EU
|'''eu.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|ES
|'''es.cvs.moodle.org'''
|[http://www.mondragon.edu/ Mondragon Unibertsitatea] In case of trouble, contact [mailto:iarenuno@eteo.mondragon.edu iarenuno@eteo.mondragon.edu] or [mailto:iarenaza@escomposlinux.org iarenaza@escomposlinux.org]
|-
|UK
|'''uk.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|US
|'''us.cvs.moodle.org'''
|San Francisco State University, Academic Technology ([http://www.sfsu.edu/ SFSU]). In case of trouble, contact [mailto:ilearn@sfsu.edu iLearn support]
|-
|US
|'''us2.cvs.moodle.org'''
|[http://www.contractorsinstitute.com The Contractors Institute] pserver and viewvc. In case of trouble contact [mailto:cvs@contractorsinstitute.com network support].
|}

Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!

For up-to-date alerts about planned or unplanned outages on any of these servers subscribe to the [http://lists.moodle.org/info/outages Moodle Outage mailing list]. See [http://moodle.org/stats/network.php moodle.org/stats/network.php] for server availability.

(If you would like to contribute to the project by running a mirror, please see [[How to set up a CVS mirror]])

==Moodle versions and CVS branches==

CVS stores every version of Moodle there has ever been. Versions are organised into branches as in the diagram at the top of this page. There is one branch for each series of stable releases, so the 2.1.x releases all come from the MOODLE_21_STABLE branch.

Along that branch, each actual release is marked with a tag. For example the Moodle 2.1 release is tagged MOODLE_21, and the 2.0.6 release is MOODLE_206. The latest 2.1.x+ weekly build is always tagged MOODLE_21_WEEKLY.

If you want Moodle 1.9, check out MOODLE_19_WEEKLY.

The latest development version is what all the stable branches branch away from. It is sometimes called HEAD or TRUNK. Use with caution.

As explained below you when you do a CVS checkout, you choose which version you want.

==Installing and maintaining Moodle via CVS==

===From a Unix computer===

To connect and login for the first time to the CVS server, you can use this command (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):

cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login

There is no password - when asked for one, just hit Enter.

To checkout (download) the entire Moodle code for the first time, use this command to get the latest WEEKLY version (generally the latest, most bug free version):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P -r MOODLE_21_WEEKLY moodle

Or the latest development version - sometimes called HEAD - (not for production use):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P moodle

Or the modules in Contrib

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co contrib

Later, to update your local copy of Moodle to the current version in CVS you just need to go into your local Moodle directory and type:

cvs update -dP

To update your local copy of Moodle to a new version (e.g. from 2.0+ to 2.1), go into your local Moodle directory and type:

cvs update -dP -r MOODLE_21_STABLE

To update your local copy of Moodle to a version from a specific date (e.g. 4th February 2009), go into your local Moodle directory and type:

cvs -q update -dP -r MOODLE_21_STABLE -D "5 Dec 2011"

To update your local copy and to save the log of the process, use the following command instead the previous one:

cvs update -dP -r MOODLE_21_STABLE | tee upgrade.log

Then look at the upgrade.log, notably look for lines starting with "C" (conflict):

grep '^C' upgrade.log

Conflicts may appear in case you have manually modified your source files. You have to resolve conflicts before using the site. See [[CVS for Developers]] for more details.

===Changing the directory name===

By default, the CVS checkout creates a directory on your webserver called 'moodle'. If you want your Moodle installation in a different directory, you can change the name of the directory that it will checkout the files to, by typing the following. This would download the MOODLE_21_STABLE branch into a directory called "mydirectory" (-d mydirectory).

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d mydirectory''' -r MOODLE_21_STABLE moodle

Or the latest development version to a directory called 'moodle-dev':

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d moodle-dev''' moodle

You can also change the name of the directory after the files are downloaded, and before you go through the Moodle install process. If you change the name of the directory before install, it will not affect anything during the install or during a CVS update. If you change the name of the directory after an install, you will need to change the config.php to reflect the name change ([[Moodle_migration#Migrating_a_complete_Moodle_site|guidance here]]). It won't affect the CVS update though.

===Change directory owner===

Depending on your webserver setup, you may well need to change the owner of the directory to the webserver user. Follow this step if you get permissions error when you try to access the page. For apache:

chown -R www-data:www-data moodle

===From a Windows computer===

To get started with a fresh copy of Moodle, follow the following steps (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):[[Image:CVS moodle settings for tortoise CVS.jpg|thumb|Tortoise CVS Screen capture]]
[[Image:Ecran cvs.jpg|thumb|Tortoise CVS (real name) Screen capture]]
# Get TortoiseCVS from [http://www.tortoisecvs.org/ tortoisecvs.org] and install it, then reboot.
# Find or create a new folder somewhere where you want Moodle to be downloaded to.
# Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.
# Copy this text into the CVSROOT field: <code>:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle</code>
#* NOTE - replace "SERVER" with "eu", "es", "uk" or "us" depending on your location.
# Under the "Module" field, type "moodle" to get moodle. (Other options here include"contrib" to get the contrib directory of hacks and addons, or "mysql" to get the optional MySQL Admin module).
#* For the latest STABLE version, click on the "Revision" tab and then check the radio button labelled "Choose branch or tag". From the drop-down menu select MOODLE_21_STABLE.
#* If you don't see the very latest version in the long drop-down list under Branch or tag name, click the Update List button next to it and wait for the list to be updated.
#* For the latest UNSTABLE development version, the radio-button "Use HEAD branch" in the Revision tab should be checked.
# Press the button: "OK" and everything should be downloaded.

Later, to update your local copy of Moodle to the current version in CVS, just right-mouse-click the folder and choose "CVS Update".

Note that the enclosing moodle folder is self-contained - you can move it anywhere you like or even rename it.

'''NOTE.-''' Admins with a developer account on cvs.moodle.org can connect with their account name, see attached screen shot.

===From a Mac OS X computer===
You will find useful informations about CVS and Mac OS X in the documentation for the complete installation package Moodle4Mac and for the Mac OS X Server installation.

Please read [[Complete_Install_Packages_for_Mac_OS_X#How_To_Update_Your_Moodle4Mac | How to update your Moodle4Mac]] or [[Step_by_Step_Installation_on_a_Mac_OS_X_Server#How_to_install_and_update_Moodle_via_CVS | How to install and to update Moodle via CVS]]. It works fine with the Moodle CVS servers.

===Troubleshooting===

If you see something like this, make sure that there is not some firewall blocking the port (it's 2401):

$ cvs -d:pserver:anonymous@us.cvs.moodle.org:/cvsroot/moodle login
Logging in to :pserver:anonymous@us.cvs.moodle.org:2401/cvsroot/moodle
CVS password:
cvs [login aborted]: connect to us.cvs.moodle.org(130.212.64.111):2401 failed: Connection timed out

==Switching to a new CVS server==

If you were ''already'' using CVS and want to switch to a different server, you'll probably need to make a small change so that the control files in your working copy will point to the new mirrors.

===Switching to a new server on Unix===

Use a shell command like this to change existing installations to point to the new mirror (UK mirror used in this example):

'''find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@uk\.cvs\.moodle\.org/''''

It can be run from /home, say, to fix multiple sites at once.

===Switching to a new server with TortoiseCVS===

If you were ''already'' using Tortoise CVS on Windows it's tricky, because Tortoise doesn't have any interface for changing the server. http://www.tortoisecvs.org/faq.html#changecvsroot explains it. But basically,

1) Install WinCVS and launch it.
2) Navigate to and select your Moodle folder.
3) Choose 'Macros'->CVS->Change Root from the menu.
4) Accept (or change) the default for the 'old' server.
5) Type the new server name. OK!

It takes a few seconds to go through all of the '''cvs''' folders and update the '''root''' files.

By the way, if you don't want to install WinCVS, another way of doing this is to uninstall your TortoiseCVS client on Windows, then do a regedit to clean up all the tortoisecvs related entries (might not be necessary), then reinstall TortoiseCVS client again (a good reason to upgrade to the most recent version of TortoiseCVS!). I have tested this and it cleared up the original setting of the original anonymous CVS server setting.

==See also==

*[[Git for Administrators]]
*[[Development:CVS_for_developers|CVS for developers]]
*[[Development:Setting up Eclipse]] for step by step instructions for setting up the [http://www.eclipse.org/ Eclipse IDE] for Moodle development, which including how to do the necessary CVS operations
*[[Development:Setting up Netbeans]] step by step instructions for those who prefer the [http://netbeans.org/ NetBeans IDE]. NetBeans comes with integrated CVS support.
* [[Development:Tracking Moodle CVS with git]]
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=91891 CVS Updating of 3rd-Party Plug-ins in the Moodle folder itself]
*[http://moodle.org/mod/forum/discuss.php?d=108196 simple question for cvs]

[[de:CVS für Administratoren]]
[[fr:CVS pour administrateurs]]
[[ja:管理者用CVS]]
[[ru:CVS для администраторов]]

CVS for Administrators

2011-12-07T11:24:53Z

Howardsmiller: /* From a Windows computer */

{{Installing Moodle}}
{{Note|
Note that Moodle development now takes place using the [[Git]] version control system. You may find it better to read [[Git for Administrators]] than this page if you want to use Git. However, CVS is still the easiest way to do it on many servers, and we will continue providing CVS mirrors of the Moodle code for the foreseeable future.
}}

The [http://cvs.moodle.org/ CVS archive] contains all the source code for Moodle. You can use a CVS program to extract versions ranging from the most stable release to the most cutting-edge development version. CVS can be an extremely convenient way of maintaining a Moodle server.

[[Image:Cvstree.png|CVS tree]]

Developers may have selective write access to the Moodle CVS archive (see [[CVS for Developers]] for details about how to do this). However, most people only need read-only access, so they can just connect to one of the mirrors using '''anonymous CVS''' as described below. There can however currently be a delay of up to 1 hour between the time a developer commits changes to developer CVS and the time it becomes available on anonymous CVS.

==CVS Servers==

Please choose the closest CVS mirror server to you from this list:

{| border="1" cellpadding="4" cellspacing="0"
|'''Country'''
|'''Server'''
|'''Provided by'''
|-
|EU
|'''eu.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|ES
|'''es.cvs.moodle.org'''
|[http://www.mondragon.edu/ Mondragon Unibertsitatea] In case of trouble, contact [mailto:iarenuno@eteo.mondragon.edu iarenuno@eteo.mondragon.edu] or [mailto:iarenaza@escomposlinux.org iarenaza@escomposlinux.org]
|-
|UK
|'''uk.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|US
|'''us.cvs.moodle.org'''
|San Francisco State University, Academic Technology ([http://www.sfsu.edu/ SFSU]). In case of trouble, contact [mailto:ilearn@sfsu.edu iLearn support]
|-
|US
|'''us2.cvs.moodle.org'''
|[http://www.contractorsinstitute.com The Contractors Institute] pserver and viewvc. In case of trouble contact [mailto:cvs@contractorsinstitute.com network support].
|}

Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!

For up-to-date alerts about planned or unplanned outages on any of these servers subscribe to the [http://lists.moodle.org/info/outages Moodle Outage mailing list]. See [http://moodle.org/stats/network.php moodle.org/stats/network.php] for server availability.

(If you would like to contribute to the project by running a mirror, please see [[How to set up a CVS mirror]])

==Moodle versions and CVS branches==

CVS stores every version of Moodle there has ever been. Versions are organised into branches as in the diagram at the top of this page. There is one branch for each series of stable releases, so the 2.1.x releases all come from the MOODLE_21_STABLE branch.

Along that branch, each actual release is marked with a tag. For example the Moodle 2.1 release is tagged MOODLE_21, and the 2.0.6 release is MOODLE_206. The latest 2.1.x+ weekly build is always tagged MOODLE_21_WEEKLY.

If you want Moodle 1.9, check out MOODLE_19_WEEKLY.

The latest development version is what all the stable branches branch away from. It is sometimes called HEAD or TRUNK. Use with caution.

As explained below you when you do a CVS checkout, you choose which version you want.

==Installing and maintaining Moodle via CVS==

===From a Unix computer===

To connect and login for the first time to the CVS server, you can use this command (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):

cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login

There is no password - when asked for one, just hit Enter.

To checkout (download) the entire Moodle code for the first time, use this command to get the latest WEEKLY version (generally the latest, most bug free version):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P -r MOODLE_21_WEEKLY moodle

Or the latest development version - sometimes called HEAD - (not for production use):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P moodle

Or the modules in Contrib

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co contrib

Later, to update your local copy of Moodle to the current version in CVS you just need to go into your local Moodle directory and type:

cvs update -dP

To update your local copy of Moodle to a new version (e.g. from 2.0+ to 2.1), go into your local Moodle directory and type:

cvs update -dP -r MOODLE_21_STABLE

To update your local copy of Moodle to a version from a specific date (e.g. 4th February 2009), go into your local Moodle directory and type:

cvs -q update -dP -r MOODLE_21_STABLE -D "5 Dec 2011"

To update your local copy and to save the log of the process, use the following command instead the previous one:

cvs update -dP -r MOODLE_21_STABLE | tee upgrade.log

Then look at the upgrade.log, notably look for lines starting with "C" (conflict):

grep '^C' upgrade.log

Conflicts may appear in case you have manually modified your source files. You have to resolve conflicts before using the site. See [[CVS for Developers]] for more details.

===Changing the directory name===

By default, the CVS checkout creates a directory on your webserver called 'moodle'. If you want your Moodle installation in a different directory, you can change the name of the directory that it will checkout the files to, by typing the following. This would download the MOODLE_21_STABLE branch into a directory called "mydirectory" (-d mydirectory).

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d mydirectory''' -r MOODLE_21_STABLE moodle

Or the latest development version to a directory called 'moodle-dev':

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d moodle-dev''' moodle

You can also change the name of the directory after the files are downloaded, and before you go through the Moodle install process. If you change the name of the directory before install, it will not affect anything during the install or during a CVS update. If you change the name of the directory after an install, you will need to change the config.php to reflect the name change ([[Moodle_migration#Migrating_a_complete_Moodle_site|guidance here]]). It won't affect the CVS update though.

===Change directory owner===

Depending on your webserver setup, you may well need to change the owner of the directory to the webserver user. Follow this step if you get permissions error when you try to access the page. For apache:

chown -R www-data:www-data moodle

===From a Windows computer===

To get started with a fresh copy of Moodle, follow the following steps (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):[[Image:CVS moodle settings for tortoise CVS.jpg|thumb|Tortoise CVS Screen capture]]
[[Image:Ecran cvs.jpg|thumb|Tortoise CVS (real name) Screen capture]]
# Get TortoiseCVS from [http://www.tortoisecvs.org/ tortoisecvs.org] and install it, then reboot.
# Find or create a new folder somewhere where you want Moodle to be downloaded to.
# Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.
# Copy this text into the CVSROOT field: <code>:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle</code>
#* NOTE - replace "SERVER" with "eu", "es", "uk" or "us" depending on your location.
# Under the "Module" field, type "moodle" to get moodle. (Other options here include"contrib" to get the contrib directory of hacks and addons, or "mysql" to get the optional MySQL Admin module).
#* For the latest STABLE version, click on the "Revision" tab and then check the radio button labelled "Choose branch or tag". From the drop-down menu select MOODLE_21_STABLE.
#* If you don't see the very latest version in the long drop-down list under Branch or tag name, click the Update List button next to it and wait for the list to be updated.
#* For the latest UNSTABLE development version, the radio-button "Use HEAD branch" in the Revision tab should be checked.
# Press the button: "OK" and everything should be downloaded.

Later, to update your local copy of Moodle to the current version in CVS, just right-mouse-click the folder and choose "CVS Update".

Note that the enclosing moodle folder is self-contained - you can move it anywhere you like or even rename it.

'''NOTE.-''' Admins with a developer account on cvs.moodle.org can connect with their account name, see attached screen shot.

===From a Mac OS X computer===
You will find useful informations about CVS and Mac OS X in the documentation for the complete installation package Moodle4Mac and for the Mac OS X Server installation.

Please read [[Complete_Install_Packages_for_Mac_OS_X#How_To_Update_Your_Moodle4Mac | How to update your Moodle4Mac]] or [[Step_by_Step_Installation_on_a_Mac_OS_X_Server#How_to_install_and_update_Moodle_via_CVS | How to install and to update Moodle via CVS]]. It works fine with the Moodle CVS servers.

===Troubleshooting===

If you see something like this, make sure that there is not some firewall blocking the port (it's 2401):

$ cvs -d:pserver:anonymous@us.cvs.moodle.org:/cvsroot/moodle login
Logging in to :pserver:anonymous@us.cvs.moodle.org:2401/cvsroot/moodle
CVS password:
cvs [login aborted]: connect to us.cvs.moodle.org(130.212.64.111):2401 failed: Connection timed out

==Switching to a new CVS server==

If you were ''already'' using CVS and want to switch to a different server, you'll probably need to make a small change so that the control files in your working copy will point to the new mirrors.

===Switching to a new server on Unix===

Use a shell command like this to change existing installations to point to the new mirror (UK mirror used in this example):

'''find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@uk\.cvs\.moodle\.org/''''

It can be run from /home, say, to fix multiple sites at once.

===Switching to a new server with TortoiseCVS===

If you were ''already'' using Tortoise CVS on Windows it's tricky, because Tortoise doesn't have any interface for changing the server. http://www.tortoisecvs.org/faq.html#changecvsroot explains it. But basically,

1) Install WinCVS and launch it.
2) Navigate to and select your Moodle folder.
3) Choose 'Macros'->CVS->Change Root from the menu.
4) Accept (or change) the default for the 'old' server.
5) Type the new server name. OK!

It takes a few seconds to go through all of the '''cvs''' folders and update the '''root''' files.

By the way, if you don't want to install WinCVS, another way of doing this is to uninstall your TortoiseCVS client on Windows, then do a regedit to clean up all the tortoisecvs related entries (might not be necessary), then reinstall TortoiseCVS client again (a good reason to upgrade to the most recent version of TortoiseCVS!). I have tested this and it cleared up the original setting of the original anonymous CVS server setting.

==See also==

*[[Git for Administrators]]
*[[Talk:CVS for Administrators]]
*[[Development:CVS_for_developers|CVS for developers]]
*[[Development:Setting up Eclipse]] for step by step instructions for setting up the [http://www.eclipse.org/ Eclipse IDE] for Moodle development, which including how to do the necessary CVS operations
*[[Development:Setting up Netbeans]] step by step instructions for those who prefer the [http://netbeans.org/ NetBeans IDE]. NetBeans comes with integrated CVS support.
* [[Development:Tracking Moodle CVS with git]]
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=91891 CVS Updating of 3rd-Party Plug-ins in the Moodle folder itself]
*[http://moodle.org/mod/forum/discuss.php?d=108196 simple question for cvs]

[[de:CVS für Administratoren]]
[[fr:CVS pour administrateurs]]
[[ja:管理者用CVS]]
[[ru:CVS для администраторов]]

CVS for Administrators

2011-12-07T11:24:29Z

Howardsmiller: /* Changing the directory name */

{{Installing Moodle}}
{{Note|
Note that Moodle development now takes place using the [[Git]] version control system. You may find it better to read [[Git for Administrators]] than this page if you want to use Git. However, CVS is still the easiest way to do it on many servers, and we will continue providing CVS mirrors of the Moodle code for the foreseeable future.
}}

The [http://cvs.moodle.org/ CVS archive] contains all the source code for Moodle. You can use a CVS program to extract versions ranging from the most stable release to the most cutting-edge development version. CVS can be an extremely convenient way of maintaining a Moodle server.

[[Image:Cvstree.png|CVS tree]]

Developers may have selective write access to the Moodle CVS archive (see [[CVS for Developers]] for details about how to do this). However, most people only need read-only access, so they can just connect to one of the mirrors using '''anonymous CVS''' as described below. There can however currently be a delay of up to 1 hour between the time a developer commits changes to developer CVS and the time it becomes available on anonymous CVS.

==CVS Servers==

Please choose the closest CVS mirror server to you from this list:

{| border="1" cellpadding="4" cellspacing="0"
|'''Country'''
|'''Server'''
|'''Provided by'''
|-
|EU
|'''eu.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|ES
|'''es.cvs.moodle.org'''
|[http://www.mondragon.edu/ Mondragon Unibertsitatea] In case of trouble, contact [mailto:iarenuno@eteo.mondragon.edu iarenuno@eteo.mondragon.edu] or [mailto:iarenaza@escomposlinux.org iarenaza@escomposlinux.org]
|-
|UK
|'''uk.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|US
|'''us.cvs.moodle.org'''
|San Francisco State University, Academic Technology ([http://www.sfsu.edu/ SFSU]). In case of trouble, contact [mailto:ilearn@sfsu.edu iLearn support]
|-
|US
|'''us2.cvs.moodle.org'''
|[http://www.contractorsinstitute.com The Contractors Institute] pserver and viewvc. In case of trouble contact [mailto:cvs@contractorsinstitute.com network support].
|}

Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!

For up-to-date alerts about planned or unplanned outages on any of these servers subscribe to the [http://lists.moodle.org/info/outages Moodle Outage mailing list]. See [http://moodle.org/stats/network.php moodle.org/stats/network.php] for server availability.

(If you would like to contribute to the project by running a mirror, please see [[How to set up a CVS mirror]])

==Moodle versions and CVS branches==

CVS stores every version of Moodle there has ever been. Versions are organised into branches as in the diagram at the top of this page. There is one branch for each series of stable releases, so the 2.1.x releases all come from the MOODLE_21_STABLE branch.

Along that branch, each actual release is marked with a tag. For example the Moodle 2.1 release is tagged MOODLE_21, and the 2.0.6 release is MOODLE_206. The latest 2.1.x+ weekly build is always tagged MOODLE_21_WEEKLY.

If you want Moodle 1.9, check out MOODLE_19_WEEKLY.

The latest development version is what all the stable branches branch away from. It is sometimes called HEAD or TRUNK. Use with caution.

As explained below you when you do a CVS checkout, you choose which version you want.

==Installing and maintaining Moodle via CVS==

===From a Unix computer===

To connect and login for the first time to the CVS server, you can use this command (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):

cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login

There is no password - when asked for one, just hit Enter.

To checkout (download) the entire Moodle code for the first time, use this command to get the latest WEEKLY version (generally the latest, most bug free version):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P -r MOODLE_21_WEEKLY moodle

Or the latest development version - sometimes called HEAD - (not for production use):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P moodle

Or the modules in Contrib

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co contrib

Later, to update your local copy of Moodle to the current version in CVS you just need to go into your local Moodle directory and type:

cvs update -dP

To update your local copy of Moodle to a new version (e.g. from 2.0+ to 2.1), go into your local Moodle directory and type:

cvs update -dP -r MOODLE_21_STABLE

To update your local copy of Moodle to a version from a specific date (e.g. 4th February 2009), go into your local Moodle directory and type:

cvs -q update -dP -r MOODLE_21_STABLE -D "5 Dec 2011"

To update your local copy and to save the log of the process, use the following command instead the previous one:

cvs update -dP -r MOODLE_21_STABLE | tee upgrade.log

Then look at the upgrade.log, notably look for lines starting with "C" (conflict):

grep '^C' upgrade.log

Conflicts may appear in case you have manually modified your source files. You have to resolve conflicts before using the site. See [[CVS for Developers]] for more details.

===Changing the directory name===

By default, the CVS checkout creates a directory on your webserver called 'moodle'. If you want your Moodle installation in a different directory, you can change the name of the directory that it will checkout the files to, by typing the following. This would download the MOODLE_21_STABLE branch into a directory called "mydirectory" (-d mydirectory).

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d mydirectory''' -r MOODLE_21_STABLE moodle

Or the latest development version to a directory called 'moodle-dev':

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d moodle-dev''' moodle

You can also change the name of the directory after the files are downloaded, and before you go through the Moodle install process. If you change the name of the directory before install, it will not affect anything during the install or during a CVS update. If you change the name of the directory after an install, you will need to change the config.php to reflect the name change ([[Moodle_migration#Migrating_a_complete_Moodle_site|guidance here]]). It won't affect the CVS update though.

===Change directory owner===

Depending on your webserver setup, you may well need to change the owner of the directory to the webserver user. Follow this step if you get permissions error when you try to access the page. For apache:

chown -R www-data:www-data moodle

===From a Windows computer===

To get started with a fresh copy of Moodle, follow the following steps (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):[[Image:CVS moodle settings for tortoise CVS.jpg|thumb|Tortoise CVS Screen capture]]
[[Image:Ecran cvs.jpg|thumb|Tortoise CVS (real name) Screen capture]]
# Get TortoiseCVS from [http://www.tortoisecvs.org/ tortoisecvs.org] and install it, then reboot.
# Find or create a new folder somewhere where you want Moodle to be downloaded to.
# Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.
# Copy this text into the CVSROOT field: <code>:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle</code>
#* NOTE - replace "SERVER" with "eu", "es", "uk" or "us" depending on your location.
# Under the "Module" field, type "moodle" to get moodle. (Other options here include"contrib" to get the contrib directory of hacks and addons, or "mysql" to get the optional MySQL Admin module).
#* For the latest STABLE version, click on the "Revision" tab and then check the radio button labelled "Choose branch or tag". From the drop-down menu select MOODLE_18_STABLE.
#* If you don't see the very latest version in the long drop-down list under Branch or tag name, click the Update List button next to it and wait for the list to be updated.
#* For the latest UNSTABLE development version, the radio-button "Use HEAD branch" in the Revision tab should be checked.
# Press the button: "OK" and everything should be downloaded.

Later, to update your local copy of Moodle to the current version in CVS, just right-mouse-click the folder and choose "CVS Update".

Note that the enclosing moodle folder is self-contained - you can move it anywhere you like or even rename it.

'''NOTE.-''' Admins with a developer account on cvs.moodle.org can connect with their account name, see attached screen shot.

===From a Mac OS X computer===
You will find useful informations about CVS and Mac OS X in the documentation for the complete installation package Moodle4Mac and for the Mac OS X Server installation.

Please read [[Complete_Install_Packages_for_Mac_OS_X#How_To_Update_Your_Moodle4Mac | How to update your Moodle4Mac]] or [[Step_by_Step_Installation_on_a_Mac_OS_X_Server#How_to_install_and_update_Moodle_via_CVS | How to install and to update Moodle via CVS]]. It works fine with the Moodle CVS servers.

===Troubleshooting===

If you see something like this, make sure that there is not some firewall blocking the port (it's 2401):

$ cvs -d:pserver:anonymous@us.cvs.moodle.org:/cvsroot/moodle login
Logging in to :pserver:anonymous@us.cvs.moodle.org:2401/cvsroot/moodle
CVS password:
cvs [login aborted]: connect to us.cvs.moodle.org(130.212.64.111):2401 failed: Connection timed out

==Switching to a new CVS server==

If you were ''already'' using CVS and want to switch to a different server, you'll probably need to make a small change so that the control files in your working copy will point to the new mirrors.

===Switching to a new server on Unix===

Use a shell command like this to change existing installations to point to the new mirror (UK mirror used in this example):

'''find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@uk\.cvs\.moodle\.org/''''

It can be run from /home, say, to fix multiple sites at once.

===Switching to a new server with TortoiseCVS===

If you were ''already'' using Tortoise CVS on Windows it's tricky, because Tortoise doesn't have any interface for changing the server. http://www.tortoisecvs.org/faq.html#changecvsroot explains it. But basically,

1) Install WinCVS and launch it.
2) Navigate to and select your Moodle folder.
3) Choose 'Macros'->CVS->Change Root from the menu.
4) Accept (or change) the default for the 'old' server.
5) Type the new server name. OK!

It takes a few seconds to go through all of the '''cvs''' folders and update the '''root''' files.

By the way, if you don't want to install WinCVS, another way of doing this is to uninstall your TortoiseCVS client on Windows, then do a regedit to clean up all the tortoisecvs related entries (might not be necessary), then reinstall TortoiseCVS client again (a good reason to upgrade to the most recent version of TortoiseCVS!). I have tested this and it cleared up the original setting of the original anonymous CVS server setting.

==See also==

*[[Git for Administrators]]
*[[Talk:CVS for Administrators]]
*[[Development:CVS_for_developers|CVS for developers]]
*[[Development:Setting up Eclipse]] for step by step instructions for setting up the [http://www.eclipse.org/ Eclipse IDE] for Moodle development, which including how to do the necessary CVS operations
*[[Development:Setting up Netbeans]] step by step instructions for those who prefer the [http://netbeans.org/ NetBeans IDE]. NetBeans comes with integrated CVS support.
* [[Development:Tracking Moodle CVS with git]]
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=91891 CVS Updating of 3rd-Party Plug-ins in the Moodle folder itself]
*[http://moodle.org/mod/forum/discuss.php?d=108196 simple question for cvs]

[[de:CVS für Administratoren]]
[[fr:CVS pour administrateurs]]
[[ja:管理者用CVS]]
[[ru:CVS для администраторов]]

CVS for Administrators

2011-12-07T11:23:37Z

Howardsmiller: /* From a Unix computer */

{{Installing Moodle}}
{{Note|
Note that Moodle development now takes place using the [[Git]] version control system. You may find it better to read [[Git for Administrators]] than this page if you want to use Git. However, CVS is still the easiest way to do it on many servers, and we will continue providing CVS mirrors of the Moodle code for the foreseeable future.
}}

The [http://cvs.moodle.org/ CVS archive] contains all the source code for Moodle. You can use a CVS program to extract versions ranging from the most stable release to the most cutting-edge development version. CVS can be an extremely convenient way of maintaining a Moodle server.

[[Image:Cvstree.png|CVS tree]]

Developers may have selective write access to the Moodle CVS archive (see [[CVS for Developers]] for details about how to do this). However, most people only need read-only access, so they can just connect to one of the mirrors using '''anonymous CVS''' as described below. There can however currently be a delay of up to 1 hour between the time a developer commits changes to developer CVS and the time it becomes available on anonymous CVS.

==CVS Servers==

Please choose the closest CVS mirror server to you from this list:

{| border="1" cellpadding="4" cellspacing="0"
|'''Country'''
|'''Server'''
|'''Provided by'''
|-
|EU
|'''eu.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|ES
|'''es.cvs.moodle.org'''
|[http://www.mondragon.edu/ Mondragon Unibertsitatea] In case of trouble, contact [mailto:iarenuno@eteo.mondragon.edu iarenuno@eteo.mondragon.edu] or [mailto:iarenaza@escomposlinux.org iarenaza@escomposlinux.org]
|-
|UK
|'''uk.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|US
|'''us.cvs.moodle.org'''
|San Francisco State University, Academic Technology ([http://www.sfsu.edu/ SFSU]). In case of trouble, contact [mailto:ilearn@sfsu.edu iLearn support]
|-
|US
|'''us2.cvs.moodle.org'''
|[http://www.contractorsinstitute.com The Contractors Institute] pserver and viewvc. In case of trouble contact [mailto:cvs@contractorsinstitute.com network support].
|}

Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!

For up-to-date alerts about planned or unplanned outages on any of these servers subscribe to the [http://lists.moodle.org/info/outages Moodle Outage mailing list]. See [http://moodle.org/stats/network.php moodle.org/stats/network.php] for server availability.

(If you would like to contribute to the project by running a mirror, please see [[How to set up a CVS mirror]])

==Moodle versions and CVS branches==

CVS stores every version of Moodle there has ever been. Versions are organised into branches as in the diagram at the top of this page. There is one branch for each series of stable releases, so the 2.1.x releases all come from the MOODLE_21_STABLE branch.

Along that branch, each actual release is marked with a tag. For example the Moodle 2.1 release is tagged MOODLE_21, and the 2.0.6 release is MOODLE_206. The latest 2.1.x+ weekly build is always tagged MOODLE_21_WEEKLY.

If you want Moodle 1.9, check out MOODLE_19_WEEKLY.

The latest development version is what all the stable branches branch away from. It is sometimes called HEAD or TRUNK. Use with caution.

As explained below you when you do a CVS checkout, you choose which version you want.

==Installing and maintaining Moodle via CVS==

===From a Unix computer===

To connect and login for the first time to the CVS server, you can use this command (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):

cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login

There is no password - when asked for one, just hit Enter.

To checkout (download) the entire Moodle code for the first time, use this command to get the latest WEEKLY version (generally the latest, most bug free version):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P -r MOODLE_21_WEEKLY moodle

Or the latest development version - sometimes called HEAD - (not for production use):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P moodle

Or the modules in Contrib

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co contrib

Later, to update your local copy of Moodle to the current version in CVS you just need to go into your local Moodle directory and type:

cvs update -dP

To update your local copy of Moodle to a new version (e.g. from 2.0+ to 2.1), go into your local Moodle directory and type:

cvs update -dP -r MOODLE_21_STABLE

To update your local copy of Moodle to a version from a specific date (e.g. 4th February 2009), go into your local Moodle directory and type:

cvs -q update -dP -r MOODLE_21_STABLE -D "5 Dec 2011"

To update your local copy and to save the log of the process, use the following command instead the previous one:

cvs update -dP -r MOODLE_21_STABLE | tee upgrade.log

Then look at the upgrade.log, notably look for lines starting with "C" (conflict):

grep '^C' upgrade.log

Conflicts may appear in case you have manually modified your source files. You have to resolve conflicts before using the site. See [[CVS for Developers]] for more details.

===Changing the directory name===

By default, the CVS checkout creates a directory on your webserver called 'moodle'. If you want your Moodle installation in a different directory, you can change the name of the directory that it will checkout the files to, by typing the following. This would download the MOODLE_19_STABLE branch into a directory called "mydirectory" (-d mydirectory).

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d mydirectory''' -r MOODLE_19_STABLE moodle

Or the latest development version to a directory called 'moodle-dev':

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d moodle-dev''' moodle

You can also change the name of the directory after the files are downloaded, and before you go through the Moodle install process. If you change the name of the directory before install, it will not affect anything during the install or during a CVS update. If you change the name of the directory after an install, you will need to change the config.php to reflect the name change ([[Moodle_migration#Migrating_a_complete_Moodle_site|guidance here]]). It won't affect the CVS update though.

===Change directory owner===

Depending on your webserver setup, you may well need to change the owner of the directory to the webserver user. Follow this step if you get permissions error when you try to access the page. For apache:

chown -R www-data:www-data moodle

===From a Windows computer===

To get started with a fresh copy of Moodle, follow the following steps (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):[[Image:CVS moodle settings for tortoise CVS.jpg|thumb|Tortoise CVS Screen capture]]
[[Image:Ecran cvs.jpg|thumb|Tortoise CVS (real name) Screen capture]]
# Get TortoiseCVS from [http://www.tortoisecvs.org/ tortoisecvs.org] and install it, then reboot.
# Find or create a new folder somewhere where you want Moodle to be downloaded to.
# Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.
# Copy this text into the CVSROOT field: <code>:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle</code>
#* NOTE - replace "SERVER" with "eu", "es", "uk" or "us" depending on your location.
# Under the "Module" field, type "moodle" to get moodle. (Other options here include"contrib" to get the contrib directory of hacks and addons, or "mysql" to get the optional MySQL Admin module).
#* For the latest STABLE version, click on the "Revision" tab and then check the radio button labelled "Choose branch or tag". From the drop-down menu select MOODLE_18_STABLE.
#* If you don't see the very latest version in the long drop-down list under Branch or tag name, click the Update List button next to it and wait for the list to be updated.
#* For the latest UNSTABLE development version, the radio-button "Use HEAD branch" in the Revision tab should be checked.
# Press the button: "OK" and everything should be downloaded.

Later, to update your local copy of Moodle to the current version in CVS, just right-mouse-click the folder and choose "CVS Update".

Note that the enclosing moodle folder is self-contained - you can move it anywhere you like or even rename it.

'''NOTE.-''' Admins with a developer account on cvs.moodle.org can connect with their account name, see attached screen shot.

===From a Mac OS X computer===
You will find useful informations about CVS and Mac OS X in the documentation for the complete installation package Moodle4Mac and for the Mac OS X Server installation.

Please read [[Complete_Install_Packages_for_Mac_OS_X#How_To_Update_Your_Moodle4Mac | How to update your Moodle4Mac]] or [[Step_by_Step_Installation_on_a_Mac_OS_X_Server#How_to_install_and_update_Moodle_via_CVS | How to install and to update Moodle via CVS]]. It works fine with the Moodle CVS servers.

===Troubleshooting===

If you see something like this, make sure that there is not some firewall blocking the port (it's 2401):

$ cvs -d:pserver:anonymous@us.cvs.moodle.org:/cvsroot/moodle login
Logging in to :pserver:anonymous@us.cvs.moodle.org:2401/cvsroot/moodle
CVS password:
cvs [login aborted]: connect to us.cvs.moodle.org(130.212.64.111):2401 failed: Connection timed out

==Switching to a new CVS server==

If you were ''already'' using CVS and want to switch to a different server, you'll probably need to make a small change so that the control files in your working copy will point to the new mirrors.

===Switching to a new server on Unix===

Use a shell command like this to change existing installations to point to the new mirror (UK mirror used in this example):

'''find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@uk\.cvs\.moodle\.org/''''

It can be run from /home, say, to fix multiple sites at once.

===Switching to a new server with TortoiseCVS===

If you were ''already'' using Tortoise CVS on Windows it's tricky, because Tortoise doesn't have any interface for changing the server. http://www.tortoisecvs.org/faq.html#changecvsroot explains it. But basically,

1) Install WinCVS and launch it.
2) Navigate to and select your Moodle folder.
3) Choose 'Macros'->CVS->Change Root from the menu.
4) Accept (or change) the default for the 'old' server.
5) Type the new server name. OK!

It takes a few seconds to go through all of the '''cvs''' folders and update the '''root''' files.

By the way, if you don't want to install WinCVS, another way of doing this is to uninstall your TortoiseCVS client on Windows, then do a regedit to clean up all the tortoisecvs related entries (might not be necessary), then reinstall TortoiseCVS client again (a good reason to upgrade to the most recent version of TortoiseCVS!). I have tested this and it cleared up the original setting of the original anonymous CVS server setting.

==See also==

*[[Git for Administrators]]
*[[Talk:CVS for Administrators]]
*[[Development:CVS_for_developers|CVS for developers]]
*[[Development:Setting up Eclipse]] for step by step instructions for setting up the [http://www.eclipse.org/ Eclipse IDE] for Moodle development, which including how to do the necessary CVS operations
*[[Development:Setting up Netbeans]] step by step instructions for those who prefer the [http://netbeans.org/ NetBeans IDE]. NetBeans comes with integrated CVS support.
* [[Development:Tracking Moodle CVS with git]]
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=91891 CVS Updating of 3rd-Party Plug-ins in the Moodle folder itself]
*[http://moodle.org/mod/forum/discuss.php?d=108196 simple question for cvs]

[[de:CVS für Administratoren]]
[[fr:CVS pour administrateurs]]
[[ja:管理者用CVS]]
[[ru:CVS для администраторов]]

CVS for Administrators

2011-12-07T11:21:35Z

Howardsmiller: /* Moodle versions and CVS branches */

{{Installing Moodle}}
{{Note|
Note that Moodle development now takes place using the [[Git]] version control system. You may find it better to read [[Git for Administrators]] than this page if you want to use Git. However, CVS is still the easiest way to do it on many servers, and we will continue providing CVS mirrors of the Moodle code for the foreseeable future.
}}

The [http://cvs.moodle.org/ CVS archive] contains all the source code for Moodle. You can use a CVS program to extract versions ranging from the most stable release to the most cutting-edge development version. CVS can be an extremely convenient way of maintaining a Moodle server.

[[Image:Cvstree.png|CVS tree]]

Developers may have selective write access to the Moodle CVS archive (see [[CVS for Developers]] for details about how to do this). However, most people only need read-only access, so they can just connect to one of the mirrors using '''anonymous CVS''' as described below. There can however currently be a delay of up to 1 hour between the time a developer commits changes to developer CVS and the time it becomes available on anonymous CVS.

==CVS Servers==

Please choose the closest CVS mirror server to you from this list:

{| border="1" cellpadding="4" cellspacing="0"
|'''Country'''
|'''Server'''
|'''Provided by'''
|-
|EU
|'''eu.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|ES
|'''es.cvs.moodle.org'''
|[http://www.mondragon.edu/ Mondragon Unibertsitatea] In case of trouble, contact [mailto:iarenuno@eteo.mondragon.edu iarenuno@eteo.mondragon.edu] or [mailto:iarenaza@escomposlinux.org iarenaza@escomposlinux.org]
|-
|UK
|'''uk.cvs.moodle.org'''
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]
|-
|US
|'''us.cvs.moodle.org'''
|San Francisco State University, Academic Technology ([http://www.sfsu.edu/ SFSU]). In case of trouble, contact [mailto:ilearn@sfsu.edu iLearn support]
|-
|US
|'''us2.cvs.moodle.org'''
|[http://www.contractorsinstitute.com The Contractors Institute] pserver and viewvc. In case of trouble contact [mailto:cvs@contractorsinstitute.com network support].
|}

Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!

For up-to-date alerts about planned or unplanned outages on any of these servers subscribe to the [http://lists.moodle.org/info/outages Moodle Outage mailing list]. See [http://moodle.org/stats/network.php moodle.org/stats/network.php] for server availability.

(If you would like to contribute to the project by running a mirror, please see [[How to set up a CVS mirror]])

==Moodle versions and CVS branches==

CVS stores every version of Moodle there has ever been. Versions are organised into branches as in the diagram at the top of this page. There is one branch for each series of stable releases, so the 2.1.x releases all come from the MOODLE_21_STABLE branch.

Along that branch, each actual release is marked with a tag. For example the Moodle 2.1 release is tagged MOODLE_21, and the 2.0.6 release is MOODLE_206. The latest 2.1.x+ weekly build is always tagged MOODLE_21_WEEKLY.

If you want Moodle 1.9, check out MOODLE_19_WEEKLY.

The latest development version is what all the stable branches branch away from. It is sometimes called HEAD or TRUNK. Use with caution.

As explained below you when you do a CVS checkout, you choose which version you want.

==Installing and maintaining Moodle via CVS==

===From a Unix computer===

To connect and login for the first time to the CVS server, you can use this command (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):

cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login

There is no password - when asked for one, just hit Enter.

To checkout (download) the entire Moodle code for the first time, use this command to get the latest WEEKLY version (generally the latest, most bug free version):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P -r MOODLE_19_WEEKLY moodle

Or the latest development version - sometimes called HEAD - (not for production use):

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P moodle

Or the modules in Contrib

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co contrib

Later, to update your local copy of Moodle to the current version in CVS you just need to go into your local Moodle directory and type:

cvs update -dP

To update your local copy of Moodle to a new version (e.g. from 1.8+ to 1.9), go into your local Moodle directory and type:

cvs update -dP -r MOODLE_19_STABLE

To update your local copy of Moodle to a version from a specific date (e.g. 4th February 2009), go into your local Moodle directory and type:

cvs -q update -dP -r MOODLE_19_STABLE -D "4 Feb 2009"

To update your local copy and to save the log of the process, use the following command instead the previous one:

cvs update -dP -r MOODLE_19_STABLE | tee upgrade.log

Then look at the upgrade.log, notably look for lines starting with "C" (conflict):

grep '^C' upgrade.log

Conflicts may appear in case you have manually modified your source files. You have to resolve conflicts before using the site. See [[CVS for Developers]] for more details.

===Changing the directory name===

By default, the CVS checkout creates a directory on your webserver called 'moodle'. If you want your Moodle installation in a different directory, you can change the name of the directory that it will checkout the files to, by typing the following. This would download the MOODLE_19_STABLE branch into a directory called "mydirectory" (-d mydirectory).

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d mydirectory''' -r MOODLE_19_STABLE moodle

Or the latest development version to a directory called 'moodle-dev':

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d moodle-dev''' moodle

You can also change the name of the directory after the files are downloaded, and before you go through the Moodle install process. If you change the name of the directory before install, it will not affect anything during the install or during a CVS update. If you change the name of the directory after an install, you will need to change the config.php to reflect the name change ([[Moodle_migration#Migrating_a_complete_Moodle_site|guidance here]]). It won't affect the CVS update though.

===Change directory owner===

Depending on your webserver setup, you may well need to change the owner of the directory to the webserver user. Follow this step if you get permissions error when you try to access the page. For apache:

chown -R www-data:www-data moodle

===From a Windows computer===

To get started with a fresh copy of Moodle, follow the following steps (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):[[Image:CVS moodle settings for tortoise CVS.jpg|thumb|Tortoise CVS Screen capture]]
[[Image:Ecran cvs.jpg|thumb|Tortoise CVS (real name) Screen capture]]
# Get TortoiseCVS from [http://www.tortoisecvs.org/ tortoisecvs.org] and install it, then reboot.
# Find or create a new folder somewhere where you want Moodle to be downloaded to.
# Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.
# Copy this text into the CVSROOT field: <code>:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle</code>
#* NOTE - replace "SERVER" with "eu", "es", "uk" or "us" depending on your location.
# Under the "Module" field, type "moodle" to get moodle. (Other options here include"contrib" to get the contrib directory of hacks and addons, or "mysql" to get the optional MySQL Admin module).
#* For the latest STABLE version, click on the "Revision" tab and then check the radio button labelled "Choose branch or tag". From the drop-down menu select MOODLE_18_STABLE.
#* If you don't see the very latest version in the long drop-down list under Branch or tag name, click the Update List button next to it and wait for the list to be updated.
#* For the latest UNSTABLE development version, the radio-button "Use HEAD branch" in the Revision tab should be checked.
# Press the button: "OK" and everything should be downloaded.

Later, to update your local copy of Moodle to the current version in CVS, just right-mouse-click the folder and choose "CVS Update".

Note that the enclosing moodle folder is self-contained - you can move it anywhere you like or even rename it.

'''NOTE.-''' Admins with a developer account on cvs.moodle.org can connect with their account name, see attached screen shot.

===From a Mac OS X computer===
You will find useful informations about CVS and Mac OS X in the documentation for the complete installation package Moodle4Mac and for the Mac OS X Server installation.

Please read [[Complete_Install_Packages_for_Mac_OS_X#How_To_Update_Your_Moodle4Mac | How to update your Moodle4Mac]] or [[Step_by_Step_Installation_on_a_Mac_OS_X_Server#How_to_install_and_update_Moodle_via_CVS | How to install and to update Moodle via CVS]]. It works fine with the Moodle CVS servers.

===Troubleshooting===

If you see something like this, make sure that there is not some firewall blocking the port (it's 2401):

$ cvs -d:pserver:anonymous@us.cvs.moodle.org:/cvsroot/moodle login
Logging in to :pserver:anonymous@us.cvs.moodle.org:2401/cvsroot/moodle
CVS password:
cvs [login aborted]: connect to us.cvs.moodle.org(130.212.64.111):2401 failed: Connection timed out

==Switching to a new CVS server==

If you were ''already'' using CVS and want to switch to a different server, you'll probably need to make a small change so that the control files in your working copy will point to the new mirrors.

===Switching to a new server on Unix===

Use a shell command like this to change existing installations to point to the new mirror (UK mirror used in this example):

'''find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@uk\.cvs\.moodle\.org/''''

It can be run from /home, say, to fix multiple sites at once.

===Switching to a new server with TortoiseCVS===

If you were ''already'' using Tortoise CVS on Windows it's tricky, because Tortoise doesn't have any interface for changing the server. http://www.tortoisecvs.org/faq.html#changecvsroot explains it. But basically,

1) Install WinCVS and launch it.
2) Navigate to and select your Moodle folder.
3) Choose 'Macros'->CVS->Change Root from the menu.
4) Accept (or change) the default for the 'old' server.
5) Type the new server name. OK!

It takes a few seconds to go through all of the '''cvs''' folders and update the '''root''' files.

By the way, if you don't want to install WinCVS, another way of doing this is to uninstall your TortoiseCVS client on Windows, then do a regedit to clean up all the tortoisecvs related entries (might not be necessary), then reinstall TortoiseCVS client again (a good reason to upgrade to the most recent version of TortoiseCVS!). I have tested this and it cleared up the original setting of the original anonymous CVS server setting.

==See also==

*[[Git for Administrators]]
*[[Talk:CVS for Administrators]]
*[[Development:CVS_for_developers|CVS for developers]]
*[[Development:Setting up Eclipse]] for step by step instructions for setting up the [http://www.eclipse.org/ Eclipse IDE] for Moodle development, which including how to do the necessary CVS operations
*[[Development:Setting up Netbeans]] step by step instructions for those who prefer the [http://netbeans.org/ NetBeans IDE]. NetBeans comes with integrated CVS support.
* [[Development:Tracking Moodle CVS with git]]
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=91891 CVS Updating of 3rd-Party Plug-ins in the Moodle folder itself]
*[http://moodle.org/mod/forum/discuss.php?d=108196 simple question for cvs]

[[de:CVS für Administratoren]]
[[fr:CVS pour administrateurs]]
[[ja:管理者用CVS]]
[[ru:CVS для администраторов]]

Git for Administrators

2011-12-07T09:12:27Z

Howardsmiller: /* Obtaining the code from Git */

{{Installing Moodle}}
The recommended way (now all Moodle development has moved to this versioning system) is Git. This page describes how to maintain a copy of Moodle on your production server which can easily be upgraded using Git. If you have customisations of Moodle core code, you are advised to follow the instructions in the [[Development:Quick Git start guide for Moodle development|Quick Git start guide for Moodle development]].

To get the most of of Git it is worth making the effort to understand its basic concepts - see the See Also section below. It can be a bit of a learning curve, especially if you are used to CVS or Subversion.

== Getting hold of Git ==

Support for Git was, up until recently, mostly confined to Linux but builds are now available for most popular operating systems:
* List of downloads from Git site - http://git-scm.com/download

== Obtaining the code from Git ==

The command line version of Git is discussed here. Graphical clients are little more that wrappers around the command line version, so you should be able to deduce the correct parameters quite easily.

You can find the official Moodle git repository at git://git.moodle.org/moodle.git (with an official clone at git://github.com/moodle/moodle.git). To initialize your local checkout, use
<pre>
$ git clone git://git.moodle.org/moodle.git (1)
$ cd moodle
$ git branch -a (2)
$ git branch --track MOODLE_21_STABLE origin/MOODLE_21_STABLE (3)
$ git checkout MOODLE_21_STABLE (4)
</pre>
* The command (1) initializes the new local repository as a clone of the 'upstream' (i.e. the remote server based) moodle.git repository. The upstream repository is called 'origin' by default. It creates a new directory named ''moodle'', where it downloads all the files. This operation can take a while as it is actually getting the entire history of all Moodle versions
* The command (2) lists all available branches.
* Use the command (3) to create a new local branch called MOODLE_21_STABLE and set it to track the remote branch MOODLE_21_STABLE from the upstream repository.
* The command (4) actually switches to the newly created local branch.

Note that Git has a huge number of options for each command and it's actually possible to do the above process with a single command (left as an exercise!!).

==Git from behind a firewall==

Git uses a proprietary protocol and it may be blocked by your firewall (port 9418). If this is a problem, you can use Github's http version <nowiki>https://github.com/moodle/moodle.git</nowiki>. It's a bit slower, so use the Git protocol if you can.

== Updating your installation ==

The Moodle development team performs integration and testing of fixed bugs every Monday and Tuesday. On Wednesday you can install all patches by updating your code. Check the [http://git.moodle.org/gw?p=moodle.git;a=summary shortlog] to see if the official repository has been already updated or not.

To update your code to the latest version (on the MOODLE_21_STABLE branch) '''all''' you have to do is:
<pre>
$ cd /path/to/your/moodle/
$ git pull
</pre>
If this is a production site you should still consider the [[Upgrade]] instructions (e.g. take backups).

== Installing a contributed extension from its Git repository ==

This is one way to handle adding plugins from other Git repositories into your Moodle repository. Another way is to use Git Submodules. However, at the time of writing, this is one of Git's rougher features and should be regarded as an advanced option.

For example, let us say we want to install the [[Book module]] form its Git repository into our Moodle 2.1.
<pre>
$ cd /path/to/your/moodle/
$ cd mod (1)
$ git clone git://github.com/skodak/moodle-mod_book.git book (2)
$ cd book
$ git checkout -b MOODLE_21_STABLE origin/MOODLE_21_STABLE (3)
$ git branch -d master (4)
</pre>
The command (1) changes the current directory into the ''mod'' folder of your local Moodle clone. The command (2) creates a new subdirectory ''book'' and makes a local clone of Petr Škoda's vanilla Book repository. The command (3) creates a new local branch that will track the remote branch with a Book version for Moodle 2.1. The command (4) deletes the ''master'' that was created automatically by git-clone in (2) as we do not want it in this production checkout.

Now it is wise to put the new directory mod/book/ to the list of ignored files of the main Moodle clone, otherwise a status of the main clone will keep reminding you that the new code has not been checked in.
<pre>
$ cd /path/to/your/moodle/
$ echo /mod/book/ >> .git/info/exclude
</pre>
To update your Moodle installation now, you must visit both Git repositories and pull changes from upstream.
<pre>
$ cd /path/to/your/moodle/
$ git pull
$ cd mod/book
$ git pull
</pre>
Writing a shell script with these lines in the root of Moodle installation is a very good idea. Otherwise it is easy to forget what Git repositories are there within the main Moodle repository.

== See also ==

; Moodle Docs
* [[Git FAQ]]
* [[CVS for Administrators]]
* [[Moodle versions]]
* For some screenshots see [[User:Frank_Ralf/Git]] (still work in progress)

; Moodle forum discussions
* [http://moodle.org/mod/forum/discuss.php?d=168094 GIT help needed]
* [http://moodle.org/mod/forum/discuss.php?d=165236 Best way to manage CONTRIB code with GIT]
* [http://moodle.org/mod/forum/discuss.php?d=167063 Handy Git tip for tracking 3rd-party modules and plugins]
* [http://moodle.org/mod/forum/discuss.php?d=167730 Moodle Git repositories]
* [http://moodle.org/mod/forum/discuss.php?d=183693 Git and CVS]

; External resources
* [http://www.kernel.org/pub/software/scm/git/docs/everyday.html Everyday GIT With 20 Commands Or So]
* [http://gitref.org/ Git Reference]
* [http://progit.org/book/ Pro Git book]

[[Category:Git]]

[[ja:管理者用Git]]

Git for Administrators

2011-12-06T10:15:20Z

Howardsmiller: /* Installing a contributed extension from its Git repository */

{{Installing Moodle}}
The recommended way (now all Moodle development has moved to this versioning system) is Git. This page describes how to maintain a copy of Moodle on your production server which can easily be upgraded using Git. If you have customisations of Moodle core code, you are advised to follow the instructions in the [[Development:Quick Git start guide for Moodle development|Quick Git start guide for Moodle development]].

To get the most of of Git it is worth making the effort to understand its basic concepts - see the See Also section below. It can be a bit of a learning curve, especially if you are used to CVS or Subversion.

== Getting hold of Git ==

Support for Git was, up until recently, mostly confined to Linux but builds are now available for most popular operating systems:
* List of downloads from Git site - http://git-scm.com/download

== Obtaining the code from Git ==

The command line version of Git is discussed here. Graphical clients are little more that wrappers around the command line version, so you should be able to deduce the correct parameters quite easily.

You can find the official Moodle git repository at git://git.moodle.org/moodle.git (with an official clone at git://github.com/moodle/moodle.git). To initialize your local checkout, use
<pre>
$ git clone git://git.moodle.org/moodle.git (1)
$ cd moodle
$ git branch -a (2)
$ git branch --track MOODLE_21_STABLE origin/MOODLE_21_STABLE (3)
$ git checkout MOODLE_21_STABLE (4)
</pre>
* The command (1) initializes the new local repository as a clone of the 'upstream' (i.e. the remote server based) moodle.git repository. The upstream repository is called 'origin' by default. It creates a new directory named ''moodle'', where it downloads all the files. This operation can take a while as it is actually getting the entire history of all Moodle versions
* The command (2) lists all available branches.
* Use the command (3) to create a new local branch called MOODLE_21_STABLE and set it to track the remote branch MOODLE_21_STABLE from the upstream repository.
* The command (4) actually switches to the newly created local branch.

Note that Git has a huge number of options for each command and it's actually possible to do the above process with a single command (left as an exercise!!).

== Updating your installation ==

The Moodle development team performs integration and testing of fixed bugs every Monday and Tuesday. On Wednesday you can install all patches by updating your code. Check the [http://git.moodle.org/gw?p=moodle.git;a=summary shortlog] to see if the official repository has been already updated or not.

To update your code to the latest version (on the MOODLE_21_STABLE branch) '''all''' you have to do is:
<pre>
$ cd /path/to/your/moodle/
$ git pull
</pre>
If this is a production site you should still consider the [[Upgrade]] instructions (e.g. take backups).

== Installing a contributed extension from its Git repository ==

This is one way to handle adding plugins from other Git repositories into your Moodle repository. Another way is to use Git Submodules. However, at the time of writing, this is one of Git's rougher features and should be regarded as an advanced option.

For example, let us say we want to install the [[Book module]] form its Git repository into our Moodle 2.1.
<pre>
$ cd /path/to/your/moodle/
$ cd mod (1)
$ git clone git://github.com/skodak/moodle-mod_book.git book (2)
$ cd book
$ git checkout -b MOODLE_21_STABLE origin/MOODLE_21_STABLE (3)
$ git branch -d master (4)
</pre>
The command (1) changes the current directory into the ''mod'' folder of your local Moodle clone. The command (2) creates a new subdirectory ''book'' and makes a local clone of Petr Škoda's vanilla Book repository. The command (3) creates a new local branch that will track the remote branch with a Book version for Moodle 2.1. The command (4) deletes the ''master'' that was created automatically by git-clone in (2) as we do not want it in this production checkout.

Now it is wise to put the new directory mod/book/ to the list of ignored files of the main Moodle clone, otherwise a status of the main clone will keep reminding you that the new code has not been checked in.
<pre>
$ cd /path/to/your/moodle/
$ echo /mod/book/ >> .git/info/exclude
</pre>
To update your Moodle installation now, you must visit both Git repositories and pull changes from upstream.
<pre>
$ cd /path/to/your/moodle/
$ git pull
$ cd mod/book
$ git pull
</pre>
Writing a shell script with these lines in the root of Moodle installation is a very good idea. Otherwise it is easy to forget what Git repositories are there within the main Moodle repository.

== See also ==

; Moodle Docs
* [[Git FAQ]]
* [[CVS for Administrators]]
* [[Moodle versions]]
* For some screenshots see [[User:Frank_Ralf/Git]] (still work in progress)

; Moodle forum discussions
* [http://moodle.org/mod/forum/discuss.php?d=168094 GIT help needed]
* [http://moodle.org/mod/forum/discuss.php?d=165236 Best way to manage CONTRIB code with GIT]
* [http://moodle.org/mod/forum/discuss.php?d=167063 Handy Git tip for tracking 3rd-party modules and plugins]
* [http://moodle.org/mod/forum/discuss.php?d=167730 Moodle Git repositories]
* [http://moodle.org/mod/forum/discuss.php?d=183693 Git and CVS]

; External resources
* [http://www.kernel.org/pub/software/scm/git/docs/everyday.html Everyday GIT With 20 Commands Or So]
* [http://gitref.org/ Git Reference]
* [http://progit.org/book/ Pro Git book]

[[Category:Git]]

[[ja:管理者用Git]]