From d51fb96e981b4dd43296ed23486ec7ca1ae3c4a2 Mon Sep 17 00:00:00 2001 From: moodler Date: Mon, 23 Dec 2002 16:07:38 +0000 Subject: [PATCH] More up-to-date-info --- doc/install.html | 40 +++++++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 15 deletions(-) diff --git a/doc/install.html b/doc/install.html index 2089e1397b..b81347d1e9 100755 --- a/doc/install.html +++ b/doc/install.html @@ -26,20 +26,18 @@

1. Requirements

Moodle is primarily developed in Linux using PHP, Apache and MySQL, and regularly - tested under Windows XP and Mac OS X environments.

+ tested with PostgreSQL and in Windows XP and Mac OS X environments.

All you should need are:

-

On a Windows platform, the quickest way to satisfy these requirements is to download FoxServ, @@ -48,7 +46,7 @@ images - you may have to edit php.ini and remove the comment (;) from this line: 'extension=php_gd.dll'.

On Mac OS X I highly recommend the fink - project.

+ project as a way to download easily-maintainable packages for all of this.

 

2. Download

@@ -95,7 +93,7 @@ such as course documents and user pictures.

Create a directory for this purpose somewhere. For security, it's best that - this directory is NOT accessible via the web. The easiest way to do this + this directory is NOT accessible directly via the web. The easiest way to do this is to simply locate it OUTSIDE the web directory, otherwise protect it by creating a file in the data directory called .htaccess, containing this line:

@@ -106,6 +104,13 @@ the web server software (eg Apache) has permission to write to this directory. On Unix machines, this means setting the owner of the directory to be something like "nobody" or "apache".

+ +

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). Speak to your server administrator if you are having + trouble setting this up securely.

+

 

5. Create a database

@@ -117,7 +122,7 @@ the password then your whole database system would be at risk, rather than just one database.

-

eg for MySQL:

+

Example command lines for MySQL: 

    # mysql -u root -p
    > CREATE DATABASE moodle; 
@@ -125,14 +130,18 @@
            TO moodleuser@localhost IDENTIFIED BY 'yourpassword'; 
    > quit 
    # mysqladmin -p reload
+
+

Example command lines for PostgreSQL:

+ 
+   # su - postgres
+   > psql -c "create user moodleuser createdb;" template1
+   > psql -c "create database moodle;" -U moodleuser template1
+   > psql -c "alter user moodleuser nocreatedb;" template1

(For MySQL I highly recommend the use of phpMyAdmin to manage your databases).

-

Note that Moodle currently does not yet support table name prefixes, and works best with a whole - database to itself. If you do want to install Moodle in a database that already contains - tables, and are SURE that Moodle tables will not conflict with any tables - that you already have installed, then you can call this script in your moodle - installation: admin/forcetables.php

+

As of version 1.0.8, Moodle now supports table prefixes, and so can safely share + a database with tables from other applications.

 

6. Check your web server settings

@@ -193,7 +202,8 @@ php_value post_max_size 2M

To start with, make a copy of config-dist.php and call it config.php. We do this so that your config.php won't be overwritten in case you upgrade Moodle later on.

-

Edit config.php to specify the database details that you just defined, as +

Edit config.php to specify the database details that you just defined (including + a table prefix - notice this is REQUIRED for PostgreSQL), as well as the site address, file system directory and data directory. The config file has detailed directions.

For the rest of this installation document we will assume your site is at: -- 2.39.5