mirror_php/moodle
1
0
Fork 0
mirror of https://github.com/moodle/moodle.git synced 2025-01-21 07:28:31 +01:00
Code Issues Projects Releases Wiki Activity
moodle/lang/fr/docs/install.html
martignoni 7e8d372a4e Partial translation
2003-10-08 21:14:41 +00:00

429 lines
23 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!-- Ce fichier est en cours de traduction. Il sera mis ý jour petit ý petit -->
<head>
<title>Documentation Moodle : Installation</title>
<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="#FFFFFF">
<h1>Installation de Moodle</h1>
<blockquote>
<p>Ce document explique une premiËre installation de Moodle. Certaines Ètapes sont
dÈcrites en dÈtails, afin de couvrir la grande variÈtÈ des petites particularitÈs des
diffÈrents serveurs web. C'est pourquoi ce document vous semblera peut-Ítre long et compliquÈ.
Ne vous laissez pas dÈcourager pour autant - la mise en place de Moodle est d'habitude
une affaire de minutes !</p>
<p>Prenez le temps d'Ètudier attentivement ces instructions - cela vous fera gagner du temps
tÙt ou tard.</p>
<p>Voici les diffÈrentes sections de ce document :</p>
<ol>
<li><a href="#requirements">Logiciels et rÈglages nÈcessaires</a></li>
<li><a href="#downloading">TÈlÈchargement</a></li>
<li><a href="#site">Structure du site</a></li>
<li><a href="#data">CrÈer un rÈpertoire de donnÈes</a></li>
<li><a href="#database">CrÈer une base de donnÈes</a></li>
<li><a href="#webserver">VÈrifier les rÈglages de votre serveur web</a></li>
<li><a href="#config">Modifier config.php</a></li>
<li><a href="#admin">Visiter la page d'administration</a></li>
<li><a href="#cron">Mettre en place un cron</a></li>
<li><a href="#course">CrÈer un nouveau cours</a></li>
</ol>
<p>&nbsp;</p>
</blockquote>
<h3 class="sectionheading"><a name="requirements"></a>1. Logiciels et rÈglages nÈcessaires</h3>
<blockquote>
<p>Moodle est principalement dÈveloppÈ sur Linux avec Apache, MySQL et PHP (environnement
appelÈ parfois plateforme LAMP), mais est aussi testÈ rÈguliËrement avec PostgreSQL
et sur les systËmes d'exploitation Windows XP, Mac OS X et Netware 6.</p>
<p>Les logiciels et rÈglages nÈcessaires pour Moodle sont les suivants :</p>
<ol>
<li>Logiciel serveur web. La plupart des gens utilisent <a href="http://www.apache.org/"
target="_blank">Apache</a>, mais Moodle devrait fonctionner tout aussi bien avec n'importe
quel serveur web compatible avec PHP, comme IIS sur les plateformes Windows.</li>
<li>Le langage <a href="http://www.php.net/" target="_blank">PHP</a> (version 4.1.0
ou ultÈrieure), avec les rÈglages suivants :
<ul>
<li>la librairie <a href="http://www.boutell.com/gd/" target="_blank">GD</a>,
installÈe et active (ON), supportant les formats JPG et PNG ;</li>
<li>la librairie zlib installÈe et active (ON), si vous voulez faire des backups
et les restaurer sous Windows ;</li>
<li>support pour les sessions actif (ON) ;</li>
<li>le dÈpÙt (upload) de fichiers actif (ON) ;</li>
<li>le mode ´&nbsp;Safe Mode&nbsp;ª doit Ítre inactif (OFF) (voir les forums sur moodle.org pour
les problËmes causÈs par le mode ´&nbsp;Safe Mode&nbsp;ª.</li>
</ul>
</li>
<li>Un serveur de base de donnÈes : <a href="http://www.mysql.com/" target="_blank">MySQL</a>
ou <a href="http://www.postgresql.org/" target="_blank">PostgreSQL</a> sont complËtement
supportÈs et recommandÈs pour Ítre utilisÈs avec Moodle 1.1. D'autres bases de donnÈes
seront pleinement supportÈes dans la prochaine version.</li>
</ol>
<p>La plupart des hÙtes web proposent tout cela par dÈfaut. Si vous vous Ítes engagÈ
auprËs d'un hÙte web qui n'offre pas ces logiciels, demandez-lui pourquoi, et
envisagez de changer d'hÈbergement.</p>
<p>Si vous voulez faire fonctionner Moodle sur votre propre ordinateur et que cela vous
fait un peu peur, lisez notre guide <a href="http://moodle.org/doc/?file=installamp.html">
Installation d'Apache, MySQL et PHP</a>. Ce document offre quelques pas-ý-pas pour
l'installation de ces logiciels sur la plupart des plateformes.</p>
<p>&nbsp;</p>
</blockquote>
<h3 class="sectionheading"><a name="downloading"></a>2. TÈlÈchargement</h3>
<blockquote>
<p>Il y a deux faÁons d'obtenir Moodle : par tÈlÈchargement d'un fichier compressÈ ou
ý l'aide du CVS. Toutes deux sont expliquÈes en dÈtail sur la page de tÈlÈchargement
<a href="http://moodle.org/download/" target="_blank">http://moodle.org/download/</a>.</p>
<p>AprËs avoir tÈlÈchargÈ et dÈcompressÈ l'archive ou obtenu les fichiers par CVS,
vous aurez sous les yeux un dossier nommÈ ´&nbsp;moodle&nbsp;ª, contenant un certain nombre de dossiers
et de fichiers.</p>
<p>Vous pouvez placer ce dossier intÈgralement dans le dossier documents de votre serveur
web. Dans ce cas, le site Moodle sera accessible ý l'adresse <b>http://votreserveur.com/moodle/</b>.
Vous pouvez aussi copier le contenu de ce dossier dans le dossier documents de votre serveur.
Dans ce cas, le site Moodle sera accessible simplement ý l'adresse <b>http://votreserveur.com/</b>.</p>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="site"></a>3. Structure du site</h3>
<blockquote>
<p>Voici une bref aperÁu du contenu du dossier Moodle, afin de vous permettre de ne pas
vous perdre :</p>
<blockquote>
<p>config.php - l'UNIQUE fichier ý modifier pour faire fonctionner votre site<br />
version.php - indique la version actuelle du programme Moodle<br />
index.php - la page d'accueil du site</p>
<ul>
<li>admin/ - programmes pour l'administration du serveur </li>
<li>auth/ - modules pour l'authentification des utilisateurs </li>
<li>course/ - programmes pour l'affichage et la gestion des cours </li>
<li>doc/ - documentation et fichiers d'aide de Moodle (p. ex. cette page) </li>
<li>files/ - programmes pour l'affichage et la gestion des fichiers dÈposÈs </li>
<li>lang/ - textes dans les diffÈrentes langues, un dossier par langue </li>
<li>lib/ - librairies pour le coeur du programme Moodle </li>
<li>login/ - programmes de gestion du login et la crÈation des comptes </li>
<li>mod/ - tous les modules de cours Moodle </li>
<li>pix/ - les images et graphiques gÈnÈriques du site </li>
<li>theme/ - diffÈrents thËmes pour changer l'aspect de votre site </li>
<li>user/ - programmes pour afficher et gÈrer les utilisateurs </li>
</ul>
<p>&nbsp;</p>
</blockquote>
</blockquote>
<h3 class="sectionheading"><a name="data"></a>4. CrÈer un rÈpertoire de donnÈes</h3>
<blockquote>
<p>Moodle aura Ègalement besoin d'espace sur votre disque dur pour conserver les
fichiers dÈposÈs par les utilisateurs, comme les documents de cours ou les photos
des utilisateurs.</p>
<p>CrÈez quelque part ý cet effet un dossier. Par sÈcuritÈ, ce dossier NE DOIT PAS
Ítre accessible directement depuis le web. La maniËre la plus simple d'obtenir cela est
de le crÈer EN DEHORS du rÈpertoire web. Sinon, vous pouvez protÈger ce dossier en y
plaÁant un fichier nommÈ ´&nbsp;.htaccess&nbsp;ª, contenant cette ligne :</p>
<blockquote>
<pre>deny from all</pre>
</blockquote>
<p>Faites en sorte que le logiciel serveur (p. ex. Apache) ait les privilËges pour
Ècrire dans ce dossier, afin que Moodle puisse enregistrer les fichiers dÈposÈs. Sur les
ordinateurs UNIX, cela signifie que le possesseur du dossier en question soit quelque
chose comme ´&nbsp;nobody&nbsp;ª, ´&nbsp;www&nbsp;ª ou ´&nbsp;apache&nbsp;ª.</p>
<p>Sur la plupart des serveurs web, vous devrez probablement restreindre ý votre
´&nbsp;groupe&nbspª tous les accËs ý vos fichiers (afin d'Èviter que d'autres utilisateurs
du mÍme fournisseur puissent voir ou modifier vos fichiers), mais accorder les droits
de lecture et d'Ècriture ý tous les autres utilisateurs (ce qui permettra au serveur web
d'accÈder ý vos fichiers). Si vous avez des difficultÈs ý gÈrer proprement cela,
parlez-en ý l'administrateur de votre serveur web.</p>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="database"></a>5. CrÈer une base de donnÈes</h3>
<!-- Le reste doit encore Ítre traduit -->
<blockquote>
<p>You need to create an empty database (eg "moodle") in your database system
along with a special user (eg "moodleuser") that has access to that database
(and that database only). You could use the "root" user if you wanted to, but
this is not recommended for a production system: if hackers manage to discover
the password then your whole database system would be at risk, rather than
just one database.
</p>
<p>Example command lines for MySQL: </p>
<pre>
# mysql -u root -p
> CREATE DATABASE moodle;
> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.*
TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
> quit
# mysqladmin -p reload
</pre>
<p>Example command lines for PostgreSQL: </p>
<pre>
# su - postgres
> psql -c "create user moodleuser createdb;" template1
> psql -c "create database moodle;" -U moodleuser template1
> psql -c "alter user moodleuser nocreatedb;" template1
</pre>
<p>(For MySQL I highly recommend the use of <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a>
to manage your databases - you can do all this via a web interface).</p>
<p>As of version 1.0.8, Moodle now supports table prefixes, and so can safely share
a database with tables from other applications.</p>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="webserver" id="webserver"></a>6. VÈrifier les rÈglages de votre serveur web</h3>
<blockquote>
<p>Firstly, make sure that your web server is set up to use index.php as a default
page (perhaps in addition to index.html, default.htm and so on).</p>
<p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf
file. Mine usually looks like this:</p>
<blockquote>
<pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>
</blockquote>
<p>Just make sure index.php is in the list (and preferably towards the start
of the list, for efficiency).</p>
<p>Secondly, <b>if you are using Apache 2</b>, then you should turn on the <i>AcceptPathInfo</i>
variable, which allows scripts to be passed arguments like http://server/file.php/arg1/arg2.
This is essential to allow relative links between your resources, and also
provides a performance boost for people using your Moodle web site. You can
turn this on by adding these lines to your httpd.conf file.</p>
<blockquote>
<pre><strong>AcceptPathInfo</strong> on </pre>
</blockquote>
<p>Thirdly, Moodle requires a number of PHP settings to be active for it to
work. <b>On most servers these will already be the default settings.</b>
However, some PHP servers (and some of the more recent PHP versions) may
have things set differently. These are defined in PHP's configuration
file (usually called php.ini):</p>
<blockquote>
<pre>magic_quotes_gpc = 1 (preferred but not necessary)
magic_quotes_runtime = 0 (necessary)
file_uploads = 1
session.auto_start = 0
session.bug_compat_warn = 0
</pre>
</blockquote>
<p>If you don't have access to httpd.conf or php.ini on your server, or you
have Moodle on a server with other applications that require different settings,
then don't worry, you can still OVERRIDE all of the default settings.
<p>To do this, you need to create a file called <b>.htaccess</b> in Moodle's
main directory that contains definitions for these settings.
This only works on Apache servers and only when Overrides have been allowed.
<blockquote>
<pre>
DirectoryIndex index.php index.html index.htm
&lt;IfDefine APACHE2>
<b>AcceptPathInfo</b> on
&lt;/IfDefine>
php_flag magic_quotes_gpc 1
php_flag magic_quotes_runtime 0
php_flag file_uploads 1
php_flag session.auto_start 0
php_flag session.bug_compat_warn 0</pre>
</blockquote>
<p>You can also do things like define the maximum size for uploaded files:
<blockquote>
<pre>
LimitRequestBody 0
php_value upload_max_filesize 2M
php_value post_max_size 2M
</pre>
</blockquote>
<p>The easiest thing to do is just copy the sample file from lib/htaccess
and edit it to suit your needs. It contains further instructions. For
example, in a Unix shell:
<blockquote>
<pre>cp lib/htaccess .htaccess</pre>
</blockquote>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="config"></a>7. Modifier config.php</h3>
<blockquote>
<p>Now you can edit the configuration file, <strong>config.php</strong>, using a
text editor. This file is used by all other files in Moodle.</p>
<p>To start with, make a copy of <strong>config-dist.php</strong> and name it
config.php. We do this so that your config.php won't be overwritten in case
you upgrade Moodle later on. </p>
<p>Edit <strong>config.php</strong> to specify the database details that you
just defined (including a table prefix - notice that this is REQUIRED for
PostgreSQL), as well as the site address, file system directory and data directory.
The config file itself has detailed directions and examples.</p>
<p>Once you have done this the rest of the installation is via a web interface.
For the rest of this installation document we will assume your site is at:
<u>http://example.com/moodle</u></p>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="admin"></a>8. Visiter la page d'administration</h3>
<blockquote>
<p>The admin page should now be working at: <u>http://example.com/moodle/admin</u>.
If you try and access the front page of your site you'll be taken there automatically
anyway. The first time you access this admin page, you will be presented with
a GPL &quot;shrinkwrap&quot; agreement with which you must agree before you
can continue with the setup.</p>
<p>(Moodle will also try to set some cookies in your browser. If you have your
browser set up to let you choose to accept cookies, then you <b>must</b> accept
the Moodle cookies, or Moodle won't work properly.)
<p>Now Moodle will start setting up your database and creating tables to store
data. Firstly, the main database tables are created. You should see a number
of SQL statements followed by status messages (in green or red) that look
like this:</p>
<blockquote>
<p>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category
int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default
'', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT
NULL default '', summary text NOT NULL, format tinyint(4) NOT NULL default
'1', teacher varchar(100) NOT NULL default 'Teacher', startdate int(10)
unsigned NOT NULL default '0', enddate int(10) unsigned NOT NULL default
'0', timemodified int(10) unsigned NOT NULL default '0', PRIMARY KEY (id))
TYPE=MyISAM</p>
<p><font color="#006600">SUCCESS</font></p>
<p>...and so on, followed by: <font color="#006600">Main databases set up
successfully.</font> </p>
</blockquote>
<p>If you don't see these, then there must have been some problem with the database
or the configuration settings you defined in config.php. Check that PHP isn't
in a restricted "Safe Mode" (commercial web hosts sometimes have safe mode
turned on). You can check PHP variables by creating a little file containing
&lt? phpinfo() ?&gt and looking at it through a browser. Check all these and
try this page again.</p>
<p>Scroll down the very bottom of the page and press the &quot;Continue&quot;
link.</p>
<p>Next you will see a similar page that sets up all the tables required by
each Moodle module. As before, they should all be <font color="#006600">green</font>.</p>
<p>Scroll down the very bottom of the page and press the &quot;Continue&quot;
link.</p>
<p>You should now see a form where you can define more configuration variables
for your installation, such as the default language, SMTP hosts and so on.
Don't worry too much about getting everything right just now - you can always
come back and edit these later on using the admin interface. Scroll down to
the bottom and click &quot;Save changes&quot;.</p>
<p>If (and only if) you find yourself getting stuck on this page, unable to
continue, then your server probably has what I call the "buggy referrer" problem.
This is easy to fix: just turn off the &quot;secureforms&quot; setting, then
try to continue again.</p>
<p>The next page is a form where you can define parameters for your Moodle site
and the front page, such as the name, format, description and so on. Fill
this out (you can always come back and change these later) and then press
&quot;Save changes&quot;.</p>
<p>Finally, you will then be asked to create a top-level administration user
for future access to the admin pages. Fill out the details with your own name,
email etc and then click &quot;Save changes&quot;. Not all the fields are
required, but if you miss any important fields you'll be re-prompted for them.
</p>
<blockquote>
<blockquote>
<blockquote>
<blockquote>
<blockquote>
<p><strong>Make sure you remember the username and password you chose
for the administration user account, as they will be necessary to
access the administration page in future.</strong></p>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<p>(If for any reason your install is interrupted, or there is a system error
of some kind that prevents you from logging in using the admin account, you
can usually log in using the default username of &quot;<strong>admin</strong>&quot;,
with password &quot;<strong>admin</strong>&quot;.)</p>
<p>Once successful, you will be returned to home page of your site. Note the
administration links that appear down the left hand side of the page (these
items also appear on a separate Admin page) - these items are only visible
to you because you are logged in as the admin user. All your further administration
of Moodle can now be done using this menu, such as:</p>
<ul>
<li>creating and deleting courses</li>
<li>creating and editing user accounts</li>
<li>administering teacher accounts</li>
<li>changing site-wide settings like themes etc</li>
</ul>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="cron"></a>9. Mettre en place un cron</h3>
<blockquote>
<p>Some of Moodle's modules require continual checks to perform tasks. For example,
Moodle needs to check the discussion forums so it can mail out copies of posts
to people who have subscribed.</p>
<p>The script that does all this is located in the admin directory, and is called
cron.php. However, it can not run itself, so you need to set up a mechanism
where this script is run regularly (eg every five or ten minutes). This provides
a &quot;heartbeat&quot; so that the script can perform functions at periods
defined by each module.</p>
<p>Note that the machine performing the cron <b>does not need to be the same
machine that is running Moodle</b>. For example, if you have a limited web
hosting service that does not have cron, then you can might choose to run
cron on another server or on your home computer. All that matters is that
the cron.php file is called regularly. </p>
<p>The load of this script is not very high, so 5 minutes is usually reasonable,
but if you're worried about it you can reduce the time period to something
like 15 minutes or even 30 minutes. It's best not to make the time period
too long, as delaying mail-outs can slow down activity within the course.</p>
<p>First, test that the script works by running it directly from your browser:</p>
<blockquote>
<pre>http://example.com/moodle/admin/cron.php</pre>
</blockquote>
<p>Now, you need to set up some of way of running the script automatically and
regularly. </p>
<h4> Running the script from a command line</h4>
<p>You can call the page from the command line just as you did in the example
above. For example, you can use a Unix utility like 'wget':</p>
<blockquote>
<pre>wget -q -O /dev/null http://example.com/moodle/admin/cron.php</pre>
</blockquote>
<p>Note in this example that the output is thrown away (to /dev/null).</p>
<p>The same thing using lynx:</p>
<blockquote>
<pre>lynx -dump http://example.com/moodle/admin/cron.php &gt; /dev/null</pre>
</blockquote>
<p>Alternatively you could use a standalone version of PHP, compiled to be run
on the command line. The advantage with doing this is that your web server
logs aren't filled with constant requests to cron.php. The disadvantage is
that you need to have access to a command-line version of php.</p>
<blockquote>
<pre>/opt/bin/php /web/moodle/admin/cron.php
(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
</pre>
</blockquote>
<h4>Automatically running the script every 5 minutes</h4>
<p><b>On Unix systems</b>: Use <b>cron</b>. Edit your cron settings from the commandline
using &quot;crontab -e&quot; and add a line like:</p>
<blockquote>
<pre>*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php</pre>
</blockquote>
<p>Usually, the "crontab" command will put you into the 'vi' editor. You enter
"insert mode" by pressing "i", then type in the line as above, then exit insert mode by
pressing ESC. You save and exit by typing ":wq", or quit with saving using ":q!" (without the quotes).</p>
<p><b>On Windows systems</b>: The simplest way is to use this little package <a href="http://moodle.org/download/moodle-cron-for-windows.zip" title="Click to download this package (150k)" target="_blank">moodle-cron-for-windows.zip</a>
which makes this whole thing very easy. You can also explore using the built-in
Windows feature for "Scheduled Tasks".</p>
<p>On web hosts: Your web-based control panel may have a web page that allows
you to set up this cron process. Ask your administrator for details on how
it works.</p>
<p></p>
</blockquote>
<h3 class="sectionheading"><a name="course"></a>10. CrÈer un nouveau cours</h3>
<blockquote>
<p>Now that Moodle is running properly, you can create a course. </p>
<p>Select &quot;Create a new course&quot; from the Admin page (or the admin
links on the home page).</p>
<p>Fill out the form, paying special attention to the course format. You don't
have to worry about the details too much at this stage, as everything can
be changed later by the teacher.</p>
<p>Press &quot;Save changes&quot;, and you will be taken to a new form where
you can assign teachers to the course. You can only add existing user accounts
from this form - if you want to create a new teacher account then either ask
the teacher to create one for themselves (see the login page), or create one
for them using the &quot;Add a new user&quot; on the Admin page.</p>
<p>Once done, the course is ready to customise, and is accessible via the &quot;Courses&quot;
link on the home page.</p>
<p>See the &quot;<a href="./?file=teacher.html">Teacher Manual</a>&quot; for more details
on course-building.</p>
</blockquote>
<p>&nbsp;</p>
<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
<p align="CENTER"><font size="1">Version: $Id$</font></p>
</body>
Reference in New Issue View Git Blame Copy Permalink