lang/en_utf8/help/install.html

   1 <h1>Installing Moodle</h1>
   2 <h2>Don't panic! <img src="http://moodle.org/pix/s/smiley.gif" alt="" /></h2>
   3 <blockquote>
   4   <p>This guide explains how to install Moodle for the first time.  For some of these steps it goes into a lot of detail to try and cover the majority of possible
   5      web server setups, so this document may look long and complicated.  Don't panic, once you know how to do it you can install Moodle in minutes!</p>
   6   <p>If you have problems please read this document carefully - most common issues are answered in here.
   7      If you still have trouble, you can seek help from
   8    <a href="http://moodle.org/help">Moodle Help</a></p>
   9   <p>Another option is to contact a <a href="http://moodle.com/hosting/">web hosting company</a>
  10      who can completely maintain Moodle for you, so that you can ignore all this and get straight into educating!
  11 </p>
  12   <p>&nbsp;  </p>
  13   <p>Sections in this document:</p>
  14   <ol>
  15     <li><a href="#requirements">Requirements</a></li>
  16     <li><a href="#downloading">Download and copy files into place</a> </li>
  17     <li><a href="#site">Site structure</a></li>
  18     <li><a href="#installer">Run the installer script to create config.php</a>      <ul>
  19         <li><a href="#webserver">Check web server settings</a></li>
  20         <li><a href="#database">Creating a database</a></li>
  21         <li><a href="#data">Creating a data directory</a></li>
  22         </ul>
  23     </li>
  24     <li><a href="#admin">Go to the admin page to continue configuration</a></li>
  25     <li><a href="#cron">Set up cron</a></li>
  26     <li><a href="#course">Create a new course</a></li>
  27      </ol>
  28   <p>&nbsp;</p>
  29 </blockquote>
  30 <h3 class="sectionheading" id="requirements">1. Requirements</h3>
  31 <blockquote>
  32   <p>Moodle is primarily developed in Linux using Apache, MySQL and PHP (also
  33     sometimes known as the LAMP platform), but is also regularly tested with PostgreSQL
  34     and on Windows XP, Mac OS X and Netware 6 operating systems</p>
  35   <p>The requirements for Moodle are as follows:</p>
  36   <ol>
  37     <li>Web server software. Most people use <a href="http://www.apache.org/" >Apache</a>,
  38       but Moodle should work fine under any web server that supports PHP, such
  39       as IIS on Windows platforms.</li>
  40     <li><a href="http://www.php.net/">PHP</a> scripting language (version 4.1.0
  41       or later). PHP 5 is supported as of Moodle 1.4. </li>
  42     <li>a working database server: <a href="http://www.mysql.com/">MySQL</a>
  43       or <a href="http://www.postgresql.org/">PostgreSQL</a> are
  44       completely supported and recommended for use with Moodle. </li>
  45   </ol>
  46   <p>Most web hosts support all of this by default. If you are signed up with
  47     one of the few webhosts that does not support these features ask them why,
  48     and consider taking your business elsewhere.</p>
  49   <p>If you want to run Moodle on your own computer and all this looks a bit daunting,
  50     then please take a look at <a href="http://docs.moodle.org/en/Administrator_documentation">the administrator documentation</a>.</p>
  51   <p>&nbsp;</p>
  52 </blockquote>
  53 <h3 class="sectionheading" id="downloading">2. Download and copy files into place </h3>
  54 <blockquote>
  55   <p>There are two ways to get Moodle, as a compressed package and via CVS. These
  56     are explained in detail on the download page: <a href="http://moodle.org/download/">http://moodle.org/download/</a></p>
  57   <p>After downloading and unpacking the archive, or checking out the files via
  58     CVS, you will be left with a directory called &quot;moodle&quot;, containing
  59     a number of files and folders.</p>
  60   <p>You can either place the whole folder in your web server documents directory,
  61     in which case the site will be located at <b>http://yourwebserver.com/moodle</b>,
  62     or you can copy all the contents straight into the main web server documents
  63     directory, in which case the site will be simply <b>http://yourwebserver.com</b>.</p>
  64   <p>If you are downloading Moodle to your local computer and then uploading it to your web site, it is usually better to upload the whole archive as one file, and then do the unpacking on the server. Even web hosting interfaces like Cpanel allow you to uncompress archives in the &quot;File Manager&quot;. </p>
  65 </blockquote>
  66 <p>&nbsp;</p>
  67 <h3 class="sectionheading" id="site">3. Site structure</h3>
  68 <blockquote>
  69   <p>You can safely skip this section, but here is a quick summary of the contents of the Moodle folder, to help get
  70     you oriented:</p>
  71   <blockquote>
  72     <table><tr>
  73       <td valign="top">config.php</td>
  74       <td valign="top">-</td>
  75       <td valign="top">
  76         contains basic settings. This file does not come with Moodle - you will create it. </td>
  77     </tr>
  78       <tr>
  79         <td valign="top">install.php</td>
  80         <td valign="top">-</td>
  81         <td valign="top">the script you will run to create config.php </td>
  82       </tr>
  83       <tr><td valign="top">version.php</td>
  84       <td valign="top">-</td>
  85       <td valign="top">
  86         defines the current version of Moodle code
  87       </td></tr>
  88       <tr><td valign="top">index.php</td>
  89       <td valign="top">-</td>
  90       <td valign="top">
  91         the front page of the site
  92       </td></tr></table>
  93     <ul>
  94       <li>admin/ - code to administrate the whole server </li>
  95       <li>auth/ - plugin modules to authenticate users </li>
  96       <li>blocks/ - plugin modules for the little side blocks on many pages</li>
  97       <li>calendar/ - all the code for managing and displaying calendars</li>
  98       <li>course/ - code to display and manage courses </li>
  99       <li>doc/ - help documentation for Moodle (eg this page)</li>
 100       <li>files/ - code to display and manage uploaded files</li>
 101       <li>lang/ - texts in different languages, one directory per language </li>
 102       <li>lib/ - libraries of core Moodle code </li>
 103       <li>login/ - code to handle login and account creation </li>
 104       <li>mod/ - all the main Moodle course modules are in here </li>
 105       <li>pix/ - generic site graphics</li>
 106       <li>theme/ - theme packs/skins to change the look of the site.</li>
 107       <li>user/ - code to display and manage users</li>
 108     </ul>
 109     <p>&nbsp;</p>
 110   </blockquote>
 111 </blockquote>
 112 <h3 class="sectionheading" id="installer">4. Run the Installer script to create config.php </h3>
 113 <blockquote>
 114   <p>To run the installer script (install.php), just try to access your Moodle main URL using a web browser, or access <strong>http://yourserver/install.php</strong> directly. </p>
 115   <p>(The Installer will try to set a session cookie. If you get a popup warning in your browser make sure you accept that cookie!) </p>
 116   <p>Moodle will detect that configuration is necessary and will lead you through some screens to help you create a new configuration file called <strong>config.php. </strong>At the end of the process Moodle will try and write the file into the right location, otherwise you can press a button to download it from the installer and then upload config.php into the main Moodle directory on the server. </p>
 117   <p>Along the way the installer will test your server environment and give you suggestions about how to fix any problems. For most common issues these suggestions should be sufficient, but if you get stuck, look below for more information about some of common things that might be holding you up. <br />
 118   </p>
 119 </blockquote>
 120 <blockquote>
 121
 122 <h3 class="sectionheading" id="webserver">4.1 General web server settings </h3>
 123   <blockquote>
 124     <p>Firstly, make sure that your web server is set up to use index.php as a default
 125       page (perhaps in addition to index.html, default.htm and so on).</p>
 126     <p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf
 127       file. Mine usually looks like this:</p>
 128     <blockquote>
 129       <pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>
 130     </blockquote>
 131     <p>Just make sure index.php is in the list (and preferably towards the start
 132       of the list, for efficiency).</p>
 133     <p>Secondly, <b>if you are using Apache 2</b>, then you should turn on the <i>AcceptPathInfo</i>
 134        variable, which allows scripts to be passed arguments like http://server/file.php/arg1/arg2.
 135        This is essential to allow relative links between your resources, and also
 136        provides a performance boost for people using your Moodle web site.  You can
 137        turn this on by adding these lines to your httpd.conf file.</p>
 138     <blockquote>
 139       <pre><strong>AcceptPathInfo</strong> on </pre>
 140     </blockquote>
 141     <p>Thirdly, Moodle requires a number of PHP settings to be active for it to
 142        work.  <b>On most servers these will already be the default settings.</b>
 143        However, some PHP servers (and some of the more recent PHP versions) may
 144        have things set differently.  These are defined in PHP's configuration
 145        file (usually called php.ini):</p>
 146     <blockquote>
 147       <pre>magic_quotes_gpc = 1    (preferred but not necessary)
 148 magic_quotes_runtime = 0    (necessary)
 149 file_uploads = 1
 150 session.auto_start = 0
 151 session.bug_compat_warn = 0
 152   </pre>
 153     </blockquote>
 154     <p>If you don't have access to httpd.conf or php.ini on your server, or you
 155       have Moodle on a server with other applications that require different settings,
 156       then don't worry, you can often still OVERRIDE the default settings.
 157     </p>
 158     <p>To do this, you need to create a file called <b>.htaccess</b> in Moodle's
 159        main directory that contains lines like the following.
 160        This only works on Apache servers and only when Overrides have been allowed in the main configuration. </p>
 161     <blockquote>
 162       <pre>
 163 DirectoryIndex index.php index.html index.htm
 164
 165 &lt;IfDefine APACHE2>
 166      <b>AcceptPathInfo</b> on
 167 &lt;/IfDefine>
 168
 169 php_flag magic_quotes_gpc 1
 170 php_flag magic_quotes_runtime 0
 171 php_flag file_uploads 1
 172 php_flag session.auto_start 0
 173 php_flag session.bug_compat_warn 0</pre>
 174     </blockquote>
 175     <p>You can also do things like define the maximum size for uploaded files:
 176
 177 </p>
 178     <blockquote>
 179       <pre>
 180 LimitRequestBody 0
 181 php_value upload_max_filesize 2M
 182 php_value post_max_size 2M
 183      </pre>
 184     </blockquote>
 185     <p>The easiest thing to do is just copy the sample file from <strong>lib/htaccess</strong>      and edit it to suit your needs.  It contains further instructions.  For
 186       example, in a Unix shell:
 187    </p>
 188     <blockquote>
 189       <pre>cp lib/htaccess .htaccess</pre>
 190     </blockquote>
 191   </blockquote>
 192 <p>&nbsp;</p>
 193 <h3 class="sectionheading" id="database">4.2 Creating a database</h3>
 194
 195   <blockquote>
 196     <p>You need to create an empty database (eg "<em>moodle</em>") in your database system
 197       along with a special user (eg "moodleuser") that has access to that database
 198       (and that database only). You could use the "root" user if you wanted to for a test server, but
 199       this is not recommended for a production system: if hackers manage to discover
 200       the password then your whole database system would be at risk, rather than
 201       just one database. </p>
 202     <p>If you are using a webhost, they will probably have a control panel web interface for you to create your database. </p>
 203     <p>The <strong>Cpanel</strong> system is  one of the most popular of these. To create a database in Cpanel, </p>
 204     <ol>
 205       <li>Click on the &quot;<strong>MySQL Databases</strong>&quot; icon.</li>
 206       <li>Type &quot;moodle&quot; in the database field and click &quot;<strong>Add Database</strong>&quot;.</li>
 207       <li> Type a username and password (not one you use elsewhere) in the respective fields and click &quot;<strong>Add User</strong>&quot;.</li>
 208       <li> Now use the &quot;<strong>Add User to Database</strong>&quot; button to give this new user account &quot;<strong>ALL</strong>&quot; rights to the new database.</li>
 209       <li>Note that the username and database names may be prefixed by your Cpanel account name. When entering this information into the Moodle installer - use the full names.</li>
 210     </ol>
 211     <p>If you have access to Unix command lines then you can do the same sort of thing by typing commands. </p>
 212     <p>Here are some example Unix command lines for MySQL: </p>
 213     <pre>
 214    # mysql -u root -p
 215    > CREATE DATABASE moodle;
 216    > GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.*
 217            TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
 218    > quit
 219    # mysqladmin -p reload
 220     </pre>
 221     <p>And some example command lines for PostgreSQL: </p>
 222     <pre>
 223    # su - postgres
 224    > psql -c "create user moodleuser createdb;" template1
 225    > psql -c "create database moodle;" -U moodleuser template1
 226    > psql -c "alter user moodleuser nocreatedb;" template1</pre>
 227   </blockquote>
 228   <p>&nbsp;</p>
 229
 230 <h3 class="sectionheading" id="data">4.3 Creating a data directory </h3>
 231
 232   <blockquote>
 233     <p>Moodle will also need some space on your server's hard disk to store uploaded files, such as course documents and user pictures. </p>
 234     <p>The Moodle installer tries hard to create this directory for you but if it fails then you will have to create a directory for this purpose manually. </p>
 235     <p>For security, it's best that this directory is NOT accessible directly via the web. The easiest way to do this is to simply locate it OUTSIDE the web directory, but if you must have it in the web directory then  protect it by creating a file in the data directory called .htaccess, containing this line: </p>
 236     <blockquote>
 237       <pre>deny from all<br />AllowOverride None</pre>
 238     </blockquote>
 239     <p>To make sure that Moodle can save uploaded files in this directory, check that the web server software (eg Apache) has permission to read, write and execute in  this directory. </p>
 240     <p>On Unix machines, this means setting the owner of the directory to be something like &quot;nobody&quot; or &quot;apache&quot;, and then giving that user read, write and execute permissions.</p>
 241     <p>On Cpanel systems you can use the &quot;File Manager&quot; to find the folder, click on it, then choose &quot;Change Permissions&quot;. On many shared hosting servers, you will probably need to restrict all file access to your "group" (to prevent other webhost customers from looking at or changing your files), but provide full read/write access to everyone else (which will allow the web server to access your files). </p>
 242     <p>Speak to your server administrator if you are having trouble setting this up securely. In particular some sites that use a PHP feature known as &quot;Safe Mode&quot; may <em>require</em> the administrator to create this directory properly for you. </p>
 243   </blockquote>
 244
 245 </blockquote>
 246
 247
 248 <h3 class="sectionheading" id="admin">5. Go to the admin page to continue configuration </h3>
 249 <blockquote>
 250   <p>Once the basic <strong>config.php</strong> has been correctly created in the previous step, trying to access the front page of your site will take you the &quot;admin&quot; page for the rest of the configuration.</p>
 251   <p>The first time you access this admin page, you will be presented with
 252     a GPL &quot;shrinkwrap&quot; agreement with which you <strong>must</strong> agree before you
 253   can continue with the setup.</p>
 254   <p>Now Moodle will start setting up your database and creating tables to store
 255     data. Firstly, the main database tables are created. You should see a number
 256     of SQL statements followed by status messages (in green or red) that look
 257     like this:</p>
 258   <blockquote>
 259     <p>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category
 260       int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default
 261       '', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT
 262       NULL default '', summary text NOT NULL, format tinyint(4) NOT NULL default
 263       '1', teacher varchar(100) NOT NULL default 'Teacher', startdate int(10)
 264       unsigned NOT NULL default '0', enddate int(10) unsigned NOT NULL default
 265       '0', timemodified int(10) unsigned NOT NULL default '0', PRIMARY KEY (id))
 266       TYPE=MyISAM</p>
 267     <p class="success">SUCCESS</p>
 268   </blockquote>
 269   <p>...and so on, followed by: <span class="success">Main databases set up
 270       successfully.</span> </p>
 271   <blockquote>
 272     <p class="style3">If you don't see these, then there must have been some problem with the database
 273         or the configuration settings you defined in config.php. Check that PHP isn't
 274         in a restricted "Safe Mode" (commercial web hosts sometimes have safe mode
 275         turned on). You can check PHP variables by creating a little file containing <strong>&lt;?php phpinfo() ?&gt;</strong> and looking at it through a browser. Check all these and
 276       try this page again.</p>
 277   </blockquote>
 278   <p>Scroll down the very bottom of the page and press the &quot;Continue&quot;
 279     link.</p>
 280   <p>You should now see a form where you can define more configuration variables
 281     for your installation, such as the default language, SMTP hosts and so on.
 282     Don't worry too much about getting everything right just now - you can always
 283     come back and edit these later on using the admin interface. The defaults are designed to be useful and secure for most sites. Scroll down to
 284     the bottom and click &quot;Save changes&quot;.</p>
 285   <blockquote>
 286     <p class="style3">If (and only if) you find yourself getting stuck on this page, unable to
 287       continue, then your server probably has what I call the "buggy referrer" problem.
 288       This is easy to fix: just turn off the &quot;secureforms&quot; setting, then
 289       try to continue again.</p>
 290   </blockquote>
 291   <p>Next you will see more  pages that print lots of status messages as they set up all the tables required by the various Moodle module. As before, they should all be <span style="color:#006600">green</span>.</p>
 292   <p>Scroll down the very bottom of the page and press the &quot;Continue&quot; link.</p>
 293   <p>The next page is a form where you can define parameters for your Moodle site
 294     and the front page, such as the name, format, description and so on. Fill
 295     this out (you can always come back and change these later) and then press
 296     &quot;Save changes&quot;.</p>
 297   <p>Finally, you will then be asked to create a top-level administration user
 298     for future access to the admin pages. Fill out the details with your own name,
 299     email etc and then click &quot;Save changes&quot;. Not all the fields are
 300     required, but if you miss any important fields you'll be re-prompted for them.
 301   </p>
 302   <blockquote>
 303     <blockquote>
 304       <blockquote>
 305         <blockquote>
 306           <blockquote>
 307             <p><strong>Make sure you remember the username and password you chose
 308               for the administration user account, as they will be necessary to
 309               access the administration page in future.</strong></p>
 310           </blockquote>
 311         </blockquote>
 312       </blockquote>
 313     </blockquote>
 314     <p class="style3">(If for any reason your install is interrupted, or there is a system error
 315       of some kind that prevents you from logging in using the admin account, you
 316       can usually log in using the default username of &quot;<strong>admin</strong>&quot;,
 317       with password &quot;<strong>admin</strong>&quot;.)</p>
 318   </blockquote>
 319   <p>Once successful, you will be returned to the home page of your new site! Note the
 320     administration links that appear down the left hand side of the page (these
 321     items also appear on a separate Admin page) - these items are only visible
 322     to you because you are logged in as the admin user. All your further administration
 323     of Moodle can now be done using this menu, such as:</p>
 324   <ul>
 325     <li>creating and deleting courses</li>
 326     <li>creating and editing user accounts</li>
 327     <li>administering teacher accounts</li>
 328     <li>changing site-wide settings like themes etc</li>
 329   </ul>
 330   <p>But you are not done installing yet! There is one very important thing still to do (see the next section on cron). </p>
 331 </blockquote>
 332 <p>&nbsp;</p>
 333
 334 <h3 class="sectionheading" id="cron">6. Set up cron -- IMPORTANT! </h3>
 335 <blockquote>
 336   <p>Some of Moodle's modules require continual checks to perform tasks. For example,
 337     Moodle needs to check the discussion forums so it can mail out copies of posts
 338     to people who have subscribed.</p>
 339   <p>The script that does all this is located in the admin directory, and is called
 340     cron.php. However, it can not run itself, so you need to set up a mechanism
 341     where this script is run regularly (eg every five or ten minutes). This provides
 342     a &quot;heartbeat&quot; so that the script can perform functions at periods
 343     defined by each module. This kind of regular mechanism is known as a <strong>cron service</strong>. </p>
 344   <p>Note that the machine performing the cron <b>does not need to be the same
 345     machine that is running Moodle</b>. For example, if you have a limited web
 346     hosting service that does not have a cron service, then you can might choose to run
 347     cron on another server or on your home computer. All that matters is that
 348     the cron.php file is called regularly. </p>
 349   <p>The load of this script is not very high, so 5 minutes is usually reasonable,
 350     but if you're worried about it you can reduce the time period to something
 351     like 15 minutes or even 30 minutes. It's best not to make the time period
 352     too long, as delaying mail-outs can slow down activity within the course.</p>
 353   <p>First, test that the script works by running it directly from your browser:</p>
 354   <blockquote>
 355     <pre>http://example.com/moodle/admin/cron.php</pre>
 356   </blockquote>
 357   <p>Now, you need to set up some of way of running the script automatically and
 358     regularly.</p>
 359
 360   <h4>On Windows systems</h4>
 361   <blockquote>
 362     <p>The simplest way is to use this little package <a href="http://moodle.org/download/modules/moodle-cron-for-windows.zip" title="Click to download this package (150k)"><strong>moodle-cron-for-windows.zip</strong></a> which makes this whole thing very easy by installing a small Windows service. Run it and forget about it!</p>
 363   </blockquote>
 364   <p><strong>On web hosting services</strong></p>
 365   <blockquote>
 366     <p> Your web-based control panel may have a web page that allows you to set up this cron process. For example, on Cpanel system, look for a button called &quot;Cron jobs&quot;. In there you can put the same sort of Unix commands as listed below. </p>
 367   </blockquote>
 368
 369   <h4> Using the command line on Unix </h4>
 370   <blockquote>
 371     <p>There are different command line programs you can use to call the page from the command line. Not all of them may be available on a given server.</p>
 372     <p>For example, you can use a Unix utility like 'wget':</p>
 373     <blockquote>
 374       <pre>wget -q -O /dev/null http://example.com/moodle/admin/cron.php</pre>
 375     </blockquote>
 376     <p>Note in this example that the output is thrown away (to /dev/null).</p>
 377     <p>The same thing using lynx:</p>
 378     <blockquote>
 379       <pre>lynx -dump http://example.com/moodle/admin/cron.php &gt; /dev/null</pre>
 380     </blockquote>
 381     <p>Alternatively you could use a standalone version of PHP, compiled to be run
 382       on the command line. The advantage with doing this is that your web server
 383       logs aren't filled with constant requests to cron.php. The disadvantage is
 384       that you need to have access to a command-line version of php.</p>
 385     <blockquote>
 386       <pre>/opt/bin/php /web/moodle/admin/cron.php
 387
 388     </pre>
 389     </blockquote>
 390   </blockquote>
 391
 392   <h4>Using the crontab program on Unix </h4>
 393   <blockquote>
 394     <p> All that Cpanel does is provide a web interface to a Unix utility known as crontab. If you have a command line, you can set up crontab yourself using the command:</p>
 395     <blockquote>
 396       <pre>crontab -e</pre>
 397    </blockquote>
 398    <p>and then adding one of the above commands like:</p>
 399     <blockquote>
 400       <pre>*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php</pre>
 401     </blockquote>
 402     <p>Usually, the "crontab" command will put you into the 'vi' editor. You enter
 403      "insert mode" by pressing "i", then type in the line as above, then exit insert mode by
 404          pressing ESC.  You save and exit by typing ":wq", or quit without saving using ":q!" (without the quotes).</p>
 405   </blockquote>
 406   <p>&nbsp;</p>
 407 </blockquote>
 408
 409 <h3 class="sectionheading" id="course">7. Create a new course</h3>
 410 <blockquote>
 411   <p>Now that Moodle is running properly, you can try creating a new course to play with. </p>
 412   <p>Select &quot;Create a new course&quot; from the Admin page (or the admin
 413     links on the home page).</p>
 414   <p>Fill out the form, paying special attention to the course format. You don't
 415     have to worry about the details too much at this stage, as everything can
 416     be changed later by the teacher. Note that the yellow help icons are everywhere to provide contextual help on any aspect. </p>
 417   <p>Press &quot;Save changes&quot;, and you will be taken to a new form where
 418     you can assign teachers to the course. You can only add existing user accounts
 419     from this form - if you want to create a new teacher account then either ask
 420     the teacher to create one for themselves (see the login page), or create one
 421     for them using the &quot;Add a new user&quot; on the Admin page.</p>
 422   <p>Once done, the course is ready to customise, and is accessible via the &quot;Courses&quot;
 423     link on the home page.</p>
 424   <p>See the &quot;<a href="http://docs.moodle.org/en/Teacher_documentation">Teacher Documentation</a>&quot; for more details
 425     on course-building.</p>
 426   <p>&nbsp;</p>
 427   <p class="center"><strong>Happy exploring and happy Moodling!</strong></p>
 428   <p class="center"><strong>If you like Moodle, please consider <a href="http://moodle.org/donations/">donating</a> to help us cover our costs! </strong></p>
 429 </blockquote>