</HEAD>\r
\r
<BODY BGCOLOR="#FFFFFF">\r
-\r
<H2>Installing Moodle</H2>\r
<P>This guide explains how to install Moodle for the first time.</P>\r
<P>Sections in this document:</P>\r
<LI><A HREF="#site">Site structure</A></LI>\r
<LI><A HREF="#data">Create a data directory</A></LI>\r
<LI><A HREF="#database">Create a database</A></LI>\r
+ <LI><A HREF="#webserver">Check web server settings</A></LI>\r
<LI><A HREF="#config">Edit config.php</A></LI>\r
<LI><A HREF="#admin">Go to the admin page</A></LI>\r
<LI><A HREF="#cron">Set up cron</A></LI>\r
<LI><A HREF="#course">Create a new course</A></LI>\r
</OL>\r
-<H3><A NAME="requirements"></A>Requirements</H3>\r
-<P>Moodle is primarily developed in Linux using PHP, Apache and MySQL, and regularly \r
- tested under Windows XP and Mac OS X environments.</P>\r
-<P>All you should need are:</P>\r
-<UL>\r
- <LI>a working installation of <A HREF="http://www.php.net/">PHP</A> (version \r
- 4.1.0 or better), including the <A HREF="http://www.boutell.com/gd/">GD</A> \r
- library for manipulating images.</LI>\r
- <LI>a working database server (<A HREF="http://www.mysql.com/">MySQL</A> for \r
- now, but soon it will support PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, \r
- Access, ADO, Sybase, DB2 or ODBC).</LI>\r
-</UL>\r
-<P>On a Windows platform, the quickest way to satisfy these requirements is to \r
- download <A HREF="http://www.phpgeek.com/">PHPTriad</A>, <A HREF="http://www.foxserv.net/">FoxServ</A>, \r
- or <A HREF="http://www.easyphp.org/">EasyPHP</A>\r
- which will install Apache, PHP, and MySQL for you. Make sure you enable the \r
- GD module so Moodle can process images - you may have to edit php.ini and remove \r
- the comment (;) from this line: 'extension=php_gd.dll'.</P>\r
-<P>On Mac OS X I highly recommend the <a href="http://fink.sourceforge.net/">fink</a> \r
- project.</P>\r
+<H3><A NAME="requirements"></A>1. Requirements</H3>\r
+<blockquote>\r
+ <p>Moodle is primarily developed in Linux using PHP, Apache and MySQL, and regularly \r
+ tested under Windows XP and Mac OS X environments.</p>\r
+ <p>All you should need are:</p>\r
+ <ul>\r
+ <li>a working installation of <A HREF="http://www.php.net/">PHP</A> (version \r
+ 4.1.0 or better), including the <A HREF="http://www.boutell.com/gd/">GD</A> \r
+ library for manipulating images.</li>\r
+ <li>a working database server (<A HREF="http://www.mysql.com/">MySQL</A> for \r
+ now, but soon it will support PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, \r
+ Access, ADO, Sybase, DB2 or ODBC).</li>\r
+ </ul>\r
+ <p>On a Windows platform, the quickest way to satisfy these requirements is \r
+ to download <A HREF="http://www.phpgeek.com/">PHPTriad</A>, <A HREF="http://www.foxserv.net/">FoxServ</A>, \r
+ or <A HREF="http://www.easyphp.org/">EasyPHP</A> which will install Apache, \r
+ PHP, and MySQL for you. Make sure you enable the GD module so Moodle can process \r
+ images - you may have to edit php.ini and remove the comment (;) from this \r
+ line: 'extension=php_gd.dll'.</p>\r
+ <p>On Mac OS X I highly recommend the <a href="http://fink.sourceforge.net/">fink</a> \r
+ project.</p>\r
+</blockquote>\r
<P> </P>\r
-<H3><A NAME="downloading"></A>Download</H3>\r
-<P>There are two ways to get Moodle, as a compressed package and via CVS. These \r
- are explained in detail on the download page on <A HREF="http://moodle.com/">http://moodle.com/</A></P>\r
-<P>After downloading and unpacking the archive, or checking out the files via \r
- CVS, you will be left with a directory called "moodle", containing \r
- a number of files and folders. </P>\r
-<P>You can either place the whole folder in your web server documents directory, \r
- in which case the site will be located at <B>http://yourwebserver.com/moodle</B>, \r
- or you can copy all the contents straight into the main web server documents \r
- directory, in which case the site will be simply <B>http://yourwebserver.com</B>.</P>\r
+<H3><A NAME="downloading"></A>2. Download</H3>\r
+<blockquote>\r
+ <p>There are two ways to get Moodle, as a compressed package and via CVS. These \r
+ are explained in detail on the download page on <A HREF="http://moodle.com/">http://moodle.com/</A></p>\r
+ <p>After downloading and unpacking the archive, or checking out the files via \r
+ CVS, you will be left with a directory called "moodle", containing \r
+ a number of files and folders. </p>\r
+ <p>You can either place the whole folder in your web server documents directory, \r
+ in which case the site will be located at <B>http://yourwebserver.com/moodle</B>, \r
+ or you can copy all the contents straight into the main web server documents \r
+ directory, in which case the site will be simply <B>http://yourwebserver.com</B>.</p>\r
+</blockquote>\r
<P> </P>\r
-<H3><A NAME="site"></A>Site structure</H3>\r
-<P>Here is a quick summary of the contents of the Moodle folder, to help get you \r
- oriented:</P>\r
-<BLOCKQUOTE> \r
- <P>config.php - the only file you need to edit to get started<br>\r
- version.php - defines the current version of Moodle code<BR>\r
- index.php - the front page of the site</P>\r
- <UL>\r
- <LI>admin/ - code to administrate the whole server </LI>\r
- <LI>course/ - code to display and manage courses </LI>\r
- <LI>doc/ - help documentation for Moodle (eg this page)</LI>\r
- <LI>files/ - code to display and manage uploaded files</LI>\r
- <LI>lang/ - texts in different languages, one directory per language </LI>\r
- <LI>lib/ - libraries of core Moodle code </LI>\r
- <LI>login/ - code to handle login and account creation </LI>\r
- <LI>mod/ - all Moodle course modules</LI>\r
- <LI>pix/ - generic site graphics</LI>\r
- <LI>theme/ - theme packs/skins to change the look of the site.</LI>\r
- <LI>user/ - code to display and manage users</LI>\r
- </UL>\r
- <P> </P>\r
+<H3><A NAME="site"></A>3. Site structure</H3>\r
+<BLOCKQUOTE>\r
+ <p>Here is a quick summary of the contents of the Moodle folder, to help get \r
+ you oriented:</p>\r
+ <blockquote>\r
+ <p>config.php - the only file you need to edit to get started<br>\r
+ version.php - defines the current version of Moodle code<BR>\r
+ index.php - the front page of the site</p>\r
+ <ul>\r
+ <li>admin/ - code to administrate the whole server </li>\r
+ <li>course/ - code to display and manage courses </li>\r
+ <li>doc/ - help documentation for Moodle (eg this page)</li>\r
+ <li>files/ - code to display and manage uploaded files</li>\r
+ <li>lang/ - texts in different languages, one directory per language </li>\r
+ <li>lib/ - libraries of core Moodle code </li>\r
+ <li>login/ - code to handle login and account creation </li>\r
+ <li>mod/ - all Moodle course modules</li>\r
+ <li>pix/ - generic site graphics</li>\r
+ <li>theme/ - theme packs/skins to change the look of the site.</li>\r
+ <li>user/ - code to display and manage users</li>\r
+ </ul>\r
+ <p> </p>\r
+ </blockquote>\r
</BLOCKQUOTE>\r
-<H3><A NAME="data"></A>Create a data directory</H3>\r
-<P>Moodle will also need some space on your hard disk to store uploaded files, \r
- such as course documents and user pictures.</P>\r
-<P>Create a directory for this purpose somewhere <B>away</B> from the web server \r
- documents directory (we don't want these files to be directly accessible from \r
- the web), and ensure that the web server software has permission to write to \r
- this directory. On Unix machines, this means setting the owner of the directory \r
- to be something like "nobody" or "apache".</P>\r
+<H3><A NAME="data"></A>4. Create a data directory</H3>\r
+<blockquote>\r
+ <p>Moodle will also need some space on your hard disk to store uploaded files, \r
+ such as course documents and user pictures.</p>\r
+ <p>Create a directory for this purpose somewhere <B>away</B> from the web server \r
+ documents directory (we don't want these files to be directly accessible from \r
+ the web), and ensure that the web server software has permission to write \r
+ to this directory. On Unix machines, this means setting the owner of the directory \r
+ to be something like "nobody" or "apache".</p>\r
+</blockquote>\r
<P> </P>\r
-<H3><A NAME="database"></A>Create a database</H3>\r
-<P>You need to create an empty database (eg "moodle") in your database system \r
- along with a special user (eg "moodleuser") that has access to that database \r
- (and that database only. For example, don't use the "root" user for the moodle \r
- database in a production system - it's a security hazard). </P>\r
-<P>eg for MySQL: </P>\r
-<PRE>\r
+<H3><A NAME="database"></A>5. Create a database</H3>\r
+<blockquote>\r
+ <p>You need to create an empty database (eg "moodle") in your database system \r
+ along with a special user (eg "moodleuser") that has access to that database \r
+ (and that database only. For example, don't use the "root" user for the moodle \r
+ database in a production system - it's a security hazard). </p>\r
+ <p>eg for MySQL: </p>\r
+ <PRE>\r
# mysql -u root -p\r
> CREATE DATABASE moodle; \r
> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.* \r
> quit \r
# mysqladmin -p reload\r
</PRE>\r
-\r
-<P>(For MySQL I highly recommend the use of <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a> \r
- to manage your databases).</P>\r
-<H3><A NAME="config"></A>Edit config.php</H3>\r
-<P>Now you can edit the configuration file, <strong>config.php</strong>. This \r
- file is used by all other files in Moodle.</P>\r
-<P>To start with, make a copy of config-dist.php and call it config.php. We do \r
- this so that your config.php won't be overwritten in case you upgrade Moodle \r
- later on. \r
-<P>Edit config.php to specify the database details that you just defined, as well as the \r
- site address, file system directory, data directory and so on. The config file \r
- has detailed directions.</P>\r
-<P>For the rest of this installation document we will assume your site is at: \r
- http://example.com/moodle</P>\r
+ <p>(For MySQL I highly recommend the use of <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a> \r
+ to manage your databases).</p>\r
+</blockquote>\r
<P> </P>\r
-<H3><A NAME="admin"></A>Go to the admin page</H3>\r
-<P>The admin page should now be working at: http://example.com/moodle/admin</P>\r
-<P>If you try and access the front page of your site you'll be taken there automatically \r
- anyway. </P>\r
-<P>The first time you access this page, Moodle will set up your database and prompt \r
- you for more information.</P>\r
-<P>Firstly, the main database tables are created. You should see a number of SQL \r
- statements followed by status messages (in green or red) that look like this:</P>\r
-<BLOCKQUOTE> \r
- <P>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category \r
- int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default \r
- '', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT NULL \r
- default '', summary text NOT NULL, format tinyint(4) NOT NULL default '1', \r
- teacher varchar(100) NOT NULL default 'Teacher', startdate int(10) unsigned \r
- NOT NULL default '0', enddate int(10) unsigned NOT NULL default '0', timemodified \r
- int(10) unsigned NOT NULL default '0', PRIMARY KEY (id)) TYPE=MyISAM</P>\r
- <P><FONT COLOR="#006600">SUCCESS</FONT></P>\r
- <P>...and so on, followed by: <FONT COLOR="#FF0000">Main databases set up successfully</FONT>. \r
- </P>\r
-</BLOCKQUOTE>\r
-<P>If you don't see these, then there must have been some problem with the database \r
- or the configuration settings you defined in config.php. Check that PHP isn't \r
- in a restricted "safe mode" (commercial web hosts often have safe mode turned \r
- on). You can check PHP variables by creating a little file containing <? phpinfo \r
- ?> and looking at it through a browser. Check all these and try this page \r
- again.</P>\r
-<P>Scroll down the very bottom of the page and press the "Continue" \r
- link.</P>\r
-<P>Next you will see a similar page that sets up all the tables required by each \r
- Moodle module. As before, they should all be green, otherwise you may be a problem \r
- in the module code.</P>\r
-<P>Scroll down the very bottom of the page and press the "Continue" \r
- link.</P>\r
-<P>You should now see a form where you can define more parameters for your Moodle \r
- site, such as the name, the description shown on the front page, and so on. \r
- Fill this out (you can always go back and change these later) and then press \r
- "Update the site".</P>\r
-<P>Finally, you will then be asked to create a top-level administration user for \r
- future access to the admin pages. Fill out the details with your own name, email \r
- etc and then click "Update this user". You will be returned to the \r
- main admin page, which contain a number of links arranged in a menu (these items \r
- also appear on the home page when you are logged in as the admin user).</P>\r
-<P><strong>Make sure you remember the username and password you chose for the \r
- administration user, as they will be necessary to access the administration \r
- page in future.</strong></P>\r
-<P>All your further administration of Moodle can now be done using the administration \r
- menu, which includes tasks such as:</P>\r
-<UL>\r
- <LI>creating and deleting courses</LI>\r
- <LI>creating and editing user accounts</LI>\r
- <LI>administering teacher accounts</LI>\r
- <LI>changing site-wide settings</LI>\r
-</UL>\r
+<H3><A NAME="database"></A>6. Check your web server settings</H3>\r
+<blockquote>\r
+ <p>Firstly, make sure that your web server is set up to use index.php as a default \r
+ page (perhaps in addition to index.html, default.htm and so on).</p>\r
+ <p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf \r
+ file. Mine usually looks like this:</p>\r
+ <blockquote>\r
+ <pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>\r
+ </blockquote>\r
+ <p>Just make sure index.php is in the list (and preferably towards the start \r
+ of the list, for efficiency).</p>\r
+ <p>Secondly, check your PHP configuration file (usually called php.ini) and \r
+ make sure uploading has been turned on:</p>\r
+ <blockquote>\r
+ <pre>file_uploads = On</pre>\r
+ </blockquote>\r
+ <p>Most distributions of PHP have this turned on by default, but you may want \r
+ to check it anyway. </p>\r
+</blockquote>\r
+<p> </p>\r
+<H3><A NAME="config"></A>7. Edit config.php</H3>\r
+<blockquote>\r
+ <p>Now you can edit the configuration file, <strong>config.php</strong>. This \r
+ file is used by all other files in Moodle.</p>\r
+ <p>To start with, make a copy of config-dist.php and call it config.php. We \r
+ do this so that your config.php won't be overwritten in case you upgrade Moodle \r
+ later on. </p>\r
+ <p>Edit config.php to specify the database details that you just defined, as \r
+ well as the site address, file system directory, data directory and so on. \r
+ The config file has detailed directions.</p>\r
+ <p>For the rest of this installation document we will assume your site is at: \r
+ <u>http://example.com/moodle</u></p>\r
+</blockquote>\r
<P> </P>\r
-<H3><A NAME="cron"></A>Set up cron</H3>\r
-<P>Some of Moodle's modules require continual checks to perform tasks. For example, \r
- Moodle needs to check the discussion forums so it can mail out copies of posts \r
- to people who have subscribed.</P>\r
-<P>The script that does all this is located in the admin directory, and is called \r
- cron.php. However, it can not run itself, so you need to set up a mechanism \r
- where this script is run regularly (eg every five minutes). This provides a \r
- "heartbeat" so that the script can perform functions at periods defined \r
- by each module.</P>\r
-<P>Test that the script works by running it directly from your browser:</P>\r
-<BLOCKQUOTE> \r
- <PRE>http://example.com/moodle/admin/cron.php</PRE>\r
-</BLOCKQUOTE>\r
-<P>Now, you need to set up some of way of running the script automatically and \r
- regularly. </P>\r
-<BLOCKQUOTE> \r
- <H4>Running the script from a command line</H4>\r
- <P>You can call the page from the command line just as you did in the example \r
- above. For example, you can use a Unix utility like 'wget':</P>\r
- <BLOCKQUOTE> \r
- <PRE>wget -q -O /dev/null http://example.com/moodle/admin/cron.php</PRE>\r
- </BLOCKQUOTE>\r
- <P>Note in this example that the output is thrown away (to /dev/null).</P>\r
- <P>The same thing using lynx:</P>\r
+<H3><A NAME="admin"></A>8. Go to the admin page</H3>\r
+<blockquote> \r
+ <p>The admin page should now be working at: http://example.com/moodle/admin. \r
+ If you try and access the front page of your site you'll be taken there automatically \r
+ anyway. The first time you access this admin page, you will be presented with \r
+ a GPL agreement which you need to agree with to continue with the setup.</p>\r
+ <p>Now Moodle will start setting set up your database. Firstly, the main database \r
+ tables are created. You should see a number of SQL statements followed by \r
+ status messages (in green or red) that look like this:</p>\r
+ <blockquote> \r
+ <p>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category \r
+ int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default \r
+ '', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT \r
+ NULL default '', summary text NOT NULL, format tinyint(4) NOT NULL default \r
+ '1', teacher varchar(100) NOT NULL default 'Teacher', startdate int(10) \r
+ unsigned NOT NULL default '0', enddate int(10) unsigned NOT NULL default \r
+ '0', timemodified int(10) unsigned NOT NULL default '0', PRIMARY KEY (id)) \r
+ TYPE=MyISAM</p>\r
+ <p><FONT COLOR="#006600">SUCCESS</FONT></p>\r
+ <p>...and so on, followed by: <FONT COLOR="#FF0000">Main databases set up \r
+ successfully</FONT>. </p>\r
+ </blockquote>\r
+ <p>If you don't see these, then there must have been some problem with the database \r
+ or the configuration settings you defined in config.php. Check that PHP isn't \r
+ in a restricted "safe mode" (commercial web hosts often have safe mode turned \r
+ on). You can check PHP variables by creating a little file containing <? \r
+ phpinfo ?> and looking at it through a browser. Check all these and try \r
+ this page again.</p>\r
+ <p>Scroll down the very bottom of the page and press the "Continue" \r
+ link.</p>\r
+ <p>Next you will see a similar page that sets up all the tables required by \r
+ each Moodle module. As before, they should all be green, otherwise you may \r
+ be a problem in the module code.</p>\r
+ <p>Scroll down the very bottom of the page and press the "Continue" \r
+ link.</p>\r
+ <p>You should now see a form where you can define more parameters for your Moodle \r
+ site, such as the name, the description shown on the front page, and so on. \r
+ Fill this out (you can always go back and change these later) and then press \r
+ "Save changes".</p>\r
+ <p>Finally, you will then be asked to create a top-level administration user \r
+ for future access to the admin pages. Fill out the details with your own name, \r
+ email etc and then click "Save changes". Not all the fields are \r
+ required, but if you miss any important fields you'll be re-prompted for them. \r
+ </p>\r
<blockquote> \r
+ <blockquote> \r
+ <blockquote> \r
+ <blockquote> \r
+ <blockquote>\r
+ <p><strong>Make sure you remember the username and password you chose \r
+ for the administration user account, as they will be necessary to \r
+ access the administration page in future.</strong></p>\r
+ </blockquote>\r
+ </blockquote>\r
+ </blockquote>\r
+ </blockquote>\r
+ </blockquote>\r
+ <p>Once successful, you will be returned to the main admin page, which contain \r
+ a number of links arranged in a menu (these items also appear on the home \r
+ page when you are logged in as the admin user). All your further administration \r
+ of Moodle can now be done using this menu, such as:</p>\r
+ <ul>\r
+ <li>creating and deleting courses</li>\r
+ <li>creating and editing user accounts</li>\r
+ <li>administering teacher accounts</li>\r
+ <li>changing site-wide settings like themes etc</li>\r
+ </ul>\r
+</blockquote>\r
+<P> </P>\r
+<H3><A NAME="cron"></A>9. Set up cron</H3>\r
+<blockquote> \r
+ <p>Some of Moodle's modules require continual checks to perform tasks. For example, \r
+ Moodle needs to check the discussion forums so it can mail out copies of posts \r
+ to people who have subscribed.</p>\r
+ <p>The script that does all this is located in the admin directory, and is called \r
+ cron.php. However, it can not run itself, so you need to set up a mechanism \r
+ where this script is run regularly (eg every five minutes). This provides \r
+ a "heartbeat" so that the script can perform functions at periods \r
+ defined by each module.</p>\r
+ <p>Test that the script works by running it directly from your browser:</p>\r
+ <blockquote> \r
+ <PRE>http://example.com/moodle/admin/cron.php</PRE>\r
+ </blockquote>\r
+ <p>Now, you need to set up some of way of running the script automatically and \r
+ regularly. </p>\r
+ <H4> Running the script from a command line</H4>\r
+ <p>You can call the page from the command line just as you did in the example \r
+ above. For example, you can use a Unix utility like 'wget':</p>\r
+ <blockquote>\r
+ <PRE>wget -q -O /dev/null http://example.com/moodle/admin/cron.php</PRE>\r
+ </blockquote>\r
+ <p>Note in this example that the output is thrown away (to /dev/null).</p>\r
+ <p>The same thing using lynx:</p>\r
+ <blockquote>\r
<pre>lynx -dump http://example.com/moodle/admin/cron.php > /dev/null</pre>\r
</blockquote>\r
- <P>Alternatively you could use a standalone version of PHP, compiled to be run \r
+ <p>Alternatively you could use a standalone version of PHP, compiled to be run \r
on the command line. The advantage with doing this is that your web server \r
logs aren't filled with constant requests to cron.php. The disadvantage is \r
- that you need to have access to a command-line version of php.</P>\r
- <blockquote> \r
+ that you need to have access to a command-line version of php.</p>\r
+ <blockquote>\r
<PRE>/opt/bin/php /web/moodle/admin/cron.php\r
\r
\r
</PRE>\r
</blockquote>\r
<h4>Automatically running the script every 5 minutes</h4>\r
- <P>On Unix systems: Use <B>cron</B>. Edit your cron settings from the commandline \r
- using "crontab -e" and add a line like:</P>\r
- <BLOCKQUOTE> \r
+ <p>On Unix systems: Use <B>cron</B>. Edit your cron settings from the commandline \r
+ using "crontab -e" and add a line like:</p>\r
+ <blockquote>\r
<PRE>*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php</PRE>\r
- </BLOCKQUOTE>\r
- <P>On Windows systems: The simplest way is to use my package <A TITLE="Click to download this package (150k)" HREF="http://moodle.com/download/moodle-cron-for-windows.zip">moodle-cron-for-windows.zip</A> which makes all this very easy.</P>\r
- <P>Other platforms: you will need to find another way to do this (please let \r
+ </blockquote>\r
+ <p>On Windows systems: The simplest way is to use my package <A TITLE="Click to download this package (150k)" HREF="http://moodle.com/download/moodle-cron-for-windows.zip">moodle-cron-for-windows.zip</A> \r
+ which makes this whole thing very easy.</p>\r
+ <p>Other platforms: you will need to find another way to do this (please let \r
me know so I can update this documentation).<br>\r
- </P>\r
-</BLOCKQUOTE>\r
-<H3><A NAME="course"></A>Create a new course</H3>\r
-<P>Now that Moodle is running properly, you can create a course. </P>\r
-<P>Start on the admin page ( http://example.com/moodle/admin ) and select "Create \r
- a new course".</P>\r
-<P>Fill out the form, paying special attention to the course format.</P>\r
-<P>If you choose a "<strong>weekly</strong>" format, then course modules \r
- will be arranged in sections called "weeks". The weeks in your course \r
- are defined by the start date and the number of weeks you choose on this form. \r
- The idea is that the next time you run this course, you can just change the \r
- dates and keep the essential course format.</P>\r
-<P>The "<strong>topics</strong>" format is pretty much the same, except \r
- it doesn't use "weeks". Useful when you arrange a course into different-sized \r
- chunks of time. The start date will not be used on the main course display.</P>\r
-<P>The "<strong>social</strong>" format is for courses that don't have \r
- a start or finish. It is basically arranged around one big forum and works a \r
- nice replacement to standard mailing lists. Again the start date will not affect \r
- the operation of the course - it will only affect the display of logs.</P>\r
-<P>Press "Update this course", and you will be taken to a new form where \r
- you can assign teachers to the course. You can only add existing user accounts \r
- from this form - if you want to create a new teacher account then either ask \r
- the teacher to create one for themselves (see the login page), or create one \r
- for them using the "Add a new user" on the Admin page.</P>\r
-<P>Once done, your course is ready to customise, and is accessible via the "Courses" \r
- link on the home page.</P>\r
-<P>See the "<A HREF="teacher.html">Teacher Manual</A>" for more details \r
- on course-building.</P>\r
+ </p>\r
+</blockquote>\r
+<H3><A NAME="course"></A>10. Create a new course</H3>\r
+<blockquote>\r
+ <p>Now that Moodle is running properly, you can create a course. </p>\r
+ <p>Select "Create a new course" from the Admin page (or the admin \r
+ links on the home page).</p>\r
+ <p>Fill out the form, paying special attention to the course format. You don't \r
+ have to worry about the details too much at this stage, as everything can \r
+ be changed later by the teacher.</p>\r
+ <p>Press "Save changes", and you will be taken to a new form where \r
+ you can assign teachers to the course. You can only add existing user accounts \r
+ from this form - if you want to create a new teacher account then either ask \r
+ the teacher to create one for themselves (see the login page), or create one \r
+ for them using the "Add a new user" on the Admin page.</p>\r
+ <p>Once done, the course is ready to customise, and is accessible via the "Courses" \r
+ link on the home page.</p>\r
+ <p>See the "<A HREF="teacher.html">Teacher Manual</A>" for more details \r
+ on course-building.</p>\r
+</blockquote>\r
<P> </P>\r
<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="index.html" TARGET="_top">Moodle Documentation</A></FONT></P>\r
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: install.html,v 1.10 2002/08/16 \r
+ 08:33:54 martin Exp $</FONT></P>\r
\r
</BODY>\r
projects / moodle.git / commitdiff