MoodleDocs - User contributions [en]

File upload size

2016-03-04T10:21:28Z

T100ss: /* Modifying the php.ini file */

{{Installing Moodle}}Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:

Server level
Moodle site level
Course level
Activity level

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

==Physical access to Server==
These instructions assume you have full physical and administrative access to your server. If you are using a hosted server then you will probably need to look into other ways to increase your file upload size.

There are positives and negatives to both methods below. If you modify the php.ini file then the changes will effect all php applications on your server. Since PHP5 you can only have one php.ini file on your server. The php.ini method will work with all web servers though. The .htaccess method will only effect the folder and all subfolders that it is placed in, but you must have certain settings enabled in Apache.

==Restricting the File size - how it works==
The Host may set a limit on the maximum file upload size in the Server environment, which you may override if the Host allows you to. PHP has a setting that it uses to limit the size of the file that it handles in upload. The Host has set that figure in the php.ini based on their particular perceptions and their clientele need. This size appears in Moodle in the '''Administration > Security > Site Policies > Maximum uploaded file size''' drop-down combo box. You can change this at any time to suit your site need. In the Course Settings page, there is also a further restriction that can be made. At no time can the Course setting over-ride the Site setting, nor can the Site setting over-ride the php.ini setting, which cannot over-ride the Server setting. The only exception to this rule is that you can manipulate both the Server and the PHP settings, and how to do that is described below.

==Modifying the php.ini file==
These instructions show you how to change the file upload size by editing your php.ini file.

For the most part these instructions amount to the following.
In the file /etc/php5/apache2/php.ini you need to change "post_max_size", "upload_max_filesize" and "max_execution_time" to values that suit your needs using whatever editor you are used to.

Below are some line by line instructions for various installations of Moodle.

====Ubuntu Linux Instructions====

These instructions assume that you have installed the standard Moodle package, PHP 5 and Apache 2 via apt-get and left it all as a default install. If you have compiled yourself I presume that you will know where your php.ini files are!

You need to edit the following three settings in your php.ini file located at: /etc/php5/apache2/
Here are a set of instructions to follow line by line.

*Type "sudo nano /etc/php5/apache2/php.ini"
*Press Ctrl and W and type "post_max_size"
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl and W and type "upload_max_filesize"
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl and W and type "max_execution_time"
*Change the value to 600
*Press Ctrl and O
*Press Ctrl and X
*Type sudo apachectl restart

[http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size NGINX] system administrators should also add client_max_body_size=XXX to the "http" section of their nginx main configuration file. ([https://rtcamp.com/tutorials/php/increase-file-upload-size-limit/#change-in-nginx-config see more info])

Your new file size limit should now appear in Administration > Security > Site Policies > Maximum uploaded file size

====XAMPP on Mac Instructions====

These are instructions for how to do this for Moodle on a Mac using the [http://download.moodle.org/macosx/ XAMPP sample download package available]. (This is not for a OS X production server.)

* Close down Apache and MySQL if they are running via the XAMPP Control app and close the XAMPP Control app
* Open Finder and go to Applications
* Navigate down and open the folder ''XAMPP'' / ''xamppfiles'' / ''etc''
* Open the file ''php.ini'' with TextEdit (or another plain text editor)
* Search for the ''post_max_size'' setting and up this from 128M (the default) to more; 500M is the maximum
* Do the same for ''upload_max_filesize'' (make the numbers the same)
* Search for the ''max_execution_time'' setting and up this to 300 (or more if you get timeouts on uploads)
* Save the php.ini file
* restart Apache and MySQL as usual

Note: You may get a "permission denied" error when saving the php.ini file unless you are logged in with admin access to your Mac. To work around this, you can set the ''/etc'' directory in which the php.ini file is located to be writable temporarily. For how to do that, see [http://answers.yahoo.com/question/index?qid=20090115235753AA4DtJ0 here] or [http://www.ehow.com/how_2314896_fix-permissions-mac-os-x.html here].

====Windows XP and Server 2003 Instructions====

These instructions presume that you have downloaded the latest PHP 5.3.x Windows zip package and extracted it to C:\PHP. If you have installed PHP to another location then change all references to "C:\PHP" to the location you installed PHP too.
{| class="nicetable"
|[[Image:lightbulb.png]]
|Download and install any text editor that can save the file in a UTF-8 format, [http://www.crimsoneditor.com Crimson Editor] is one such, NotePad++ is another, use that instead of either Wordpad or Notepad! The issue is that WordPad or Notepad will include hidden characters that may not be compatible with the requirements of PHP.
|}

*Open C:\PHP
*Right Click the '''php.ini''' file in this folder and choose "Open with..." selecting your editor of choice.
*Press Ctrl + F and type "post_max_size" (click Find...", where needed)
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl + F and type "upload_max_filesize" (click Find...", where needed)
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl + F and type "max_execution_time" (click Find...", where needed)
*Change the value to 600
*Press Ctrl and S or the save button.
*Exit your editor.
*Restart your webserver to reload PHP with the edited changes.
**'''For IIS'''
**Open the Start Menu on your server and select "Run"
**Type "iisreset /RESTART"
**For '''Apache 2 and Windows XP'''
**Go to Start > All Programs > Apache > Restart
**'''For Apache 2 and Windows Server'''
**The following command will work as long as you have installed Apache 2 as a service on your Windows Server
**Open your Start Menu on your server and select "Run"
**Type "httpd -k restart"

Your new file size limit should now appear in Administration > Security > Site Policies > Maximum uploaded file size

'''NOTE:''' These instructions also cover the Xampp Windows installer. Just replace C:\PHP with C:\Moodle\server\php and to restart your Moodle with a normal stop-start.

==Modifying the apache config file==
====Ubuntu Linux Instructions====
You may also need to edit the config.php file in the moodle directory:
*Type "gksudo nautilus" to get root permissions
*Navigate to /etc/moodle
*Open apache.conf
*Go to the "<IfModule mod_php5.c>" section
*Change "php_value upload_max_filesize = 2M" to a higher value
*Change "php_value post_max_size = 2M" to a higher value
*Go to the "<IfModule mod_php4.c>" section
*Change "php_value upload_max_filesize = 2M" to a higher value
*Change "php_value post_max_size = 2M" to a higher value
*Save file
*Type sudo /etc/init.d/apache2 restart

===Modifying the .htaccess file===

The following instructions will only work on an Apache web server, and also the Apache server must have Overrides allowed. Traditionally, you could only use .htaccess files when PHP was run as a module of Apache, but with Apache 2.2, this appears to no longer be the case. You can now use the .htaccess file in either module or cgi forms. As well, allowing the use of .htaccess files will cause a performance hit on the server, not a desirable outcome either - so check with your Host.

The .htaccess file is a distributed configuration file, that is, it can be used on a per-folder basis to configure each user's folder and sub-folders. You cannot alter the "AllowOverrides" directive in the Apache configuration file with a .htaccess file, only the Host can set that manually. Usually the Host will place a .htaccess file into your site Root if they do allow you to override the server settings. You can edit it the same as below, and the overrides you set will work. Alternatively, you may create your own .htaccess file in your text editor. It may also be called something else, like .config. If you have any file that starts with a ., you might want to open it in your text editor, just out of curiosity.

Create a file called .htaccess in Moodle's main directory (where 'index.php' is located, not the 'moodledata' directory) that contains the following information:

php_value upload_max_filesize 20971520
php_value post_max_size 20971520
php_value max_execution_time 600

20971520 is the integer value for 20Mb. You can use the following site to [http://www.onlineconversion.com/computer_base2.htm convert MegaBytes to Bytes].

For a more complete description of how to edit the .htacess file, look at this page, [http://httpd.apache.org/docs/current/howto/htaccess.html Apache Tutorial: .htaccess files]

===Modifying the IIS 7.0/7.5 configuration (Windows Server 2008, Windows Server 2008 R2)===
First increase activity and request time outs (allows large files to succeed on slow connections)
FastCGI Settings > Edit (Right-click on PHP application)
Set Process Model > Activity Timeout to '3600' (one hour)
Set Process Model > Request Timeout to '3600' (one hour)
Next set 'Maximum allowed content length'
Request Filtering > Edit Feature Settings:
Set 'Maximum allowed content length' to your desired file size (in bytes) e.g. '536870912' for 512MB (default is approximately 28.6MB)

==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

{| class="nicetable"
|[[Image:lightbulb.png]]
|It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.
|}

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They may already have a standard file you can use, if so, use it - but perhaps not.

To the .htaccess file add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and tell you to use a php.ini file for php directives. Here you can use the instruction located in the section above called [[File_upload_size#Modifying_the_php.ini_file|Modifying the php.ini file]].

Find the php.ini file in your moodle subfolder on your hosted server. You might want to copy the file as a backup just in case. Edit php.ini, find "upload_max_filesize" and post_max_size in the code. After the = change the number. Here the max filesize is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

{| class="nicetable"
|[[Image:lightbulb.png]]
|Still not changed? Some hosts using cpanel have a php config program under services/software. Use the "Single php.ini" option and make sure you note the location of the php.ini file to modify. This changes the .htaccess file in the same area and thus the server limit for all programs using php.
|}

==See Also==
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F|Administration FAQ Doc page]]
*[[Site_policies#Maximum_uploaded_file_size|Site Policies Doc page]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=39625 Detailed instructions to increase the maximum allowed size for uploaded files] forum discussion
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97907 Instructions to increase maximum allowed size on hosted servers] forum discussion
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=124441 Help on changing the maximum upload size when installing Moodle via apt-get] forum discussion

[[es:Tamaño de archivo subido]]

[[Category:FAQ|File]]

File upload size

2016-03-04T10:16:18Z

T100ss: /* Modifying the php.ini file */

{{Installing Moodle}}Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:

Server level
Moodle site level
Course level
Activity level

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

==Physical access to Server==
These instructions assume you have full physical and administrative access to your server. If you are using a hosted server then you will probably need to look into other ways to increase your file upload size.

There are positives and negatives to both methods below. If you modify the php.ini file then the changes will effect all php applications on your server. Since PHP5 you can only have one php.ini file on your server. The php.ini method will work with all web servers though. The .htaccess method will only effect the folder and all subfolders that it is placed in, but you must have certain settings enabled in Apache.

==Restricting the File size - how it works==
The Host may set a limit on the maximum file upload size in the Server environment, which you may override if the Host allows you to. PHP has a setting that it uses to limit the size of the file that it handles in upload. The Host has set that figure in the php.ini based on their particular perceptions and their clientele need. This size appears in Moodle in the '''Administration > Security > Site Policies > Maximum uploaded file size''' drop-down combo box. You can change this at any time to suit your site need. In the Course Settings page, there is also a further restriction that can be made. At no time can the Course setting over-ride the Site setting, nor can the Site setting over-ride the php.ini setting, which cannot over-ride the Server setting. The only exception to this rule is that you can manipulate both the Server and the PHP settings, and how to do that is described below.

==Modifying the php.ini file==
These instructions show you how to change the file upload size by editing your php.ini file.
====Ubuntu Linux Instructions====

These instructions assume that you have installed the standard Moodle package, PHP 5 and Apache 2 via apt-get and left it all as a default install. If you have compiled yourself I presume that you will know where your php.ini files are!

You need to edit the following three settings in your php.ini file located at: /etc/php5/apache2/
Here are a set of instructions to follow line by line.

*Type "sudo nano /etc/php5/apache2/php.ini"
*Press Ctrl and W and type "post_max_size"
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl and W and type "upload_max_filesize"
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl and W and type "max_execution_time"
*Change the value to 600
*Press Ctrl and O
*Press Ctrl and X
*Type sudo apachectl restart

In other words, in the file /etc/php5/apache2/php.ini you need to change "post_max_size", "upload_max_filesize" and "max_execution_time" to values that suit your needs. All this using whatever editor you are used to.

[http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size NGINX] system administrators should also add client_max_body_size=XXX to the "http" section of their nginx main configuration file. ([https://rtcamp.com/tutorials/php/increase-file-upload-size-limit/#change-in-nginx-config see more info])

Your new file size limit should now appear in Administration > Security > Site Policies > Maximum uploaded file size

====XAMPP on Mac Instructions====

These are instructions for how to do this for Moodle on a Mac using the [http://download.moodle.org/macosx/ XAMPP sample download package available]. (This is not for a OS X production server.)

* Close down Apache and MySQL if they are running via the XAMPP Control app and close the XAMPP Control app
* Open Finder and go to Applications
* Navigate down and open the folder ''XAMPP'' / ''xamppfiles'' / ''etc''
* Open the file ''php.ini'' with TextEdit (or another plain text editor)
* Search for the ''post_max_size'' setting and up this from 128M (the default) to more; 500M is the maximum
* Do the same for ''upload_max_filesize'' (make the numbers the same)
* Search for the ''max_execution_time'' setting and up this to 300 (or more if you get timeouts on uploads)
* Save the php.ini file
* restart Apache and MySQL as usual

Note: You may get a "permission denied" error when saving the php.ini file unless you are logged in with admin access to your Mac. To work around this, you can set the ''/etc'' directory in which the php.ini file is located to be writable temporarily. For how to do that, see [http://answers.yahoo.com/question/index?qid=20090115235753AA4DtJ0 here] or [http://www.ehow.com/how_2314896_fix-permissions-mac-os-x.html here].

====Windows XP and Server 2003 Instructions====

These instructions presume that you have downloaded the latest PHP 5.3.x Windows zip package and extracted it to C:\PHP. If you have installed PHP to another location then change all references to "C:\PHP" to the location you installed PHP too.
{| class="nicetable"
|[[Image:lightbulb.png]]
|Download and install any text editor that can save the file in a UTF-8 format, [http://www.crimsoneditor.com Crimson Editor] is one such, NotePad++ is another, use that instead of either Wordpad or Notepad! The issue is that WordPad or Notepad will include hidden characters that may not be compatible with the requirements of PHP.
|}

*Open C:\PHP
*Right Click the '''php.ini''' file in this folder and choose "Open with..." selecting your editor of choice.
*Press Ctrl + F and type "post_max_size" (click Find...", where needed)
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl + F and type "upload_max_filesize" (click Find...", where needed)
*Change the value to the number of Mb you want your site to accept as uploads
*Press Ctrl + F and type "max_execution_time" (click Find...", where needed)
*Change the value to 600
*Press Ctrl and S or the save button.
*Exit your editor.
*Restart your webserver to reload PHP with the edited changes.
**'''For IIS'''
**Open the Start Menu on your server and select "Run"
**Type "iisreset /RESTART"
**For '''Apache 2 and Windows XP'''
**Go to Start > All Programs > Apache > Restart
**'''For Apache 2 and Windows Server'''
**The following command will work as long as you have installed Apache 2 as a service on your Windows Server
**Open your Start Menu on your server and select "Run"
**Type "httpd -k restart"

Your new file size limit should now appear in Administration > Security > Site Policies > Maximum uploaded file size

'''NOTE:''' These instructions also cover the Xampp Windows installer. Just replace C:\PHP with C:\Moodle\server\php and to restart your Moodle with a normal stop-start.

==Modifying the apache config file==
====Ubuntu Linux Instructions====
You may also need to edit the config.php file in the moodle directory:
*Type "gksudo nautilus" to get root permissions
*Navigate to /etc/moodle
*Open apache.conf
*Go to the "<IfModule mod_php5.c>" section
*Change "php_value upload_max_filesize = 2M" to a higher value
*Change "php_value post_max_size = 2M" to a higher value
*Go to the "<IfModule mod_php4.c>" section
*Change "php_value upload_max_filesize = 2M" to a higher value
*Change "php_value post_max_size = 2M" to a higher value
*Save file
*Type sudo /etc/init.d/apache2 restart

===Modifying the .htaccess file===

The following instructions will only work on an Apache web server, and also the Apache server must have Overrides allowed. Traditionally, you could only use .htaccess files when PHP was run as a module of Apache, but with Apache 2.2, this appears to no longer be the case. You can now use the .htaccess file in either module or cgi forms. As well, allowing the use of .htaccess files will cause a performance hit on the server, not a desirable outcome either - so check with your Host.

The .htaccess file is a distributed configuration file, that is, it can be used on a per-folder basis to configure each user's folder and sub-folders. You cannot alter the "AllowOverrides" directive in the Apache configuration file with a .htaccess file, only the Host can set that manually. Usually the Host will place a .htaccess file into your site Root if they do allow you to override the server settings. You can edit it the same as below, and the overrides you set will work. Alternatively, you may create your own .htaccess file in your text editor. It may also be called something else, like .config. If you have any file that starts with a ., you might want to open it in your text editor, just out of curiosity.

Create a file called .htaccess in Moodle's main directory (where 'index.php' is located, not the 'moodledata' directory) that contains the following information:

php_value upload_max_filesize 20971520
php_value post_max_size 20971520
php_value max_execution_time 600

20971520 is the integer value for 20Mb. You can use the following site to [http://www.onlineconversion.com/computer_base2.htm convert MegaBytes to Bytes].

For a more complete description of how to edit the .htacess file, look at this page, [http://httpd.apache.org/docs/current/howto/htaccess.html Apache Tutorial: .htaccess files]

===Modifying the IIS 7.0/7.5 configuration (Windows Server 2008, Windows Server 2008 R2)===
First increase activity and request time outs (allows large files to succeed on slow connections)
FastCGI Settings > Edit (Right-click on PHP application)
Set Process Model > Activity Timeout to '3600' (one hour)
Set Process Model > Request Timeout to '3600' (one hour)
Next set 'Maximum allowed content length'
Request Filtering > Edit Feature Settings:
Set 'Maximum allowed content length' to your desired file size (in bytes) e.g. '536870912' for 512MB (default is approximately 28.6MB)

==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

{| class="nicetable"
|[[Image:lightbulb.png]]
|It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.
|}

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They may already have a standard file you can use, if so, use it - but perhaps not.

To the .htaccess file add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and tell you to use a php.ini file for php directives. Here you can use the instruction located in the section above called [[File_upload_size#Modifying_the_php.ini_file|Modifying the php.ini file]].

Find the php.ini file in your moodle subfolder on your hosted server. You might want to copy the file as a backup just in case. Edit php.ini, find "upload_max_filesize" and post_max_size in the code. After the = change the number. Here the max filesize is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

{| class="nicetable"
|[[Image:lightbulb.png]]
|Still not changed? Some hosts using cpanel have a php config program under services/software. Use the "Single php.ini" option and make sure you note the location of the php.ini file to modify. This changes the .htaccess file in the same area and thus the server limit for all programs using php.
|}

==See Also==
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F|Administration FAQ Doc page]]
*[[Site_policies#Maximum_uploaded_file_size|Site Policies Doc page]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=39625 Detailed instructions to increase the maximum allowed size for uploaded files] forum discussion
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97907 Instructions to increase maximum allowed size on hosted servers] forum discussion
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=124441 Help on changing the maximum upload size when installing Moodle via apt-get] forum discussion

[[es:Tamaño de archivo subido]]

[[Category:FAQ|File]]

Apache

2015-09-15T12:37:00Z

T100ss: /* SSL */

{{Installing Moodle}}
'''This article refers to the 'Apache HTTP server''''

The Apache HTTP server is the software that (along with the PHP scripting language) 'runs' Moodle. Note that there are alternatives (e.g. IIS on Windows) but the Apache HTTP Server is very popular on all platforms.

== Installing Apache ==
Installers are available for most platforms from http://httpd.apache.org/download.cgi. The official installation instructions are here: http://httpd.apache.org/docs/2.0/install.html. If you are running Linux then you are recommended to use the packaged version if you can. For example in Debian/Ubuntu it is simply:
<pre>
sudo apt-get install apache2
</pre>

See the documentation for your particular platform for the instructions. Apache is straightforward to build from source if you have to and the PHP documentation contains an article on building both Apache and PHP together - although you should rarely need to do that.

==Performance==

See [[Performance recommendations]]

==Slasharguments==

The function ''slash arguments'' is required for various features in Moodle to work correctly, as described in [[Using slash arguments]].

To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory:

AcceptPathInfo On

Note: When using ".htaccess" in your local Moodle install folder, you should include/enable "AllowOverride Directive" in "httpd.conf", first.
Also! please note that using .htaccess file will cause performance hit on your server!

==SSL==

Moodle has an option to enable HTTPS for the whole site or for just the login pages; either option requires that your web server is configured for SSL.

* Whole site HTTPS is enabled by changing http://<url> to https:// <url> in your config.php 'wwwroot' parameter.
* Login only HTTPS is enabled by setting the 'loginhttps' parameter, where the wwwroot schema should remain as http://

Login only https is available in the admin interface via Administration>Security>HTTP Security and checking the button. (Note the warning and see ssl section below)

Prior to Moodle 2.3 It was not advised to run the whole site over HTTPS due to legacy restrictions with client-side caching. This is no longer the case assuming client browsers support the 'Cache-Control: public' method, which all supported browsers for this version of Moodle do.

To use HTTPS you will need to obtain an SSL certificate, you have two options:

* Generate a self-signed certificate. This is fine on (say) an Intranet but unsuitable for the public internet, but users will we warned the certificated is untrusted when used publicly.
* Purchase a certificate from a vendor. There is a surprising range of prices and value-added services available. Some hosting companies even provide free certificates.

Debian provides instructions for installing a self-signed certificate [https://wiki.debian.org/Self-Signed_Certificate on their wiki] and includes general information on configuring Apache for SSL.
If you purchase a vendor certificate you will normally receive instructions for installing it.

A basic Apache SSL configuration can be summarised as:

Listen 443
NameVirtualHost *:443
<VirtualHost *:443>
SSLEngine On
SSLCertificateFile /path/to/your/certificate.crt
SSLCertificateKeyFile /path/to/your/certificate.key
...
</VirtualHost>

== See also ==

* [http://httpd.apache.org/ The Apache HTTP Server Project homepage]
* [http://en.wikipedia.org/wiki/Apache_HTTP_Server Wikipedia article on the Apache HTTP Server]
* [http://httpd.apache.org/docs/2.0/misc/perf-tuning.html Apache Performance Tuning article at the official homepage]
* [https://els.earlham.edu/cayaraa/weblog/1468.html Making Moodle work with SSL]
* [http://www.krufix.de/ Using the same Moodle twice in local network and Internet via SSL-Proxy] (in German)

[[pl:Apache]]
[[ja:Apache]]
[[de:Apache]]
[[es:Apache]]

install on OS X

2015-09-04T15:19:18Z

T100ss: /* Using Homebrew */

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not cooperate with your changes when they upgrade the OS.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

==Using the native Apache===

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so

LoadModule authz_host_module libexec/apache2/mod_authz_host.so

LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so

Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

==php modules==
To Do

=Using Homebrew=

This is an easier alternative to most of the above.
Homebrew is a package management tool like apt and yum which was created for OSX. Everything ends up in /usr/local or similar and when Apple do an upgrade, they shouldn't muck it up.
The homebrew site is at http://brew.sh

Start with the command

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

[[Category:Installation]]

install on OS X

2015-09-04T14:00:09Z

T100ss: /* Using Homebrew */

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not cooperate with your changes when they upgrade the OS.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

==Using the native Apache===

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so

LoadModule authz_host_module libexec/apache2/mod_authz_host.so

LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so

Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

==php modules==
To Do

=Using Homebrew=
This is an easier alternative to most of the above.
Homebrew is a package management tool like apt and yum which was created for OSX. Everything ends up in /usr/local or similar and when Apple do an upgrade, they shouldn't muck it up.

[[Category:Installation]]

install on OS X

2015-09-04T13:59:45Z

T100ss: /* Using Homebrew */

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not cooperate with your changes when they upgrade the OS.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

==Using the native Apache===

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so

LoadModule authz_host_module libexec/apache2/mod_authz_host.so

LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so

Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

==php modules==
To Do

===Using Homebrew===
This is an easier alternative to most of the above.
Homebrew is a package management tool like apt and yum which was created for OSX. Everything ends up in /usr/local or similar and when Apple do an upgrade, they shouldn't muck it up.

[[Category:Installation]]

install on OS X

2015-09-04T13:59:13Z

T100ss:

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not cooperate with your changes when they upgrade the OS.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

==Using the native Apache===

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so

LoadModule authz_host_module libexec/apache2/mod_authz_host.so

LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so

Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

==php modules==
To Do

==Using Homebrew==
This is an easier alternative to most of the above.
Homebrew is a package management tool like apt and yum which was created for OSX. Everything ends up in /usr/local or similar and when Apple do an upgrade, they shouldn't muck it up.

[[Category:Installation]]

install on OS X

2015-09-02T09:01:26Z

T100ss: /* Yosemite native OSX install */

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not cooperate with your changes when they upgrade the OS.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so

LoadModule authz_host_module libexec/apache2/mod_authz_host.so

LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so

Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

[[Category:Installation]]

install on OS X

2015-09-02T08:19:35Z

T100ss: /* Making php etc work */

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not keep apache and php up to date on a standard OS X install.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so

LoadModule authz_host_module libexec/apache2/mod_authz_host.so

LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so

Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

[[Category:Installation]]

install on OS X

2015-09-02T08:18:41Z

T100ss: Created page with "==Yosemite native OSX install== This page is for people who want to do an OSX install without using someone else's packaging. There are some warning to bear in mind. A nati..."

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not keep apache and php up to date on a standard OS X install.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

[[Category:Installation]]

Installing Moodle

2015-09-02T08:17:34Z

T100ss:

{{Template:Installing Moodle}}
''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''

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]]) or [[ install on OS X]]. These are unsuitable for production servers.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[PostgreSQL]]/[[MySQL]]/[[MariaDB]] 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:

If you are installing Moodle in a Windows server, note that from php5.5 onwards, you will also need to have the Visual C++ Redistributable for Visual Studio 2012 installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=30679 Visual C++] ( x86 or x64)

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.
* Processor: 1GHz (min), 2GHz dual core recommended. These settings may vary according to the resources used.
* 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 ===

See the [{{Release notes}} release notes] in the dev docs for software requirements.

== 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]], [[Internet_Information_Services|IIS]], [[Nginx]]

If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.

== 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 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 --depth=1 -b MOODLE_29_STABLE git://git.moodle.org/moodle.git
</pre>
--depth=1 for shallow cloning (only) latest revision

--single-branch option to limit cloning to a single branch, this fetches the Moodle 2.9 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
# find /path/to/moodle -type f -exec chmod 0644 {} \;
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

The third command finds all the regular files and executes the chmod command 0644 on them.

If you want to use the built-in plugin installer you need to make the directory writable by web server user. It is strongly recommended to use ACL when your server supports it, for example if your Apache server uses account www-data:

<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodle
</pre>

The effect of the previous command is to allow the Apache user account (www-data in this case) to access and change files within the moodle site. Many people would consider this a brave move for a new site admin to implement. In a new moodle you can safely leave this out. A default Ubuntu install does not have the +a option for the chmod command anyway. The +a attribute is an ACL (Access Control List) facility which allows you to set per user access for individual files. For example, OSX has this by default.

== 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:
* [[PostgreSQL]]
* [[MariaDB]]
* [[MySQL]]
* [[MSSQL]]
* [[Oracle]] (known issues, not fully supported)

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

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, cache, 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.

Due to the way Moodle caches data you may have performance issues if you use relatively slow storage (e.g. NFS) for this directory. Read the [[Performance_recommendations]] carefully and consider using (e.g.) memcached for [[Caching]].

'''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 better permissions that just allow the web server user to access these files.

<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodledata
</pre>
If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:
<pre>
$ sudo chmod -R +a "`whoami` allow read,delete,write,append,file_inherit,directory_inherit" /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 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 (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 'Administration' block. Here are a few of the more important ones that you will probably want to check:
* ''Administration > Site administration > Plugins > Message Outputs > 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.
* ''Administration > Site administration > Server > System paths'': Set the paths to du, dot and aspell binaries.
* ''Administration > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Administration > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date. (more info [[Location]])
** [http://php.net/manual/en/timezones.php Set server's local timezone] inside <tt>php.ini</tt> (should probably be inside <tt>/etc/php.ini</tt> or <tt>/etc/php.d/date.ini</tt>, depending on the underline OS):
**: <code ini>[Date]
; Defines the default timezone used by the date functions
date.timezone = "YOUR LOCAL TIMEZONE"</code>

=== 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''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings > Site administration > Plugins > Message outputs > Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)
* '''Secure your Moodle site''': Read the [[Security recommendations]].
*'''Increasing the maximum upload size''' See [[Installation FAQ]] Maximum upload file size - how to change it?

=== Installation is complete :) ===

* Create a new course: You can now [[Adding a new 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)?
* Create your [[Configuration file]] (config.php) by hand. Copy config-dist.php (in the root of the Moodle program directory) to config.php, edit it and set 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]]
** [[Installing Moodle on SmarterASP.NET]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]
* [[Amazon EC2 Cloud Services Installation]]

== See also ==
* [http://www.slideshare.net/gb2048/my-own-moodle Slideshare presentation by Gareth Barnard on installing a local installation of Moodle] and accompanying [https://drive.google.com/folderview?id=0B17B0rYH2zERU21sQnVweUZCUFk&usp=sharing help guides]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]

None Mamp install on OS X

2015-09-02T08:16:09Z

T100ss:

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.
There are some warning to bear in mind.
A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the same as a Linux install and so the advice there can be applied here also Apple does not keep apache and php up to date on a standard OS X install.

Most of this work is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf or sudo vi /etc/apache2/httpd.conf

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

[[Category:Installation]]

None Mamp install on OS X

2015-09-01T13:29:24Z

T100ss:

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.

Most of this stuff is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf

A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development. The OS X install described here is essentially the samer as a Linux install and so the advice there can be applied here.

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

The default Apache user is "_www" and so your moodledata folder needs write permissions for the _www user.

sudo chown <username>:_www moodledata

In the finder, choose the folder and using the get info dialogue to give _www write access to the folder.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will probably need to install Mysql again if Apple issue an upgrade of Yosemite.

[[Category:Installation]]

None Mamp install on OS X

2015-09-01T13:06:49Z

T100ss:

==Yosemite native OSX install==

This page is for people who want to do an OSX install without using someone else's packaging.

Most of this stuff is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf

A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development.

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

=Enable Apache.=
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

=Making “Sites” work (Optional)=

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

=Making php etc work=

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

=Test php.=

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

=Mysql=

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will need to install Mysql again if Apple issue an upgrade of Yosemite.

[[Category:Installation]]

None Mamp install on OS X

2015-09-01T13:04:13Z

T100ss:

Yosemite native OSX install

This page is for people who want to do an OSX install without using someone else's packaging.

Most of this stuff is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf

A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development.

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

Enable Apache.
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

Making “Sites” work (Optional)

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

Making php etc all work

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

Test php.

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well known phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

Mysql

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will need to install Mysql again if Apple issue an upgrade of Yoesmite.

[[Category:Installation]]

None Mamp install on OS X

2015-09-01T13:01:08Z

T100ss:

Yosemite native OSX install

This page is for people who want to do an OSX install without using someone else's packaging.

Most of this stuff is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf

A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development.

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

Enable Apache.
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

Making “Sites” work (Optional)

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

Making php etc all work

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

Test php.

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well know phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

Mysql

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will need to install Mysql again if Apple issue an upgrade of Yoesmite.

[[Category:Installation]]

None Mamp install on OS X

2015-09-01T13:00:43Z

T100ss:

Yosemite native OSX install

This page is for people who want to do an OSX install without using someone else's packaging.

Most of this stuff is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf

A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development.

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

Enable Apache.
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

Making “Sites” work (Optional)

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

Making php etc all work

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

Test php.

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well know phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

Mysql

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will need to install Mysql again if Apple issue an upgrade of Yoesmite.

[[Category:Mac OS X | Installation]]

None Mamp install on OS X

2015-09-01T13:00:08Z

T100ss:

Yosemite native OSX install

This page is for people who want to do an OSX install without using someone else's packaging.

Most of this stuff is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf

A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development.

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

Enable Apache.
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

Making “Sites” work (Optional)

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

Making php etc all work

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

Test php.

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well know phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

Mysql

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will need to install Mysql again if Apple issue an upgrade of Yoesmite.

[[Category:Mac OS X]]

None Mamp install on OS X

2015-09-01T12:54:21Z

T100ss: Start of a native OSX install page 1/9/2015

Yosemite native OSX install

This page is for people who want to do an OSX install without using someone else's packaging.

Most of this stuff is via the cli which you can use in the ‘terminal’ application. To edit files, use nano or vi. Mostly you need to be root to edit the files so precede your editor name by sudo.

e.g sudo nano /etc/apache2/httpd.conf

A native install of Moodle on an OSX machine is not really suitable as an internet linked live server but it is great for testing and development.

If you are doing any kind of development on an mac then consider an installation of XCode which will install all sorts of odds and ends that you are likely to need now and then such as libraries for php etc.

e.g sudo nano /etc/apache2/httpd.conf

Enable Apache.
Apache is already installed and you need to start it and test it works. Start apache via this command.

sudo apachectl start

If you want it to start on boot then issue this command

sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist

Test this by going to http://localhost on a browser.
at the time of writing 01/09/2015 this test was passed by Safari, Firefox and Chrome.

Making “Sites” work (Optional)

Mac users are used to having a Sites folder which publishes a local-users web site on http://<host url address>/~<UserName>

cd /etc/apache2/users
edit <username>.conf

with these contents. Don’t forget to change <username> for your username.

<Directory "/Users/<username>/Sites/">
AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted
</Directory>

Making php etc all work

in /etc/apache2/httpd.conf uncomment all the following lines

LoadModule authz_core_module libexec/apache2/mod_authz_core.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule userdir_module libexec/apache2/mod_userdir.soLoadModule php5_module libexec/apache2/libphp5.so
Include /private/etc/apache2/extra/httpd-userdir.conf

Test php.

Make a file in the root of your webfolder called phpinfo.php and add this content.
<?php phpinfo(); ?>

Then, visit the site by url httpd://localhost/<your user name>/phpinfo.php

This should give you the well know phpinfo page. The most likely error will be a page just showing the text <?php phpinfo(); ?> which means php is not working.

Mysql

Download your version of Mysql from the Mysql site http://dev.mysql.com/downloads/mysql/
and install it!
The dmg install will put a system settings item enabling Mysql to be started/stopped. If you tick the option to start on boot then it may not actually start on boot. This is an on-off issue with OSX.

If you are not running OSX server then you will need to install Mysql again if Apple issue an upgrade of Yoesmite.

Installing Moodle

2015-09-01T12:50:22Z

T100ss: Adding page for native OSX install

{{Template:Installing Moodle}}
''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''

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]]) or [[None Mamp install on OS X]]. These are unsuitable for production servers.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[PostgreSQL]]/[[MySQL]]/[[MariaDB]] 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:

If you are installing Moodle in a Windows server, note that from php5.5 onwards, you will also need to have the Visual C++ Redistributable for Visual Studio 2012 installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=30679 Visual C++] ( x86 or x64)

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.
* Processor: 1GHz (min), 2GHz dual core recommended. These settings may vary according to the resources used.
* 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 ===

See the [{{Release notes}} release notes] in the dev docs for software requirements.

== 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]], [[Internet_Information_Services|IIS]], [[Nginx]]

If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.

== 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 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 --depth=1 -b MOODLE_29_STABLE git://git.moodle.org/moodle.git
</pre>
--depth=1 for shallow cloning (only) latest revision

--single-branch option to limit cloning to a single branch, this fetches the Moodle 2.9 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
# find /path/to/moodle -type f -exec chmod 0644 {} \;
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

The third command finds all the regular files and executes the chmod command 0644 on them.

If you want to use the built-in plugin installer you need to make the directory writable by web server user. It is strongly recommended to use ACL when your server supports it, for example if your Apache server uses account www-data:

<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodle
</pre>

The effect of the previous command is to allow the Apache user account (www-data in this case) to access and change files within the moodle site. Many people would consider this a brave move for a new site admin to implement. In a new moodle you can safely leave this out. A default Ubuntu install does not have the +a option for the chmod command anyway. The +a attribute is an ACL (Access Control List) facility which allows you to set per user access for individual files. For example, OSX has this by default.

== 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:
* [[PostgreSQL]]
* [[MariaDB]]
* [[MySQL]]
* [[MSSQL]]
* [[Oracle]] (known issues, not fully supported)

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

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, cache, 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.

Due to the way Moodle caches data you may have performance issues if you use relatively slow storage (e.g. NFS) for this directory. Read the [[Performance_recommendations]] carefully and consider using (e.g.) memcached for [[Caching]].

'''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 better permissions that just allow the web server user to access these files.

<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodledata
</pre>
If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:
<pre>
$ sudo chmod -R +a "`whoami` allow read,delete,write,append,file_inherit,directory_inherit" /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 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 (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 'Administration' block. Here are a few of the more important ones that you will probably want to check:
* ''Administration > Site administration > Plugins > Message Outputs > 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.
* ''Administration > Site administration > Server > System paths'': Set the paths to du, dot and aspell binaries.
* ''Administration > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Administration > Site administration > Location > Update timezones'': Run this to make sure your timezone information is up to date. (more info [[Location]])
** [http://php.net/manual/en/timezones.php Set server's local timezone] inside <tt>php.ini</tt> (should probably be inside <tt>/etc/php.ini</tt> or <tt>/etc/php.d/date.ini</tt>, depending on the underline OS):
**: <code ini>[Date]
; Defines the default timezone used by the date functions
date.timezone = "YOUR LOCAL TIMEZONE"</code>

=== 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''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings > Site administration > Plugins > Message outputs > Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)
* '''Secure your Moodle site''': Read the [[Security recommendations]].
*'''Increasing the maximum upload size''' See [[Installation FAQ]] Maximum upload file size - how to change it?

=== Installation is complete :) ===

* Create a new course: You can now [[Adding a new 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)?
* Create your [[Configuration file]] (config.php) by hand. Copy config-dist.php (in the root of the Moodle program directory) to config.php, edit it and set 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]]
** [[Installing Moodle on SmarterASP.NET]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]
* [[Amazon EC2 Cloud Services Installation]]

== See also ==
* [http://www.slideshare.net/gb2048/my-own-moodle Slideshare presentation by Gareth Barnard on installing a local installation of Moodle] and accompanying [https://drive.google.com/folderview?id=0B17B0rYH2zERU21sQnVweUZCUFk&usp=sharing help guides]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]

Features

2015-08-19T19:11:31Z

T100ss: changed drop and drop to drag and drop

{{About Moodle}}
Moodle is a free, online Learning Management system enabling educators to create their own private website filled with dynamic courses that extend learning, any time, anywhere.

Whether you're a teacher, student or administrator, Moodle can meet your needs. Moodle’s extremely customisable core comes with many standard features. Take a look at a highlight of Moodle's core features below.

==General Features==
<div class="contentblock">
<gallery mode="nolines" widths="300px" heights="225px">
Image:better-responsive-design.png|<h3>Modern, easy to use interface</h3>Designed to be responsive and accessible, the Moodle interface is easy to navigate on both desktop and mobile devices.<br>[http://school.demo.moodle.net/ View demo]
Image:newdashboardfeature.png|<h3>Personalised Dashboard</h3>Organise and display courses the way you want, and view at a glance current tasks and messages.<br>[[Dashboard]]
Image:Collaborative-tools.jpg|<h3>Collaborative tools and activities</h3>Work and learn together in forums, wikis, glossaries, database activities, and much more.<br>[[Activities]]
Image:all-in-one-Calendar.jpg|<h3>All-in-one calendar</h3>Moodle’s calendar tool helps you keep track of your academic or company calendar, course deadlines, group meetings, and other personal events. <br>[[Calendar]]
Image:File-Management.jpg|<h3>Convenient file management</h3>Drag and drop files from cloud storage services including MS Skydrive, Dropbox and Google Drive.<br>[[Working with files]]
Image:text-editor.jpg|<h3>Simple and intuitive text editor</h3>Format text and conveniently add media and images with an editor that works across all web browsers and devices.<br>[[Text editor]]
Image:Notifications.jpg|<h3>Notifications</h3>When enabled, users can receive automatic alerts on new assignments and deadlines, forum posts and also send private messages to one another.<br>[[Messaging]]
Image:track-progress.jpg|<h3>Track progress</h3>Educators and learners can track progress and completion with an array of options for tracking individual activities or resources and at course level.<br>[[Tracking progress]]
</img></gallery>

[[Main page|View the complete list of features→]]

==Administrative Features==

<gallery mode="nolines" widths="300px" heights="225px">
Image:customisedesign.jpg|<h3>Customisable site design and layout</h3>Easily customise a Moodle theme with your logo, colour schemes and much more - or simply design your own theme.<br>[[Themes]]
Image:secure-authentication-and-enrolment.jpg|<h3>Secure authentication and mass enrolment</h3>Over 50 authentication and enrolment options to add and enrol users to your Moodle site and courses.<br>[[Authentication]] / [[Enrolment]]
Image:multilingual-capability.jpg|<h3>Multilingual capability</h3>Allow users to view course content and learn in their own language, or set it up for multilingual users and organisations. <br>[[Language]]
Image:bulk-course-upload.jpg|<h3>Bulk course creation and easy backup</h3>Add courses in bulk, back up and restore large courses with ease.<br>[[Bulk course upload]]
Image:manage-user-roles.jpg|<h3>Manage user roles and permissions</h3>Address security concerns by defining roles to specify and manage user access.<br>[[Roles and permissions]]
Image:lti-scorm-compliant.jpg|<h3>Supports open standards</h3>Readily import and export IMS-LTI, SCORM courses and more into Moodle. <br>[[SCORM]] / [[External tool]]
Image:embed-external-tool.jpg|<h3>High interoperability</h3>Freely integrate external applications and content or create your own plugin for custom integrations. <br>[[Standards]]
Image:Install_add_on.jpg|<h3>Simple plugin management</h3>Install and disable plugins within a single admin interface. <br>[[Installing plugins]]
Image:security-updates.jpg|<h3>Regular security updates</h3>Moodle is regularly updated with the latest security patches to help ensure your Moodle site is secure. <br>[[Security]]
Image:detailed-logs.jpg|<h3>Detailed reporting and logs</h3>View and generate reports on activity and participation at course and site level.<br>[[Site-wide reports]]
</img></gallery>

[[Managing a Moodle site|See all site management and development features→]]

==Course Development and Management Features==
<gallery mode="nolines" widths="300px" heights="225px">
Image:direct-learning-path.jpg|<h3>Direct learning paths</h3>Design and manage courses to meet various requirements. Classes can be instructor-led, self-paced, blended or entirely online. <br>[[Pedagogy]]
Image:collaborative-activities.jpg|<h3>Encourage collaboration</h3>Built-in collaborative publishing features foster engagement and encourage content-driven collaboration. <br>[[Activities]]
Image:embed-external-tool.jpg|<h3>Embed external resources</h3>Teach materials and include assignments from other sites and connect to the gradebook in Moodle.<br>[[External tool]]
Image:built-in-media-support.jpg|<h3>Multimedia Integration</h3>Moodle’s built-in media support enables you to easily search for and insert video and audio files in your courses. <br>[[Working with media]]
Image:manage-groups.jpg|<h3>Group management</h3>Group learners to share courses, differentiate activities and facilitate team work.<br>[[Groups]]
Image:marking-workflow.jpg|<h3>Marking workflow</h3>Conveniently assign different markers to assignments, manage grade moderation and control when marks are released to individual learners.<br>[[Assignment module]]
Image:annotate-pdf.jpg|<h3>In-line marking</h3>Easily review and provide in-line feedback by annotating on PDF files directly within browser.<br>[[Assignment module]]
Image:peer-and-self-assessment.jpg|<h3>Peer and self assessment</h3>Built-in activities such as workshops and surveys encourages learners to view, grade and assess their own and other course members' work as a group.<br>[[Workshop]]
Image:badges.jpg|<h3>Integrated Badges</h3>Fully compatible with Mozilla Open Badges, motivate learners and reward participation and achievement with customised Badges. <br>[[Badges]]
Image:advanced-grading.jpg|<h3>Outcomes and rubrics</h3>Select from advanced grading methods to tailor the gradebook to your course and examination criteria.<br>[[Grades]]
Image:private-classroom.jpg|<h3>Security and privacy</h3>Teach and share in a private space only you and your class can access.<br>[[Courses]]
</img></gallery>

[[Managing a Moodle course|See all course creation and management features→]]
</div>
[[es:Características]]

Upgrading

2014-12-23T15:51:51Z

T100ss: /* Install the new Moodle software */

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Check that your server meets all requirements for 2.8 in ''Administration > Site administration > Server > [[Environment]]''.

Note: You can only upgrade to Moodle 2.8 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

== Backup important data ==

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, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

==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.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.8 version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

== Install the new Moodle software ==
You can fetch the current (2.8) version of the software through

wget http://sourceforge.net/projects/moodle/files/Moodle/stable28/moodle-latest-28.tgz

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.
# Dont forget to also copy over your moodledata folder / directory. If you don't you will get a "fatal error $cfg- dataroot is not configured properly".

====Linux====
mv moodle moodle.backup
tar xvzf moodle-2.8.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that 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 make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.

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 or chmod 755)
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.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle 2.8 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

To do this just go to ''Administration > Site administration > Notifications''.

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!

Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 2.8 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.8 config-dist.php.

===Cron===

Cron has received a major update (MDL-25499) and now has support for both scheduled and adhoc tasks.

The benefits of these changes are:
* The schedule for every task can be configured by the admin
* Tasks can run in parallel
* Cron processes use locking to prevent the same task running at the same time by different processes
* Clusters with multiple identical application nodes are supported, you can run cron on all of them

A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least ''once per minute''.

You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure.

Before the upgrade to 2.8, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade to 2.8.

===Assignments===

The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one.

If you are still using the old assignment (2.2) module, after upgrading to Moodle 2.8 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.

If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 2.8, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.

==Possible issues that may affect you in Moodle 2.8==

===New aggregation method - 'Natural'===

The aggregation method 'Sum of grades' used in the [[Grades|gradebook]] has been reviewed, significantly improved and renamed to 'Natural'. It is recommended that 'Natural' is set as the default aggregation method, as for new Moodle 2.8 installs.

In addition, the aggregation setting 'Aggregate including subcategories' has been removed.

Any courses previously using either 'Sum of grades' and/or 'Aggregate including subcategories' may have some changes to grades. Thus it is recommended that grades in the gradebook are reviewed for such courses.

===Teachers able to enrol users via the cohort sync enrolment method===

Teachers will get access to [[Cohort sync]] enrolment method if it is enabled, remove capability to use this enrolment method from teachers if you want to preserve 2.7 behaviour. See MDL-36014

===Gradebook scrolling and theme issues===
Themes with non-fixed headers must have the .navbar class in their navbar in order for floating headers in the grader report to work - see MDL-46658 for more information.

===Removal of the 'Group members only' experimental setting===

The experimental setting 'Group members only' has been removed in Moodle 2.8. The group and grouping restrictions in [[Conditional activities settings|conditional activities]] now provide this functionality. Any 'Available for group members only' instances are automatically converted to group or grouping restrictions when a site is upgraded.

* 'Available for group members only' instances with no grouping selected are converted to a 'Must belong to any group' restriction.
* 'Available for group members only' instances with a grouping specified are converted to a 'Must belong to the specific grouping' restriction.

''More items to be added here...''

=== Moodle 2.3, 2.4, 2.5, 2.6 and 2.7 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3]
* [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4]
* [https://docs.moodle.org/25/en/Upgrading Upgrading to Moodle 2.5]
* [https://docs.moodle.org/26/en/Upgrading Upgrading to Moodle 2.6]
* [https://docs.moodle.org/27/en/Upgrading Upgrading to Moodle 2.7]

==See also==

* [[Installation]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[dev:Moodle 2.8 release notes|Moodle 2.8 release notes]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

MySQL

2014-12-10T15:34:38Z

T100ss: /* Creating Moodle database */

{{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. Increase the 'max_allowed_packet' setting to at least 4 megabytes.

== 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.
Databases have a "Character set" and a "Collation". For moodle the character set should be utf8 and the collation is utf8_general_ci. You may get the option to set these values when you create the database. If you are not given a choice, the default options are probably good. An install on an old server may have the wrong settings.

=== 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). We recommend you use '''utf8_unicode_ci''' for collation.
<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.

==Which database belongs to which Moodle==
If you have installed several Moodle installations on the same server, there will be several several databases in your MySQL server. The names might be quite poor reflections of the content like _mdl1 _mdl2 _mdl3 . So how do I see which database goes with which Moodle installation? You can go in with phpMyAdmin and in the various databases check for the table "mdl_course". There you will easily see the name of that Moodle Installation. In table mdl_config you can see the Moodle version. (Where can one find the home relative URL of the Moodle installation?)

== See also ==

* [[MariaDB]]
* [http://www.mysql.com/ The MySQL homepage]
* [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]]
[[es:MySQL]]

Installing Moodle

2014-12-10T14:19:23Z

T100ss:

{{Template:Installing Moodle}}
''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''

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.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[PostgreSQL]]/[[MySQL]]/[[MariaDB]] 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:

If you are installing Moodle in a Windows server, note that from php5.5 onwards, you will also need to have the Visual C++ Redistributable for Visual Studio 2012 installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=30679 Visual C++] ( x86 or x64)

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.
* Processor: 1GHz (min), 2GHz dual core recommended. These settings may vary according to the resources used.
* 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 ===

See the [{{Release notes}} release notes] in the dev docs for software requirements.

== 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]]

If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.

== 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 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 --depth=1 -b MOODLE_28_STABLE --single-branch git://git.moodle.org/moodle.git
</pre>
--depth=1 for shallow cloning (only) latest revision

--single-branch option to limit cloning to a single branch, this fetches the Moodle 2.8 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
# find /path/to/moodle -type f -exec chmod 0644 {} \;
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

The third command finds all the regular files and executes the chmod command 0644 on them.

If you want to use the built-in plugin installer you need to make the directory writable by web server user. It is strongly recommended to use ACL when your server supports it, for example if your Apache server uses account www-data:

<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodle
</pre>

The effect of the previous command is to allow the Apache user account (www-data in this case) to access and change files within the moodle site. Many people would consider this a brave move for a new site admin to implement. In a new moodle you can safely leave this out. A default Ubuntu install does not have the +a option for the chmod command anyway. The +a attribute is an ACL (Access Control List) facility which allows you to set per user access for individual files. For example, OSX has this by default.

== 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:
* [[PostgreSQL]]
* [[MariaDB]]
* [[MySQL]]
* [[MSSQL]]
* [[Oracle]] (known issues, not fully supported)

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

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, cache, 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.

Due to the way Moodle caches data you may have performance issues if you use relatively slow storage (e.g. NFS) for this directory. Read the [[Performance_recommendations]] carefully and consider using (e.g.) memcached for [[Caching]].

'''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 better permissions that just allow the web server user to access these files.

<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodledata
</pre>
If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:
<pre>
$ sudo chmod -R +a "`whoami` allow read,delete,write,append,file_inherit,directory_inherit" /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 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 (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 'Administration' block. Here are a few of the more important ones that you will probably want to check:
* ''Administration > Site administration > Plugins > Message Outputs > 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.
* ''Administration > Site administration > Server > System paths'': Set the paths to du, dot and aspell binaries.
* ''Administration > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Administration > 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''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings > Site administration > Plugins > Message outputs > Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)
* '''Secure your Moodle site''': Read the [[Security recommendations]].
*'''Increasing the maximum upload size''' See [[Installation FAQ]] Maximum upload file size - how to change it?

=== Installation is complete :) ===

* Create a new course: You can now [[Adding a new 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)?
* Create your [[Configuration file]] (config.php) by hand. Copy config-dist.php (in the root of the Moodle program directory) to config.php, edit it and set 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]]
** [[Installing Moodle on SmarterASP.NET]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]
* [[Amazon EC2 Cloud Services Installation]]

== See also ==
* [http://www.slideshare.net/gb2048/my-own-moodle Slideshare presentation by Gareth Barnard on installing a local installation of Moodle] and accompanying [https://drive.google.com/folderview?id=0B17B0rYH2zERU21sQnVweUZCUFk&usp=sharing help guides]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]

Installing Moodle

2014-12-10T14:09:00Z

T100ss:

{{Template:Installing Moodle}}
''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''

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.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[PostgreSQL]]/[[MySQL]]/[[MariaDB]] 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:

If you are installing Moodle in a Windows server, note that from php5.5 onwards, you will also need to have the Visual C++ Redistributable for Visual Studio 2012 installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=30679 Visual C++] ( x86 or x64)

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.
* Processor: 1GHz (min), 2GHz dual core recommended. These settings may vary according to the resources used.
* 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 ===

See the [{{Release notes}} release notes] in the dev docs for software requirements.

== 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]]

If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.

== 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 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 --depth=1 -b MOODLE_28_STABLE --single-branch git://git.moodle.org/moodle.git
</pre>
--depth=1 for shallow cloning (only) latest revision

--single-branch option to limit cloning to a single branch, this fetches the Moodle 2.8 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
# find /path/to/moodle -type f -exec chmod 0644 {} \;
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

The third command finds all the regular files and executes the chmod command 0644 on them.

If you want to use the built-in plugin installer you need to make the directory writable by web server user. It is strongly recommended to use ACL when your server supports it, for example if your Apache server uses account www-data:

<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodle
</pre>

The effect of the previous command is to allow the Apache user account (www-data in this case) to access to change files in the site. In a new moodle you can safely leave this out.) A default Ubuntu install does not have the +a option for the chmod command anyway.

== 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:
* [[PostgreSQL]]
* [[MariaDB]]
* [[MySQL]]
* [[MSSQL]]
* [[Oracle]] (known issues, not fully supported)

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

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, cache, 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.

Due to the way Moodle caches data you may have performance issues if you use relatively slow storage (e.g. NFS) for this directory. Read the [[Performance_recommendations]] carefully and consider using (e.g.) memcached for [[Caching]].

'''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 better permissions that just allow the web server user to access these files.

<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodledata
</pre>
If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:
<pre>
$ sudo chmod -R +a "`whoami` allow read,delete,write,append,file_inherit,directory_inherit" /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 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 (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 'Administration' block. Here are a few of the more important ones that you will probably want to check:
* ''Administration > Site administration > Plugins > Message Outputs > 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.
* ''Administration > Site administration > Server > System paths'': Set the paths to du, dot and aspell binaries.
* ''Administration > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Administration > 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''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings > Site administration > Plugins > Message outputs > Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)
* '''Secure your Moodle site''': Read the [[Security recommendations]].
*'''Increasing the maximum upload size''' See [[Installation FAQ]] Maximum upload file size - how to change it?

=== Installation is complete :) ===

* Create a new course: You can now [[Adding a new 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)?
* Create your [[Configuration file]] (config.php) by hand. Copy config-dist.php (in the root of the Moodle program directory) to config.php, edit it and set 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]]
** [[Installing Moodle on SmarterASP.NET]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]
* [[Amazon EC2 Cloud Services Installation]]

== See also ==
* [http://www.slideshare.net/gb2048/my-own-moodle Slideshare presentation by Gareth Barnard on installing a local installation of Moodle] and accompanying [https://drive.google.com/folderview?id=0B17B0rYH2zERU21sQnVweUZCUFk&usp=sharing help guides]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]

Installing Moodle

2014-12-10T14:07:08Z

T100ss:

{{Template:Installing Moodle}}
''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''

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.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[PostgreSQL]]/[[MySQL]]/[[MariaDB]] 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:

If you are installing Moodle in a Windows server, note that from php5.5 onwards, you will also need to have the Visual C++ Redistributable for Visual Studio 2012 installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=30679 Visual C++] ( x86 or x64)

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.
* Processor: 1GHz (min), 2GHz dual core recommended. These settings may vary according to the resources used.
* 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 ===

See the [{{Release notes}} release notes] in the dev docs for software requirements.

== 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]]

If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.

== 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 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 --depth=1 -b MOODLE_28_STABLE --single-branch git://git.moodle.org/moodle.git
</pre>
--depth=1 for shallow cloning (only) latest revision

--single-branch option to limit cloning to a single branch, this fetches the Moodle 2.8 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
# find /path/to/moodle -type f -exec chmod 0644 {} \;
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

The third command finds all the regular files and executes the chmod command 0644 on them.

If you want to use the built-in plugin installer you need to make the directory writable by web server user. It is strongly recommended to use ACL when your server supports it, for example if your Apache server uses account www-data: The effect of this command is to all the Apache user account (www-data in this case) to access to change files in the site. In a new moodle you can safely leave this out.)
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodle
</pre>

== 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:
* [[PostgreSQL]]
* [[MariaDB]]
* [[MySQL]]
* [[MSSQL]]
* [[Oracle]] (known issues, not fully supported)

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

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, cache, 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.

Due to the way Moodle caches data you may have performance issues if you use relatively slow storage (e.g. NFS) for this directory. Read the [[Performance_recommendations]] carefully and consider using (e.g.) memcached for [[Caching]].

'''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 better permissions that just allow the web server user to access these files.

<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodledata
</pre>
If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:
<pre>
$ sudo chmod -R +a "`whoami` allow read,delete,write,append,file_inherit,directory_inherit" /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 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 (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 'Administration' block. Here are a few of the more important ones that you will probably want to check:
* ''Administration > Site administration > Plugins > Message Outputs > 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.
* ''Administration > Site administration > Server > System paths'': Set the paths to du, dot and aspell binaries.
* ''Administration > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Administration > 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''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings > Site administration > Plugins > Message outputs > Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)
* '''Secure your Moodle site''': Read the [[Security recommendations]].
*'''Increasing the maximum upload size''' See [[Installation FAQ]] Maximum upload file size - how to change it?

=== Installation is complete :) ===

* Create a new course: You can now [[Adding a new 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)?
* Create your [[Configuration file]] (config.php) by hand. Copy config-dist.php (in the root of the Moodle program directory) to config.php, edit it and set 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]]
** [[Installing Moodle on SmarterASP.NET]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]
* [[Amazon EC2 Cloud Services Installation]]

== See also ==
* [http://www.slideshare.net/gb2048/my-own-moodle Slideshare presentation by Gareth Barnard on installing a local installation of Moodle] and accompanying [https://drive.google.com/folderview?id=0B17B0rYH2zERU21sQnVweUZCUFk&usp=sharing help guides]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]

Installing Moodle

2014-12-10T14:02:33Z

T100ss:

{{Template:Installing Moodle}}
''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''

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.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[PostgreSQL]]/[[MySQL]]/[[MariaDB]] 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:

If you are installing Moodle in a Windows server, note that from php5.5 onwards, you will also need to have the Visual C++ Redistributable for Visual Studio 2012 installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=30679 Visual C++] ( x86 or x64)

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.
* Processor: 1GHz (min), 2GHz dual core recommended. These settings may vary according to the resources used.
* 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 ===

See the [{{Release notes}} release notes] in the dev docs for software requirements.

== 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]]

If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.

== 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 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 --depth=1 -b MOODLE_28_STABLE --single-branch git://git.moodle.org/moodle.git
</pre>
--depth=1 for shallow cloning (only) latest revision

--single-branch option to limit cloning to a single branch, this fetches the Moodle 2.8 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
# find /path/to/moodle -type f -exec chmod 0644 {} \;
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

The third command finds all the regular files and executes the chmod command 0644 on them.

If you want to use the built-in plugin installer you need to make the directory writable by web server user. It is strongly recommended to use ACL when your server supports it, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodle
</pre>

== 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:
* [[PostgreSQL]]
* [[MariaDB]]
* [[MySQL]]
* [[MSSQL]]
* [[Oracle]] (known issues, not fully supported)

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

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, cache, 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.

Due to the way Moodle caches data you may have performance issues if you use relatively slow storage (e.g. NFS) for this directory. Read the [[Performance_recommendations]] carefully and consider using (e.g.) memcached for [[Caching]].

'''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 better permissions that just allow the web server user to access these files.

<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodledata
</pre>
If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:
<pre>
$ sudo chmod -R +a "`whoami` allow read,delete,write,append,file_inherit,directory_inherit" /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 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 (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 'Administration' block. Here are a few of the more important ones that you will probably want to check:
* ''Administration > Site administration > Plugins > Message Outputs > 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.
* ''Administration > Site administration > Server > System paths'': Set the paths to du, dot and aspell binaries.
* ''Administration > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Administration > 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''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings > Site administration > Plugins > Message outputs > Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)
* '''Secure your Moodle site''': Read the [[Security recommendations]].
*'''Increasing the maximum upload size''' See [[Installation FAQ]] Maximum upload file size - how to change it?

=== Installation is complete :) ===

* Create a new course: You can now [[Adding a new 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)?
* Create your [[Configuration file]] (config.php) by hand. Copy config-dist.php (in the root of the Moodle program directory) to config.php, edit it and set 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]]
** [[Installing Moodle on SmarterASP.NET]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]
* [[Amazon EC2 Cloud Services Installation]]

== See also ==
* [http://www.slideshare.net/gb2048/my-own-moodle Slideshare presentation by Gareth Barnard on installing a local installation of Moodle] and accompanying [https://drive.google.com/folderview?id=0B17B0rYH2zERU21sQnVweUZCUFk&usp=sharing help guides]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]

Installing Moodle

2014-12-10T13:22:46Z

T100ss: Added clarification to a command line expression.

{{Template:Installing Moodle}}
''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''

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.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[PostgreSQL]]/[[MySQL]]/[[MariaDB]] 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:

If you are installing Moodle in a Windows server, note that from php5.5 onwards, you will also need to have the Visual C++ Redistributable for Visual Studio 2012 installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=30679 Visual C++] ( x86 or x64)

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.
* Processor: 1GHz (min), 2GHz dual core recommended. These settings may vary according to the resources used.
* 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 ===

See the [{{Release notes}} release notes] in the dev docs for software requirements.

== 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]]

If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.

== 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 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 --depth=1 -b MOODLE_28_STABLE --single-branch git://git.moodle.org/moodle.git
</pre>
--depth=1 for shallow cloning (only) latest revision

--single-branch option to limit cloning to a single branch, this fetches the Moodle 2.8 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
# find /path/to/moodle -type f -exec chmod 0644 {} \;
</pre>
(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)
The command finds all the regular files and executes the chmod command 0644 on them.

If you want to use the built-in plugin installer you need to make the directory writable by web server user. It is strongly recommended to use ACL when your server supports it, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodle
</pre>

== 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:
* [[PostgreSQL]]
* [[MariaDB]]
* [[MySQL]]
* [[MSSQL]]
* [[Oracle]] (known issues, not fully supported)

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

Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, cache, 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.

Due to the way Moodle caches data you may have performance issues if you use relatively slow storage (e.g. NFS) for this directory. Read the [[Performance_recommendations]] carefully and consider using (e.g.) memcached for [[Caching]].

'''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 better permissions that just allow the web server user to access these files.

<pre>
# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata
</pre>

If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:
<pre>
# chmod -R +a "www-data allow read,delete,write,append,file_inherit,directory_inherit" /path/to/moodledata
</pre>
If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:
<pre>
$ sudo chmod -R +a "`whoami` allow read,delete,write,append,file_inherit,directory_inherit" /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 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 (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 'Administration' block. Here are a few of the more important ones that you will probably want to check:
* ''Administration > Site administration > Plugins > Message Outputs > 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.
* ''Administration > Site administration > Server > System paths'': Set the paths to du, dot and aspell binaries.
* ''Administration > Site administration > Server > HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
* ''Administration > 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''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings > Site administration > Plugins > Message outputs > Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)
* '''Secure your Moodle site''': Read the [[Security recommendations]].
*'''Increasing the maximum upload size''' See [[Installation FAQ]] Maximum upload file size - how to change it?

=== Installation is complete :) ===

* Create a new course: You can now [[Adding a new 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)?
* Create your [[Configuration file]] (config.php) by hand. Copy config-dist.php (in the root of the Moodle program directory) to config.php, edit it and set 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]]
** [[Installing Moodle on SmarterASP.NET]]
* [[Unix or Linux Installation]]
* [[Mac Installation]]
* [[Amazon EC2 Cloud Services Installation]]

== See also ==
* [http://www.slideshare.net/gb2048/my-own-moodle Slideshare presentation by Gareth Barnard on installing a local installation of Moodle] and accompanying [https://drive.google.com/folderview?id=0B17B0rYH2zERU21sQnVweUZCUFk&usp=sharing help guides]
* [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]
* [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]

Amazon EC2 Cloud Services Installation

2012-04-10T12:23:06Z

T100ss: /* To ensure that utf8 is used by mysql */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows (I have found that the precise lines required seem to vary as time goes on)
Back up my.cnf first with
cp /etc/my.cnf /etc/mycnf.original

Then edit to read

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

Check that mysql restarts with
service mysqld restart

NB edit. Later with FC16 I found that I needed to make my.cnf read

[mysqld]
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under different user or group,
# customize your systemd unit file for mysqld according to the
# instructions in http://fedoraproject.org/wiki/Systemd
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Also, you may give the apache user ownership of the site, this way, when you install, the script will be able to create the config.php file.
If you leave the owner as root, you will have to paste the suggested config.php into /var/www/html/moodle

To give apache ownership do

chown -R apache:apache /var/www/html/moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-04-10T12:22:37Z

T100ss: /* To ensure that utf8 is used by mysql */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows (I have found that the precise lines required seem to vary as time goes on)
Back up my.cnf first with
cp /etc/my.cnf /etc/mycnf.original

Then edit to read

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

Check that mysql restarts with

NB edit. Later with FC16 I found that I needed to make my.cnf read

[mysqld]
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under different user or group,
# customize your systemd unit file for mysqld according to the
# instructions in http://fedoraproject.org/wiki/Systemd
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Also, you may give the apache user ownership of the site, this way, when you install, the script will be able to create the config.php file.
If you leave the owner as root, you will have to paste the suggested config.php into /var/www/html/moodle

To give apache ownership do

chown -R apache:apache /var/www/html/moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-04-10T12:20:08Z

T100ss: /* To ensure that utf8 is used by mysql */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows (I have found that the precise lines required seem to vary as time goes on)

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Also, you may give the apache user ownership of the site, this way, when you install, the script will be able to create the config.php file.
If you leave the owner as root, you will have to paste the suggested config.php into /var/www/html/moodle

To give apache ownership do

chown -R apache:apache /var/www/html/moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-04-10T12:01:59Z

T100ss: /* Fetch moodle */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Also, you may give the apache user ownership of the site, this way, when you install, the script will be able to create the config.php file.
If you leave the owner as root, you will have to paste the suggested config.php into /var/www/html/moodle

To give apache ownership do

chown -R apache:apache /var/www/html/moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-04-10T12:01:05Z

T100ss: /* Fetch moodle */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Also, you may give the apache user ownership of the site, this way, when you install, the script will be able to create the config.php file.
If you leave the owner as root, you will have to paste the suggested config.php into /var/www/html/moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Installation Guide for Installing on Amazon EC2

2012-04-10T11:27:00Z

T100ss: /* Set up MYSQL */

{{Installing Moodle}}
An ec2 instance is a virtual web server that can be rented out by the hour from Amazon. Prices vary depending on the power of the instance you rent out.

I recommend the following book for background reading on Amazon EC2 "Host Your Web Site in the Cloud: Amazon Web Services Made Easy
by Jeff Barr Copyright ©2010 Amazon Web Services" This is the official Amazon book on their web services and tells you how to set up a web server on an ec2 instance.

The instructions below are one way in which to set up Moodle on an EC2 instance.

==Rent an ec2 instance==

You can set up an account with Amazon Web Services and rent out a ec2 instance here [http://aws.amazon.com/console/ The Amazon Web Service Console]

I used an instance of the [http://aws.amazon.com/amazon-linux-ami/ Amazon Linux AMI] based on Elastic Block Store. Using an instance based on an Elastic Block Store gives you more options for backing up your disks later. The "[http://aws.amazon.com/amazon-linux-ami/ Amazon Linux AMI]" is based on CentOS and is a pared down version of linux with only the bare essentials included, that should be more secure. You can use the yum command to install anything extra necessary on your server.

===Attach an 'elastic ip' and open necessary ports on firewall===

Again through the [http://aws.amazon.com/console/ The Amazon Web Service Console] :

* I created and attached an elastic ip address to the ec2 instance I had launched with the [http://aws.amazon.com/amazon-linux-ami/ Amazon Linux AMI].
* I opened ports 22 and 80. For my purposes I did not intend to make the server accessible through https so these were sufficient.

You may want to map a domain name to point to your elastic IP address. You will need a dns provider to do this. Amazon does not provide this service at the time of writing.

==Connect to your ec2 instance with putty or another ssh client==

Through the [http://aws.amazon.com/console/ The Amazon Web Service Console] you can set up an ssh key and attach it to the ec2 instance you have running.

Your username for an ec2 instance using the Linux AMI will be ec2-user and no password will be required if you have the private key set up correctly.

===Accessing ec2 instance using putty ssh client===

In order for this key to work with putty on Windows you need to import it using puttygen and then save the private key in a safe location possibly with a pass phrase (local password) to protect it. You can then associate the key file with the ssh connection in putty by opening settings in Connection/SSH/Auth and browsing for the correct 'Private Key for Authentication'

==Setting up a web server on Amazon Linux AMI==

Make sure all your currently installed packages are up to date.

sudo yum -y update

You use yum to install all the software you need on your server. You can use the following command to install apache, mysql and php and the php extensions and all dependencies required by Moodle with this command :

sudo yum -y install aspell aspell-en aspell-fr aspell-es cvs httpd mysql mysql-server php php-cli php-gd php-intl php-mbstring php-mysql php-pdo php-soap php-xml php-xmlrpc php-pspell

You can list all your installed packages (including dependencies) with this command :

sudo yum list installed

===Start server services and have them start up automatically on a reboot===

Configure the new services to start automatically.

sudo /sbin/chkconfig httpd on
sudo /sbin/chkconfig mysqld on

sudo /sbin/service httpd start
sudo /sbin/service mysqld start

===Edit httpd.conf===

If you need to edit httpd.conf it is in /etc/httpd/conf

But by default the directory /var/www/html/ is the root web directory and you can install Moodle in there.

If you do edit httpd.conf then you must restart apache using this command for the changes to take effect :

sudo /sbin/service httpd restart

==Set up MYSQL==

sudo mysqladmin -u root password 'new-password'

Make additional security-related changes to mysql. This can be done very easily with the command "mysql_secure_installation" and answering conservatively.

sudo mysql -u root -p

mysql> DROP DATABASE test; [removes the test database]
mysql> DELETE FROM mysql.user WHERE user = ''; [Removes anonymous access]
mysql> FLUSH PRIVILEGES;

==Install Moodle==

Now you need to :

* Install the version of Moodle required. I recommend using CVS to install Moodle. See [[CVS for Administrators]].
* Create Moodle site database
* [[Creating Moodle site data directory]]
* [[Cron#Using_the_crontab_program_on_Unix|Set up cron using crontab command]]

Install Moodle by going to http://youelasticipaddress/roottoyourmoodleserver/ (if you have set up a domain name to point to your elasticip address then you should use that of course)

Copy the config.php that the installer creates and then go to the root of your moodleserver and do :

sudo vi config.php

Then type i to put vi in insert mode and on putty you can use the right mouse key to paste the contents of the clipboard, then delete the former contents.

Then go again to the root of your Moodle installation http://youelasticipaddress/roottoyourmoodleserver/ and complete the automatic installation of your Moodle db.

Amazon EC2 Cloud Services Installation

2012-04-10T11:18:09Z

T100ss: /* Fetch and do permissions on moodle */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-04-10T11:17:35Z

T100ss: chown moodle not necessary for web site

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Talk:Installing Moodle on Debian based distributions

2012-02-15T08:01:51Z

T100ss:

TODO
Suggest that the mysql secure utility is used. I refer to it in my Amazon EC2 install page. Copy & paste from there.
Mention the various extra that need to be installed php-pear etc.
Test php by using a phpinfo page

Talk:Installing Moodle on Debian based distributions

2012-02-15T07:58:20Z

T100ss: Created page with "Suggest that the mysql secure utility is mentioned. I refer to it in my Amazon EC2 install page."

Suggest that the mysql secure utility is mentioned. I refer to it in my Amazon EC2 install page.

Amazon EC2 Cloud Services Installation

2012-01-31T08:52:01Z

T100ss: /* In order to make sure php is included when httpd comes up */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Do the same for ownership as you did for moodledata. The -R makes the chown (change owner) recursive.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-01-31T08:12:34Z

T100ss: /* In order to make sure php is included when httpd comes up */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589)
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Do the same for ownership as you did for moodledata. The -R makes the chown (change owner) recursive.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-01-29T11:21:14Z

T100ss: /* Fetch and do permissions on moodle */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589)
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.
Do the same for ownership as you did for moodledata. The -R makes the chown (change owner) recursive.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-01-29T11:20:03Z

T100ss: /* Fetch and do permissions on moodle */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589)
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-01-29T11:19:26Z

T100ss: /* Create moodledata folder */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589)
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a file called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-01-26T15:48:09Z

T100ss: /* In order to make sure php is included when httpd comes up */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589)
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a file called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-01-26T15:46:43Z

T100ss:

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here {http://moodle.org/mod/forum/discuss.php?d=194589]
Attached to a forum post.) Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a file called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Amazon EC2 Cloud Services Installation

2012-01-26T15:45:49Z

T100ss:

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli. Assumptions you have an Amazon 32 bit EC2 server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here {http://moodle.org/mod/forum/discuss.php?d=194589]
Attached to a forum post.) Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a file called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Talk:Amazon EC2 Cloud Services Installation

2012-01-26T15:36:23Z

T100ss:

This document followed from a post in Moodle forums the other day ~24th Jan 2008. I did a complete install and have written it up here whilst it was fresh in my mind.

You might choose to add at the beginning how to get the said services.
Also, this is not necessarily any good for a "live" moodle as the server does not stay "up" all the time and if you do not backup, it will forget stuff.

Amazon EC2 Cloud Services Installation

2012-01-26T15:34:56Z

T100ss: /* Fetch and do permissions on moodle */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to that category. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli. Assumptions you have an Amazon 32 bit EC2 server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here {http://moodle.org/mod/forum/discuss.php?d=194589]
Attached to a forum post.) Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a file called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.

There are more sophisticated git commands, see git docs in moodle docs for more info.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

Talk:Amazon EC2 Cloud Services Installation

2012-01-26T15:33:23Z

T100ss: Created page with "This document followed from a post in Moodle forums the other day ~24th Jan 2008. I did a complete install and have written it up here whilst it was fresh in my mind. You might ..."

Amazon EC2 Cloud Services Installation

2012-01-26T15:27:45Z

T100ss: /* Fetch and do permissions on moodle */

This is essentially a linux box in the cloud but at the time of writing I did not like to add it to that category. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli. Assumptions you have an Amazon 32 bit EC2 server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install php-mcrypt
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-zts
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

At the time of writing 26-01-2012) (php-common should provide zip.zo but it doesn't so I have put a copy here {http://moodle.org/mod/forum/discuss.php?d=194589]
Attached to a forum post.) Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.

chown apache:apache /var/www/moodledata

= Fetch and do permissions on moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

This should put all of moodle in a file called moodle in the correct folder /var/www/html

There are more sophisticated git commands, see git docs in moodle docs for more info.

chown -R apache:apache ./moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!