mirror_php/moodle
1
0
Fork 0
mirror of https://github.com/moodle/moodle.git synced 2025-02-01 21:54:04 +01:00
Code Issues Projects Releases Wiki Activity

Section 1-5 translated by Koen Roggemans

Browse Source
This commit is contained in:
koenr 2003-10-08 21:36:39 +00:00
parent 76e0168130
commit 95a1b0cc4e
1 changed files with 415 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

415
lang/nl/docs/install.html Normal file
View File

@ -0,0 +1,415 @@
<head>
<title>Moodle Documentatie: Installatie</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>Moodle Installeren</h1>
<blockquote>
<p>In deze gids vind je hoe je Moodle de eerste keer moet installeren. Soms wordt er in detail getreden
om de grote variëteit aan kleine verschillen tussen verschillende installaties van webservers. Zo lijkt dit
document lang en moeilijk. Laat je er niet door afschrikken - Moodle kan geïnstalleerd worden in enkele minuten!</p>
<p>Neem je tijd en werk je door dit document - het zal je later tijd besparen.</p>
<p>Sections in this document:</p>
<ol>
<li><a href="#requirements">Systeemvereisten</a></li>
<li><a href="#downloading">Download</a></li>
<li><a href="#site">Site structuur</a></li>
<li><a href="#data">Een gegevensmap maken</a></li>
<li><a href="#database">Een databank maken</a></li>
<li><a href="#webserver">Instellingen van de webserver controleren</a></li>
<li><a href="#config">Config.php bewerken</a></li>
<li><a href="#admin">Naar de admin pagina gaan</a></li>
<li><a href="#cron">Cron installeren</a></li>
<li><a href="#course">Een nieuw vak maken</a></li>
</ol>
<p>&nbsp;</p>
</blockquote>
<h3 class="sectionheading"><a name="requirements"></a>1. Systeemvereisten</h3>
<blockquote>
<p>De ontwikkeling van Moodle is gestart in Linux met Apache, MySQL en PHP (soms ook gekend onder de naam
LAMP platform), maar is ook grondig getest met PostgreSQL en op Windows XP, Mac OS X en Netware 6 besturingssystemen</p>
<p>De systeemvereisten zijn de volgende:</p>
<ol>
<li>Web server software. Meest gebruikt is <a href="http://www.apache.org/" target="_blank">Apache</a>,
maar Moodle zou ook goed moeten werken op gelijk welke webserver met ondersteuning voor PHP, zoals
IIS op Windows platforms.</li>
<li><a href="http://www.php.net/" target="_blank">PHP</a> scripting taal (version 4.1.0
or later), met volgende instellingen:
<ul>
<li><a href="http://www.boutell.com/gd/" target="_blank">GD library</a>
ingeschakeld, met ondersteuning voo JPG en PNG bestandsindeling</li>
<li>zlib library ingeschakeld (als je backup/restore op Windows wil gebruiken)</li>
<li>Sessions support ingeschakeld</li>
<li>Bestanden uploaden ingeschakeld</li>
<li>Safe Mode moet uitgeschakeld worden (raadpleeg de forums op moodle.org voor problemen
veroorzaakt door Safe Mode)</li>
</ul>
</li>
<li>een werkende databank server: <a href="http://www.mysql.com/" target="_blank">MySQL</a>
of <a href="http://www.postgresql.org/" target="_blank">PostgreSQL</a> zijn volledig ondersteund en aangeraden
voor het gebruik met Moodle 1.1. Alle andere databanken zullen volledig ondersteund worden in de volgende versie.</li>
</ol>
<p>De meeste web hosts ondesteunen dit allemaal standaard. Als je ingetekend hebt bij een van de weinige
webhosts die deze mogelijkheden niet ondersteunen, vraag hen dan waarom en overweeg om te verhuizen.
<p>Als je Moodle op je eigen computer wil laten lopen en dit lijkt je allemaal wat moeilijk, raadpleeg dan onze
gids: <a href="http://moodle.org/doc/?file=installamp.html">Installing
Apache, MySQL and PHP</a>. Die geeft stap voor stap informatie om dit te installeren op de meest gebruikte platforms.</p>
<p>&nbsp;</p>
</blockquote>
<h3 class="sectionheading"><a name="downloading"></a>2. Download</h3>
<blockquote>
<p>Er zijn twee manieren om Moodle te bekomen. als gecomprimeerd pakket en via CVS. Dit staat in detail uitgelegd
op de downloadpagina: <a href="http://moodle.org/download/" target="_blank">http://moodle.org/download/</a></p>
<p>Na het downloaden en het uitpakken van het gecomprimeerd bestand of na het uitchecken uit CVS, krijg je een
map &quot;moodle&quot;, die een hele reeks bestanden en mappen bevat. </p>
<p>Je kan de hele map in de documentenmap van je webserver kopiëren; in dat geval zal je site te vinden zijn via
<b>http://jouwdomein.com/moodle</b> of je kan heel de inhoud van die map recht in de documentenmap van je webserver
zetten, zodat je site gewoon <b>http://jouwdomein.com</b> zal zijn.</p>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="site"></a>3. Site structuur</h3>
<blockquote>
<p>Een kort overzicht van de inhoud van de Moodle map, om je te helpen oriënteren</p>
<blockquote>
<p>config.php - het ENIGE bestand dat bewerkt moet worden voor je kunt starten<br>
version.php - geeft de huidige versie van de Moodle programmatuur<br>
index.php - de startpagina van de site</p>
<ul>
<li>admin/ - code om de server te beheren </li>
<li>auth/ - modules om gebruikers te authenticeren </li>
<li>course/ - code om de vakken te tonen en te beheren </li>
<li>doc/ - help documentatie voor Moodle (bijvoorbeeld deze pagina)</li>
<li>files/ - code om geüploade pagina's te tonen</li>
<li>lang/ - teksten in verschillende talen, een map per taal</li>
<li>lib/ - bibliotheken met de kern van de Moodle code </li>
<li>login/ - code voor aanmelding en accountaanmaak </li>
<li>mod/ - alle vakmodules van Moodle</li>
<li>pix/ - stanaard afbeeldingen voor de site</li>
<li>theme/ - thema pakketten/skins om het uiterlijk van de site te wijzigen.</li>
<li>user/ - code gebuikers te tonen en te beheren</li>
</ul>
<p>&nbsp;</p>
</blockquote>
</blockquote>
<h3 class="sectionheading"><a name="data"></a>4. Een gegevensmap maken</h3>
<blockquote>
<p>Moodle zal wat ruimte op je harde schijf nodig hebben om geüploade bestanden te bewaren, zoals vak bestanden
en foto's van de gebruikers.</p>
<p>Maak ergens een map voor dit doel. Voor de veiligheid is het best dat deze map NIET rechtstreeks te bereiken
is via het web. De gemakkelijkste manier om dit te doen is door ze gewoon BUITEN de webmap te zetten. Anders
kun je de map ook beschermen door een bestandje te maken dat je .htaccess noemt en in die map plaatst. In dat
bestandje zet je volgende lijn
<blockquote>
<pre>deny from all</pre>
</blockquote>
<p>Om er zeker van te zijn dat Moodle bestanden kan uploaden naar deze map, kijk je best na of de webserver
(bijvoorbeeld Apache) het recht heeft om te schrijven in deze map. Voor Unixmachines betekent dit de instellingen
voor de eigenaar van de map op &quot;nobody&quaot; of &quot;apache&quot; zetten.</p>
<p>Op veel gedeelde hostinservers zul je waarschijnlijk alle bestandstoegang moeten beperken tot jouw groep
(om te verhinderen dat andere klanten van je host je bestanden kunnen komen bekijken en wijzigen), maar volledig
lezen en schrijvenrecht geven alle anderen (wat de webserver zal toelaten tot jouw bestanden) Spreek er over met
de beheerder van je server als je problemen hebt met dit veilig in te stellen.</p>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="database"></a>5. Een databank maken</h3>
<blockquote>
<p>Je moet een lega databank maken (bv "moodle") in je databanksysteem
samen met een speciale gebruiker (bv "moodleuser") die toegang heeft tot die databank
(en alleen die databank). Je kunt ook de "root" gebruiker nemen als je wil, maar dit is niet aan te raden
voor een productiesysteem: als hackers je wachtwoord kraken, dan is je hele databanksysteem in gevaar, anders
slechts één databank
</p>
<p>Voorbeeldcode voor 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>Voorbeeldcode voor 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>(Voor MySQL raad ik ten zeerste <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a>
aan voor het beheer van je databank - Je kunt dit dan allemaal doen via een webinterface).</p>
<p>Vanaf versie 1.0.8 ondersteunt Moodle tabelprefixen, zodat je veilig een databank kun delen met tabellen
van andere applicaties</p>
</blockquote>
<p>&nbsp;</p>
<h3 class="sectionheading"><a name="webserver" id="webserver"></a>6. Instellingen van de webserver controleren</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. Edit 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. Go to the admin page</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. Set up 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. Create a new course</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>