Installation de Moodle

De MoodleDocs
Révision datée du 30 juin 2012 à 12:35 par Thomas Canniot (discussion | contributions) (Suite de la traduction)
Aller à :navigation, rechercher

Remarque : la traduction de cette page n'est pas terminée. N'hésitez pas à traduire tout ou partie de cette page ou à la compléter. Vous pouvez aussi utiliser la page de discussion pour vos recommandations et suggestions d'améliorations.


Ne paniquez pas ! Fichier:F1 35px.png

Cette page explique de quelle manière installer Moodle. Moodle fonctionne sur un nombre important de configurations que nous allons presque toutes abordées dans cette page. Veuillez prendre le temps de chercher et lire les parties qui vous concernent le plus.

Planification

Installer Moodle nécessite de planifier un minimum les choses, en fonction de l'importance de l'installation que vous vous apprêtez à réaliser. Voici quelques pistes que vous pourriez envisager :

  • Souhaitez-vous vraiment installer Moodle par vous-même ? Consultez Finding and Selecting A Web Host.
  • De quelles compétences disposez-vous et êtes-vous prêt à apprendre ? Administrer un serveur web sécurisé et stable est une entreprise sérieuse avant même d'envisager installer Moodle. Cette documentation prend le parti que vous disposez d'un minimum de connaissance de la plateforme sur laquelle vous vous apprêtez à installer Moodle (ou que vous êtes prêts à apprendre certaines choses).
  • Quelle est la configuration nécessaire pour le matériel et la solution d'hébergement ? Moodle s'adapte facilement, mais en fonction de la configuration dont vous avez besoin, vous pourriez être intéressé par différentes solutions : l'hébergement mutualisé, un serveur virtuel dédié, votre propre serveur web, votre propre installation de plusieurs serveurs web.
  • Quelle plateforme logicielle allez-vous utiliser ? Cela dépend de vos compétences ou de la politique ayant trait dans votre entreprise ou votre institution. Vous avez peut-être la possibilité de faire vous-même le choix.
  • Quelles sont vos besoins en termes de support ? Est-ce que le support gratuit et communautaire de Moodle.org sera suffisant ou avez-vous besoin d'un support professionnel ?
  • Comment allez-vous organiser les sauvegardes ?

Configuration nécessaire

Moodle est principalement développée pour fonctionner sous un environnement Linux Apache, MySQL et PHP (parfois appelée la plateforme LAMP). En cas de doute, il s'agit du choix le plus sûr à faire (en plus d'être la plus répandue). Vous trouverez d'autres options possibles dans la section Logiciel qui suit.

La configuration recommandée de base pour Moodle est la suivante :

Matériel

  • Espace disque : 160Mo de libre (minimum) et autant que nécessaire en fonction de vos besoins de stockage. 5go nous paraît être un minimum réaliste.
  • Sauvegarde : au moins la même quantité d'espace disque que ci-dessus, sur une unité de stockage différente pour conserver une sauvegarde de votre site.
  • Mémoire : 256Mo (minimum), 1Go ou plus est fortement recommandé. La règle générale est que Moodle peut prendre en charge de 10 à 20 utilisateurs simultanément par giga-octet de RAM disponible, mais cela varie en fonction du matériel et du logiciel que vous avez choisis ainsi que du type d'utilisation. « Simultanément » signifie des process du serveur web en mémoire qui travaillent en même temps (c'est à dire des utilisateurs qui interagissent avec le système dans une fenêtre de quelques secondes), ce qui est DIFFÉRENT du nombre d'utilisateurs CONNECTÉS.

Logiciel

  • Un système d'exploitation (!). Tout système capable de faire fonctionner les logiciels suivants. Bien que le choix dépendra des performances recherchées et des compétences disponibles. Linux et Windows restent les choix les plus populaires (et pour lesquels un support est disponible). Si vous êtes libre du choix, Linux est généralement reconnu comme une plateforme optimale. Moodle est aussi régulièrement testé sur les systèmes d'exploitation Windows XP/2000/2003, Solaris 10 (Sparc et x64), Mac OS server et Netware 6.
  • Un serveur web. Principalement Apache ou IIS. Moodle n'est pas entièrement testé (mais devrait fonctionner) avec lightttpd, nginx, cherokee, zeus et LiteSpeed. Moodle refusera de s'installer sur d'autres serveurs web. Votre serveur web devra être correctement configuré pour interpréter les fichiers PHP. Le numéro de la version n'est pas critique mais essayez d'utiliser le serveur web dans sa version la plus récente que vous ayez à disponisition.
  • PHP - The minimum version is currently 5.3.2. A number of extensions are required; see the PHP page for full details. Installation will halt at the environment check if any of the required extensions are missing.
  • A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (note that optional plugins may be untested with these databases) but documentation and online help are not as comprehensive as MySQL/PostgreSQL. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.

Client

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

Also read....

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

Set up your server

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

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 maxmimums). 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 three basic options:

  • Download your required version from http://moodle.org/downloads and unzip/unpack...
  • OR Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):
$ git clone -b MOODLE_22_STABLE git://git.moodle.org/moodle.git 

...this fetches a complete copy of the Moodle repository and then switches to the 2.2 Stable branch (latest weekly build). For a fuller discussion see Git for Administrators.

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

You can either place the whole folder in your web server documents directory, in which case the site will be located at http://yourwebserver.com/moodle, or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply http://yourwebserver.com. 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):
# chown -R root /path/to/moodle
# chmod -R 0755 /path/to/moodle

(files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)

Create an empty database

Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:

  • dbhost - the database server hostname. Probably localhost if the database and web server are the same machine, otherwise the name of the database server
  • dbname - the database name. Whatever you called it, e.g. moodle
  • dbuser - the username for the database. Whatever you assigned, e.g. moodleuser - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
  • dbpass - the password for the above user

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

Create the (moodledata) data directory

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

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

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

# mkdir /path/to/moodledata
# chmod 0777 /path/to/moodledata

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:

order deny,allow
deny from all

Start Moodle install

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

Command line installer

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

  • Example of using the command-line installer (as root - substitute 'www-data' for your web user):
# 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

The chowns allow the script to write a new config.php file. More information about the options can be found using

# php install.php --help

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

Web based installer

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

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

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

Final configuration

Settings within Moodle

There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:

  • Settings > Site administration > Server > Email: Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
  • Settings > Site administration > Server > System paths: Set the paths to du, dot and aspell binaries.
  • Settings > Site administration > Server > HTTP: If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
  • Settings > Site administration > Location > Update timezones: Run this to make sure your timezone information is up to date.

Remaining tasks

  • Configure Cron: Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the Cron instructions.
  • Set up backups: See Site backup and Automated course backup.
  • Check mail works: Create a test user with a valid email address and 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.
  • Secure your Moodle site: Read the Security recommendations.

Installation is complete :)

If something goes wrong...

Here are some things you should try...

  • Check the Installation FAQ
  • Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?
  • Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?
  • If you are having trouble creating a config.php file, you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place.
  • Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).
  • Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?
  • Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).
  • Explain your problem in the 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.

See also